Culture Python Package
Latest schema.org : https://schema.org/version/latest/schemaorg-current-https.jsonld
NFDI4Culture
This is a placeholder for the Python tools being developed to manage the infrastructure of NFDI4Culture
Example:
from nfdi4culture import cto
from lidolator import from_file
item = cto.Item()
item.datafeed = "https://nfdi4culture.de/id/E5320"
# Or should we have cto.DataFeed("https://nfdi4culture.de/id/E5320") and the rest happens from there?
# either of the above will set things like .publisher on the Item too.
# and create the relevant schema.DataFeedItem and schema.DataFeed triples?
item.sourcefile = "http://foo.com/bar/baz.oai-pmh?id=123456"
# the update method expects a dict with key-value mappings
# the cto.Item objet knows how to map a key and value to the relevant fields.
# How do we specify this field mapping?
# And do we split it into a NamedNode/Literal difference?
item.update(from_file(filepath))
item.ntriples()
# or
item.turtle()
TODO
- JS is working on scraper
Open Discussion Points
Should we use RDFlib? While it is very much a "batteries included" package, for large datasets (which we increasingly want to create) it is just too slow.
Metadata
Release files for nfdi4culture 0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nfdi4culture-0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / nfdi4culture-0.3-py3-none-any.whl
| Download URL | nfdi4culture-0.3-py3-none-any.whl |
|---|---|
| Size | 263.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8757140e330dcd9168f2ec512f717c4f7708a33377bd0253230e04e46f16fb30
|
|
BLAKE2b-256 checksum How to use checksums |
43c21babad6c22e77481b8ccdb7eae1eee5a36a9959005ea6adac45bd8817894
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.11.9
|
Security for nfdi4culture 0.3
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.