NASA PDS DOI Service
This tools provides services for PDS operators to mint DOIs.
Prerequisites
- python 3
- a login to OSTI server
User Documentation
https://nasa-pds.github.io/pds-doi-service/
Developers
Get the code and work on a branch
git clone ...
git checkout -b "#<issue number>"
Install virtual env
pip install virtualenv
python -m venv venv
source venv/bin/activate
Deploy dependancies:
pip install -r requirements_dev.txt
or
pip intall -e .
Launch api server (to be re-worked)
pds-doi-start-dev
Test
Unit tests:
python setup.py test
Behavioral testing
You first need to get some reference datasets, in the project base directory:
curl https://pds.nasa.gov/software/test-data/pds-doi-service/aaDOI_production_submitted_labels.zip > aaDOI_production_submitted_labels.zip
unzip aaDOI_production_submitted_labels.zip
Then you can run the behavioral tests:
behave
You can also run them for a nicer reporting:
behave -f allure_behave.formatter:AllureFormatter -o ./allure ./features
allure service allure
To report to testrail
Test report can be pushed to testrail: https://cae-testrail.jpl.nasa.gov/testrail/
Project: Planetary Data System (PDS) Test suite: pds-doi-service
Set you environment:
export TESTRAIL_USER=<your email in testrail>
export TESTRAIL_KEY=<your API key in tesrail>
Run the tests:
behave
See the results in https://cae-testrail.jpl.nasa.gov/testrail/index.php?/projects/overview/168
Documentation management
Design :
See in this repository:
https://github.com/NASA-PDS/pds-doi-service/tree/master/docs
User documentation
Managed with sphynx
brew install sphinx-doc
pip install -r requirements_dev.txt
cd docs
sphinx-build -b html source build -a
Build & Release
The build and release process is managed in github actions.
Metadata
Release files for pds-doi-core 1.0.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 |
|---|---|---|---|---|
| pds_doi_core-1.0.0.tar.gz | 63.1 kB | Without provenance | Details for pds_doi_core-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pds_doi_core-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for pds_doi_core-1.0.0-py3-none-any.whl |
Total release size: 157.0 kB
Release files / pds_doi_core-1.0.0.tar.gz
| Download URL | pds_doi_core-1.0.0.tar.gz |
|---|---|
| Size | 63.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55d5e898884c8b3bdd3436da88526d02d8ecb86cb9c525dce0e2c11d97c2ced7
|
|
BLAKE2b-256 checksum How to use checksums |
5dcbdd930a47af35e3672378ec28bf14df8c96b349531fabf2a2d1cadb512c19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.6
|
Release files / pds_doi_core-1.0.0-py3-none-any.whl
| Download URL | pds_doi_core-1.0.0-py3-none-any.whl |
|---|---|
| Size | 94.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1bbe3540570d8dd54f8298ea5c2eda335eb13e31ad616a7dc2dcee4c0b27eae2
|
|
BLAKE2b-256 checksum How to use checksums |
ea7a2138c2cccd84c0af419e1e0198807106b2a009383d323f2c49c76e420d7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.6
|
Security for pds-doi-core 1.0.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.