Simple Bibliography Database
## Introduction
This tool manages article PDFs. This tool is based on two working principles.
First, DOIs are central. Only documents with a DOI can be stored in the
database. All metadata is acquired through the [Crossref](https://crossref.org)
[API](https://github.com/CrossRef/rest-api-doc) through DOIs scraped from the
PDF or entered by the user. Second, document repositories are local to a
directory hierarchy. For example, if I have a project based in ~/projects/foo,
I can create a document repository by
cd ~/projects/foo
pdfs init
This creates a new direcory in ~/projects/foo called articles. All PDFs
imported into the database will be copied here. Running `pdfs` in
~/projects/foo, or any directory below it will use the repository at
~/projects/foo/articles.
## Commands
usage: pdfs command ...
| Command | Description |
|---------|--------------------------------------------|
| add | Import new PDF into repository |
| aux2bib | Read LaTeX .aux file and dump a .bib file |
| bibtex | Dump bibtex for keys |
| edit | Edit bibtex, metadata and file attachments |
| import | Import entries from other database |
| info | Print information about current repository |
| init | Initialize new document repository |
| list | List all items in database |
| search | Search full text of PDF |
| view | View article PDF and attachements |
| watch | Watch a directory for new pdf files to add |
| www | Spin up http server |
## Command line completion
Command line autocomplete support via
[argcomplete](https://argcomplete.readthedocs.io).
To start quickly with zsh:
autoload bashcompinit
bashcompinit
eval "$(register-python-argcomplete pdfs)"
Metadata
Release files for pdfs 0.1.0
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 |
|---|---|---|---|---|
| pdfs-0.1.0.tar.gz | 535.4 kB | Without provenance | Details for pdfs-0.1.0.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pdfs-0.1.0-py3.6.egg | Legacy Egg format | - | - | Details for pdfs-0.1.0-py3.6.egg |
| pdfs-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pdfs-0.1.0-py3-none-any.whl |
Total release size: 1.7 MB
Release files / pdfs-0.1.0.tar.gz
| Download URL | pdfs-0.1.0.tar.gz |
|---|---|
| Size | 535.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
162e221076bd612d27f0b35717708f410f2d04424f085247a9557335963254b0
|
|
BLAKE2b-256 checksum How to use checksums |
b30599ac43fd0f859892f758afb4e31247014da45ace13fe0d50473e0fcc6138
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pdfs-0.1.0-py3.6.egg
| Download URL | pdfs-0.1.0-py3.6.egg |
|---|---|
| Size | 622.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
64dd7b9a3ad192a62e04b2ba07caccb1e3e5af62de18da289967718fbac5a7d7
|
|
BLAKE2b-256 checksum How to use checksums |
6ebcda6f7759bb56221e0c729638f2452d9b972e962a9a07da866b27f68a94a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pdfs-0.1.0-py3-none-any.whl
| Download URL | pdfs-0.1.0-py3-none-any.whl |
|---|---|
| Size | 550.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1b26eab4b5646b47320a38e664b9e7d2c793ea04691def6e7a4989fb1a675ba4
|
|
BLAKE2b-256 checksum How to use checksums |
6daf5a871cd3b553e8a5cd2c54239675dad529da5a56ac5e12f98c7a464ebf88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pdfs 0.1.0
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.