This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.8.10 instead.
Reason given by maintainers: Missing dependency
dryad2dataverse
dryad2dataverse is a Python package and an associated console line application which allows easier transfer of metadata and data from a Dryad data repository (ie, https://datadryad.org) to a Dataverse repository. Dryad2dataverse is pure Python and should run on any platform which supports Python 3.6 or greater.
Data transfers between repositories require local storage, so not all platforms will be equally suitable.
Installing
pip install dryad2dataverse
Usage
Most users will likely just want to use the command line transfer and monitor tool (dryadd) but the tools are available in any Python environment
Command line application
dryadd [all the various options]
see all the options available with
dryadd -h
Initiate a transfer from a Dryad repository to a Dataverse repository.
Using the package
#Serializer
import dryad2dataverse.serializer
#Transfer
import dryad2dataverse.transfer
#Monitor
#import dryad2dataverse.monitor
i_heart_dryad = dryad2dataverse.serializer.Serializer('doi:10.5061/dryad.2rbnzs7jp')
dv = dryad2dataverse.transfer.Transfer(i_heart_dryad)
dv.download_files()
dv.upload_study(targetDv='dryad')
dv.upload_files()
#For an explanation look at the more detailed docs
#You know, like where your API key goes.
Documentation
This very terse description is by no means the entirety of the documentation. Complete plain text documentation is available in the docs directory of (https://github.com/ubc-library-rc/dryad2dataverse), beginning with index.md.
A (much) more user-friendly version of the documentation is available at https://ubc-library-rc.github.io/dryad2dataverse, including full dryadd documentation and API information.
Or if you've cloned the git repostory above, you can use mkdocs and mkdocs serve to have a local server version of the documentation.
1 maintainer
Metadata
1 maintainer
Release files for dryad2dataverse 0.8.9
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 | |
|---|---|---|---|---|
| dryad2dataverse-0.8.9.tar.gz | 39.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dryad2dataverse-0.8.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.7 kB
Release files / dryad2dataverse-0.8.9.tar.gz
| Download URL | dryad2dataverse-0.8.9.tar.gz |
|---|---|
| Size | 39.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c2c38115449ac705446e60e518b2d3c82ab23003e4b39d28f78d5bfc58488cd
|
|
BLAKE2b-256 checksum How to use checksums |
dd36c03ebd6060b0d9c061ca7f7bf7d0b1c3e2bf72202f74065582313f3c9fec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.13.17 Darwin/24.6.0
|
Release files / dryad2dataverse-0.8.9-py3-none-any.whl
| Download URL | dryad2dataverse-0.8.9-py3-none-any.whl |
|---|---|
| Size | 43.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7eac9823789fd70eed16d2aaa08b2ad588a0bf4c060193660566d35d40ab6b14
|
|
BLAKE2b-256 checksum How to use checksums |
869b84688a40a1ff0ce900186a5ed099f3462e83ac1ba1508399a86c1e0abd46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.13.17 Darwin/24.6.0
|
Security for dryad2dataverse 0.8.9
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.
