Format author lists for academic texts and journal submissions.
Project description
🚢 Authorship 🚢
Format author lists for academic texts and journal submissions.
🕵️ Why does this exist?
Maintaining author lists on collaborative academic work is a bit of a pain. A lot of us have started collecting author information on Google Sheets since it allows people to input their own information, like their ORCID and affiliations. I wanted to automate turning those sheets into some useful forms for copy/pasting into my manuscripts (e.g., in Google Docs or LaTeX) as well submission forms (e.g., bulk author TSV file import on bioRxiv).
💪 Getting Started
This example shows loading a standardized spreadsheet from Google Sheets that is subsequently printed in a nice text format, in a bioRxiv bulk import format, and in LaTeX for a submission to Nature Scientific Data.
from authorship.reader import GoogleSheetReader, OboGoogleSheetReader
from authorship.writer import BiorxivWriter, ScientificDataWriter, TextWriter
# Standard google sheet
reader = GoogleSheetReader("1Fo1YH3ZzOVrQ4wzKnBm6sPha5hZG66-u-uSMDGUvguI")
TextWriter().print(reader)
BiorxivWriter().print(reader)
ScientificDataWriter().print(reader)
# shortcut via class_resolver
reader.print("text")
reader.print("biorxiv)
The next example shows loading an OBO community-flavored spreadsheet from Google Sheets. This has been used for the SSSOM, ODK, Cell Ontology, and several other papers.
from authorship.reader import OboGoogleSheetReader
# OBO community-flavored google sheet
reader = OboGoogleSheetReader(
"1NfhibWHOKgV2glmgRdKMzHEzTCw2_dUq_t0Zq64cgeQ",
skiprows=1,
)
reader.print("text")
reader.print("biorxiv")
reader.print("scientific data")
🐇 Extending
You can implement your own reader subclassing the Reader
class and
implementing the get_authorship()
function.
Similarly, you can implement your own writer by subclassing the Writer
class
an implementing the iter_lines()
function
We'd be happy to accept new plugins, especially to help auto-generate LaTeX for various journal-specific LaTeX templates.
🚀 Installation
The most recent code and data can be installed directly from GitHub with:
$ pip install git+https://github.com/cthoyt/authorship.git
👐 Contributing
Contributions, whether filing an issue, making a pull request, or forking, are appreciated. See CONTRIBUTING.md for more information on getting involved.
👋 Attribution
⚖️ License
The code in this package is licensed under the MIT License.
🍪 Cookiecutter
This package was created with @audreyfeldroy's cookiecutter package using @cthoyt's cookiecutter-snekpack template.
🛠️ For Developers
See developer instructions
The final section of the README is for if you want to get involved by making a code contribution.
Development Installation
To install in development mode, use the following:
$ git clone git+https://github.com/cthoyt/authorship.git
$ cd authorship
$ pip install -e .
🥼 Testing
After cloning the repository and installing tox
with pip install tox
, the unit tests in the tests/
folder can be
run reproducibly with:
$ tox
Additionally, these tests are automatically re-run with each commit in a GitHub Action.
📖 Building the Documentation
The documentation can be built locally using the following:
$ git clone git+https://github.com/cthoyt/authorship.git
$ cd authorship
$ tox -e docs
$ open docs/build/html/index.html
The documentation automatically installs the package as well as the docs
extra specified in the setup.cfg
. sphinx
plugins
like texext
can be added there. Additionally, they need to be added to the
extensions
list in docs/source/conf.py
.
📦 Making a Release
After installing the package in development mode and installing
tox
with pip install tox
, the commands for making a new release are contained within the finish
environment
in tox.ini
. Run the following from the shell:
$ tox -e finish
This script does the following:
- Uses Bump2Version to switch the version number in the
setup.cfg
,src/authorship/version.py
, anddocs/source/conf.py
to not have the-dev
suffix - Packages the code in both a tar archive and a wheel using
build
- Uploads to PyPI using
twine
. Be sure to have a.pypirc
file configured to avoid the need for manual input at this step - Push to GitHub. You'll need to make a release going with the commit where the version was bumped.
- Bump the version to the next patch. If you made big changes and want to bump the version by minor, you can
use
tox -e bumpversion minor
after.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for authorship-0.0.1-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | f7a0f878e9173d742adcd47b6077e513983d7c2af7ea4f5f42ad5df980a32b4e |
|
MD5 | f0a36d918e725ee694a8116f3a1a8a8e |
|
BLAKE2b-256 | 3b2233b00094f78b1fe5e21f0f366828336cf3601565bbcff10fe787503d1d4c |