bibcites
Command-line utility which reads a BibTeX file, finds entries with a DOI, looks up the corresponding number of citations using OpenCitations, saves this number to the addendum field of each entry, and writes results to a new BibTex file.
Installation
python -m pip install bibcites should do the trick.
Usage
Usage: bibcites [OPTIONS] BIBFILE
Reads a BibTeX file (BIBFILE), finds entries with a DOI, looks up the
corresponding number of citations using OpenCitations
(https://opencitations.net), saves this number to the 'addendum' field of
each entry, and writes results to a new BibTex file.
Optionally, using option -s, print out a list of entries with DOI sorted by
number of citations.
Options:
-o TEXT output BibTex file
-f TEXT format of text to save to 'addendum' field
-s print list sorted by cites
-v enable verbose output
-t TEXT only process entries of this type (may be used several times to
process several types)
-n INTEGER size limit for OpenCitations queries
--help Show this message and exit.
bibcites myfile.bib will read the contents of myfile.bib, look up all entries with a DOI field in OpenCitations, append “[X citations]” to the addendum field of each entry, and save the result to myfile_withcites.bib
- To get verbose output, use
-voption. - To set a custom file name for the output BibTeX file, use the
-o <customfilename>option. - To set a custom format to the
addendumfield, use the-foption, e.g.,-f 'Cited {:s} times'. Use the{:s}specifier because the citation count is a string. - To print out a list of processed entries, sorted by decreasing number of citations, use the
-soption. - To process only entries of certain types, use the
-toption one or more times, e.g.,-t article -t book. - To limit the size of OpenCitations queries, use
-noption (default is-n 50).
Contact
All questions and suggestions are welcome and should be directed at Mathieu Daëron.
Metadata
Release files for bibcites 2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bibcites-2.0.1.tar.gz | 3.5 kB | Without provenance | Details for bibcites-2.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bibcites-2.0.1-py3-none-any.whl | Python 3 | none | any | Details for bibcites-2.0.1-py3-none-any.whl |
Total release size: 8.3 kB
Release files / bibcites-2.0.1.tar.gz
| Download URL | bibcites-2.0.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b72b1b326c281de6f10f8f8582bbf5f32c0b405599d122e87c7269b6ac5158aa
|
|
BLAKE2b-256 checksum How to use checksums |
8dffafc91718f97b63d935070eb040a8bd235717e83ae8e2021a94492237beb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.6
|
Release files / bibcites-2.0.1-py3-none-any.whl
| Download URL | bibcites-2.0.1-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79ae65295b99085c2c7180a7615c7b548bc9a31fcd750e427d6910724591b194
|
|
BLAKE2b-256 checksum How to use checksums |
b0f81d190a483e23d067b96a055a5f728108b8bf89b1b4b83c21deffcaaf83fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.6
|
Security for bibcites 2.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.