From 0a00458f8580235b2990f6d0f6a8785e26745113 Mon Sep 17 00:00:00 2001 From: Jordan Padams <33492486+jordanpadams@users.noreply.github.com> Date: Thu, 16 Jun 2022 00:17:08 -0700 Subject: [PATCH] Add branch continuous integration (#333) * Add CI testing to branches * Add checkout of repo * Add shell * Add python version * Fix linter issues * Upgrade black dependency to fix bug Fixes bug that appears when trying to run pre-commit ImportError: cannot import name '_unicodefun' from 'click' --- .github/workflows/branch-cicd.yaml | 76 ++++++++++++++ .pre-commit-config.yaml | 2 +- docs/requirements/v2.1.3/REQUIREMENTS.md | 104 +++++++++---------- docs/requirements/v2.1.4-dev/REQUIREMENTS.md | 104 +++++++++---------- 4 files changed, 181 insertions(+), 105 deletions(-) create mode 100644 .github/workflows/branch-cicd.yaml diff --git a/.github/workflows/branch-cicd.yaml b/.github/workflows/branch-cicd.yaml new file mode 100644 index 00000000..2aacbe12 --- /dev/null +++ b/.github/workflows/branch-cicd.yaml @@ -0,0 +1,76 @@ +# 🏃‍♀️ Continuous Integration and Delivery: Branch Testing +# ====================================================== + + +--- + +name: 🔁 Branch integration testing + + +# Driving Event +# ------------- +# +# What event starts this workflow: a push to any branch other than main + +on: + push: + branches: + - '**' + - '!main' + + +# What to Do +# ---------- +# +# Test the software with tox + +jobs: + branch-testing: + name: 🪵 Branch Testing + runs-on: ubuntu-latest + if: github.actor != 'pdsen-ci' + + steps: + - + name: 💳 Checkout + uses: actions/checkout@v2 + with: + lfs: true + fetch-depth: 0 + token: ${{secrets.ADMIN_GITHUB_TOKEN}} + - + name: Set up Python 3 + uses: actions/setup-python@v1 + with: + python-version: '3.9' + - + name: 💵 Python Cache + uses: actions/cache@v2 + with: + path: ~/.cache/pip + # The "key" used to indicate a set of cached files is the operating system runner + # plus "py" for Python-specific builds, plus a hash of the wheels, plus "pds" because + # we pds-prefix everything with "pds" in PDS! 😅 + key: pds-${{runner.os}}-py-${{hashFiles('**/*.whl')}} + # To restore a set of files, we only need to match a prefix of the saved key. + restore-keys: pds-${{runner.os}}-py- + - + name: Update default configuration + run: | + import sys + import os + print("Running python version {}".format(sys.version)) + conf_file = "pds_doi_service.ini" + print("Create config file for unit test {}".format(conf_file)) + with open(conf_file, "w") as f: + f.write("[OSTI]\n") + f.write("user = {}\n".format("${{secrets.osti_login}}")) + f.write("password = {}\n".format("${{secrets.osti_password}}")) + shell: python + - + name: 🩺 Test Software + run: + pip install --editable '.[dev]' + + tox + shell: bash diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 40a22fa0..b543eb4b 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -36,7 +36,7 @@ repos: ] - repo: https://github.com/python/black - rev: 21.7b0 + rev: 22.3.0 hooks: - id: black files: ^src/|tests/ diff --git a/docs/requirements/v2.1.3/REQUIREMENTS.md b/docs/requirements/v2.1.3/REQUIREMENTS.md index 1d2ab678..4734025e 100644 --- a/docs/requirements/v2.1.3/REQUIREMENTS.md +++ b/docs/requirements/v2.1.3/REQUIREMENTS.md @@ -4,215 +4,215 @@ Requirements Summary # DOI management -## The software shall be capable of accepting a request to create a draft DOI. ([#5](https://github.com/NASA-PDS/doi-service/issues/5)) +## The software shall be capable of accepting a request to create a draft DOI. ([#5](https://github.com/NASA-PDS/doi-service/issues/5)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to reserve a DOI. ([#6](https://github.com/NASA-PDS/doi-service/issues/6)) +## The software shall be capable of accepting a request to reserve a DOI. ([#6](https://github.com/NASA-PDS/doi-service/issues/6)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to release a DOI. ([#7](https://github.com/NASA-PDS/doi-service/issues/7)) +## The software shall be capable of accepting a request to release a DOI. ([#7](https://github.com/NASA-PDS/doi-service/issues/7)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to deactivate a DOI. ([#8](https://github.com/NASA-PDS/doi-service/issues/8)) +## The software shall be capable of accepting a request to deactivate a DOI. ([#8](https://github.com/NASA-PDS/doi-service/issues/8)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to update DOI metadata. ([#9](https://github.com/NASA-PDS/doi-service/issues/9)) +## The software shall be capable of accepting a request to update DOI metadata. ([#9](https://github.com/NASA-PDS/doi-service/issues/9)) This requirement is not impacted by the current version -## The software shall be capable of batch processing >1 DOI requests. ([#10](https://github.com/NASA-PDS/doi-service/issues/10)) +## The software shall be capable of batch processing >1 DOI requests. ([#10](https://github.com/NASA-PDS/doi-service/issues/10)) This requirement is not impacted by the current version # DOI metadata -## The software shall be capable of autonomously generating the minimum set of DOI metadata from PDS4 Collection, Bundle, Document products. ([#11](https://github.com/NASA-PDS/doi-service/issues/11)) +## The software shall be capable of autonomously generating the minimum set of DOI metadata from PDS4 Collection, Bundle, Document products. ([#11](https://github.com/NASA-PDS/doi-service/issues/11)) This requirement is not impacted by the current version -## The software shall validate a minimum set of metadata is provided when reserving, releasing, or updating a DOI. This minimum set of metadata will be defined by the PDS DOI Working Group. ([#12](https://github.com/NASA-PDS/doi-service/issues/12)) +## The software shall validate a minimum set of metadata is provided when reserving, releasing, or updating a DOI. This minimum set of metadata will be defined by the PDS DOI Working Group. ([#12](https://github.com/NASA-PDS/doi-service/issues/12)) This requirement is not impacted by the current version -## The software shall validate the DOI metadata when reserving, releasing, or updating a DOI. ([#13](https://github.com/NASA-PDS/doi-service/issues/13)) +## The software shall validate the DOI metadata when reserving, releasing, or updating a DOI. ([#13](https://github.com/NASA-PDS/doi-service/issues/13)) This requirement is not impacted by the current version # DOI interface support -## The software shall maintain a database of PDS DOIs and their current state. ([#14](https://github.com/NASA-PDS/doi-service/issues/14)) +## The software shall maintain a database of PDS DOIs and their current state. ([#14](https://github.com/NASA-PDS/doi-service/issues/14)) This requirement is not impacted by the current version -## The software shall maintain the ability to manage DOIs through OSTI ([#15](https://github.com/NASA-PDS/doi-service/issues/15)) +## The software shall maintain the ability to manage DOIs through OSTI ([#15](https://github.com/NASA-PDS/doi-service/issues/15)) This requirement is not impacted by the current version -## The software shall maintain the ability to manage DOIs through DataCite. ([#16](https://github.com/NASA-PDS/doi-service/issues/16)) +## The software shall maintain the ability to manage DOIs through DataCite. ([#16](https://github.com/NASA-PDS/doi-service/issues/16)) This requirement is not impacted by the current version # DOI-management -## The software shall provide a Status capability that will allow a user to query for the current status of a DOI ([#30](https://github.com/NASA-PDS/doi-service/issues/30)) +## The software shall provide a Status capability that will allow a user to query for the current status of a DOI ([#30](https://github.com/NASA-PDS/doi-service/issues/30)) This requirement is not impacted by the current version -## The software shall provide the capability of producing a DOI Status Report based upon a user-specified query ([#35](https://github.com/NASA-PDS/doi-service/issues/35)) +## The software shall provide the capability of producing a DOI Status Report based upon a user-specified query ([#35](https://github.com/NASA-PDS/doi-service/issues/35)) This requirement is not impacted by the current version # default -## As a node operator, I want to include a DOI as a related identifier in the DOI metadata for parent PDS4 products. ([#69](https://github.com/NASA-PDS/doi-service/issues/69)) +## As a node operator, I want to include a DOI as a related identifier in the DOI metadata for parent PDS4 products. ([#69](https://github.com/NASA-PDS/doi-service/issues/69)) This requirement is not impacted by the current version -## As a user, I want the DOI metadata for a product to be automatically updated when I have a new version of an accumulating bundle / collection. ([#97](https://github.com/NASA-PDS/doi-service/issues/97)) +## As a user, I want the DOI metadata for a product to be automatically updated when I have a new version of an accumulating bundle / collection. ([#97](https://github.com/NASA-PDS/doi-service/issues/97)) This requirement is not impacted by the current version -## As the PDS, I want to mint DOIs through DataCite ([#103](https://github.com/NASA-PDS/doi-service/issues/103)) +## As the PDS, I want to mint DOIs through DataCite ([#103](https://github.com/NASA-PDS/doi-service/issues/103)) This requirement is not impacted by the current version -## As a user, I want to see the lidvid of my DOIs in the email report ([#167](https://github.com/NASA-PDS/doi-service/issues/167)) +## As a user, I want to see the lidvid of my DOIs in the email report ([#167](https://github.com/NASA-PDS/doi-service/issues/167)) This requirement is not impacted by the current version -## As an operator, I want to reserve a DOI through DataCite ([#171](https://github.com/NASA-PDS/doi-service/issues/171)) +## As an operator, I want to reserve a DOI through DataCite ([#171](https://github.com/NASA-PDS/doi-service/issues/171)) This requirement is not impacted by the current version -## As an operator, I want query for one or more minted DOIs from DataCite ([#172](https://github.com/NASA-PDS/doi-service/issues/172)) +## As an operator, I want query for one or more minted DOIs from DataCite ([#172](https://github.com/NASA-PDS/doi-service/issues/172)) This requirement is not impacted by the current version -## As an operator, I want to query for a DOI's change history through DataCite ([#173](https://github.com/NASA-PDS/doi-service/issues/173)) +## As an operator, I want to query for a DOI's change history through DataCite ([#173](https://github.com/NASA-PDS/doi-service/issues/173)) This requirement is not impacted by the current version -## As an operator, I want to release a DOI through DataCite ([#174](https://github.com/NASA-PDS/doi-service/issues/174)) +## As an operator, I want to release a DOI through DataCite ([#174](https://github.com/NASA-PDS/doi-service/issues/174)) This requirement is not impacted by the current version -## As an operator, I want to update DOI metadata through DataCite ([#175](https://github.com/NASA-PDS/doi-service/issues/175)) +## As an operator, I want to update DOI metadata through DataCite ([#175](https://github.com/NASA-PDS/doi-service/issues/175)) This requirement is not impacted by the current version -## As an API user, I want to have pagination that is consistent with the PDS API. ([#176](https://github.com/NASA-PDS/doi-service/issues/176)) +## As an API user, I want to have pagination that is consistent with the PDS API. ([#176](https://github.com/NASA-PDS/doi-service/issues/176)) This requirement is not impacted by the current version -## As an API user I want to filter on lidvids with wildcards ([#177](https://github.com/NASA-PDS/doi-service/issues/177)) +## As an API user I want to filter on lidvids with wildcards ([#177](https://github.com/NASA-PDS/doi-service/issues/177)) This requirement is not impacted by the current version -## As an API user I want to filter on PDS3 Data Set IDs with wildcards ([#180](https://github.com/NASA-PDS/doi-service/issues/180)) +## As an API user I want to filter on PDS3 Data Set IDs with wildcards ([#180](https://github.com/NASA-PDS/doi-service/issues/180)) This requirement is not impacted by the current version -## As a user of the API, I want to see the DOI's title when I go GET /dois request ([#183](https://github.com/NASA-PDS/doi-service/issues/183)) +## As a user of the API, I want to see the DOI's title when I go GET /dois request ([#183](https://github.com/NASA-PDS/doi-service/issues/183)) This requirement is not impacted by the current version -## As an API user, I want to always have an update date for the DOIs ([#184](https://github.com/NASA-PDS/doi-service/issues/184)) +## As an API user, I want to always have an update date for the DOIs ([#184](https://github.com/NASA-PDS/doi-service/issues/184)) This requirement is not impacted by the current version -## As a SA, I want the operational deployment of the service to be secure ([#187](https://github.com/NASA-PDS/doi-service/issues/187)) +## As a SA, I want the operational deployment of the service to be secure ([#187](https://github.com/NASA-PDS/doi-service/issues/187)) This requirement is not impacted by the current version -## As a user, I want the application to support the history of PDS's DOIs, especially the one created for PDS3 products ([#192](https://github.com/NASA-PDS/doi-service/issues/192)) +## As a user, I want the application to support the history of PDS's DOIs, especially the one created for PDS3 products ([#192](https://github.com/NASA-PDS/doi-service/issues/192)) This requirement is not impacted by the current version -## As a system administrator, I want to be able to deploy pds_doi_service with python 3.6 ([#197](https://github.com/NASA-PDS/doi-service/issues/197)) +## As a system administrator, I want to be able to deploy pds_doi_service with python 3.6 ([#197](https://github.com/NASA-PDS/doi-service/issues/197)) This requirement is not impacted by the current version -## As a user, I want to use the API with ids containing a slash (/) ([#198](https://github.com/NASA-PDS/doi-service/issues/198)) +## As a user, I want to use the API with ids containing a slash (/) ([#198](https://github.com/NASA-PDS/doi-service/issues/198)) This requirement is not impacted by the current version -## As an operator, I want to know what version of the software I am running ([#200](https://github.com/NASA-PDS/doi-service/issues/200)) +## As an operator, I want to know what version of the software I am running ([#200](https://github.com/NASA-PDS/doi-service/issues/200)) This requirement is not impacted by the current version -## As an operator, I want to know how to deploy and use the API from the Sphinx documentation ([#201](https://github.com/NASA-PDS/doi-service/issues/201)) +## As an operator, I want to know how to deploy and use the API from the Sphinx documentation ([#201](https://github.com/NASA-PDS/doi-service/issues/201)) This requirement is not impacted by the current version -## As an operator, I want one place to go for all DOI Service / API / UI documentation ([#202](https://github.com/NASA-PDS/doi-service/issues/202)) +## As an operator, I want one place to go for all DOI Service / API / UI documentation ([#202](https://github.com/NASA-PDS/doi-service/issues/202)) This requirement is not impacted by the current version -## As a user of the command line, I don't want to see all the log info in the stdout ([#206](https://github.com/NASA-PDS/doi-service/issues/206)) +## As a user of the command line, I don't want to see all the log info in the stdout ([#206](https://github.com/NASA-PDS/doi-service/issues/206)) This requirement is not impacted by the current version -## As a command-line user, I want to be suggested to use -f option when a Warning exception is raised ([#207](https://github.com/NASA-PDS/doi-service/issues/207)) +## As a command-line user, I want to be suggested to use -f option when a Warning exception is raised ([#207](https://github.com/NASA-PDS/doi-service/issues/207)) This requirement is not impacted by the current version -## As a user, I want to run the commandline on windows ([#212](https://github.com/NASA-PDS/doi-service/issues/212)) +## As a user, I want to run the commandline on windows ([#212](https://github.com/NASA-PDS/doi-service/issues/212)) This requirement is not impacted by the current version -## As a user, I want to search dois without case sensitiveness ([#223](https://github.com/NASA-PDS/doi-service/issues/223)) +## As a user, I want to search dois without case sensitiveness ([#223](https://github.com/NASA-PDS/doi-service/issues/223)) This requirement is not impacted by the current version -## As a user, I would like to include licensing information with all PDS DOIs ([#224](https://github.com/NASA-PDS/doi-service/issues/224)) +## As a user, I would like to include licensing information with all PDS DOIs ([#224](https://github.com/NASA-PDS/doi-service/issues/224)) This requirement is not impacted by the current version -## As an admistrator of the application, I want to restrict access to API by specific referrer ([#228](https://github.com/NASA-PDS/doi-service/issues/228)) +## As an admistrator of the application, I want to restrict access to API by specific referrer ([#228](https://github.com/NASA-PDS/doi-service/issues/228)) This requirement is not impacted by the current version -## As a user, I want to include related DOIs in DOI metadata ([#232](https://github.com/NASA-PDS/doi-service/issues/232)) +## As a user, I want to include related DOIs in DOI metadata ([#232](https://github.com/NASA-PDS/doi-service/issues/232)) This requirement is not impacted by the current version -## As a PDS Operator, I want to perform a bulk update of a specific field across many DOI records ([#257](https://github.com/NASA-PDS/doi-service/issues/257)) +## As a PDS Operator, I want to perform a bulk update of a specific field across many DOI records ([#257](https://github.com/NASA-PDS/doi-service/issues/257)) This requirement is not impacted by the current version -## As a user, I want to search for ids without case sensitiviy ([#271](https://github.com/NASA-PDS/doi-service/issues/271)) +## As a user, I want to search for ids without case sensitiviy ([#271](https://github.com/NASA-PDS/doi-service/issues/271)) This requirement is not impacted by the current version -## As a user, I want to update the LIDVID associated with a DOI ([#278](https://github.com/NASA-PDS/doi-service/issues/278)) +## As a user, I want to update the LIDVID associated with a DOI ([#278](https://github.com/NASA-PDS/doi-service/issues/278)) This requirement is not impacted by the current version -## As a user, I want to update the bundle/collection metadata associated with a DOI for accumulating data sets ([#279](https://github.com/NASA-PDS/doi-service/issues/279)) +## As a user, I want to update the bundle/collection metadata associated with a DOI for accumulating data sets ([#279](https://github.com/NASA-PDS/doi-service/issues/279)) This requirement is not impacted by the current version -## As an API user, I want to know the status value which can be expected ([#280](https://github.com/NASA-PDS/doi-service/issues/280)) +## As an API user, I want to know the status value which can be expected ([#280](https://github.com/NASA-PDS/doi-service/issues/280)) This requirement is not impacted by the current version -## As a user, I want a simplified DOI lifecycle workflow ([#286](https://github.com/NASA-PDS/doi-service/issues/286)) +## As a user, I want a simplified DOI lifecycle workflow ([#286](https://github.com/NASA-PDS/doi-service/issues/286)) This requirement is not impacted by the current version -## Update default values to sync with SBN documentation ([#295](https://github.com/NASA-PDS/doi-service/issues/295)) +## Update default values to sync with SBN documentation ([#295](https://github.com/NASA-PDS/doi-service/issues/295)) This requirement is not impacted by the current version -## As a user, I want to sort by DOI, title, or identifier. ([#306](https://github.com/NASA-PDS/doi-service/issues/306)) +## As a user, I want to sort by DOI, title, or identifier. ([#306](https://github.com/NASA-PDS/doi-service/issues/306)) This requirement is not impacted by the current version -## Add Radio Science to set of possible nodes ([#317](https://github.com/NASA-PDS/doi-service/issues/317)) +## Add Radio Science to set of possible nodes ([#317](https://github.com/NASA-PDS/doi-service/issues/317)) -This requirement is not impacted by the current version \ No newline at end of file +This requirement is not impacted by the current version diff --git a/docs/requirements/v2.1.4-dev/REQUIREMENTS.md b/docs/requirements/v2.1.4-dev/REQUIREMENTS.md index 1d2ab678..4734025e 100644 --- a/docs/requirements/v2.1.4-dev/REQUIREMENTS.md +++ b/docs/requirements/v2.1.4-dev/REQUIREMENTS.md @@ -4,215 +4,215 @@ Requirements Summary # DOI management -## The software shall be capable of accepting a request to create a draft DOI. ([#5](https://github.com/NASA-PDS/doi-service/issues/5)) +## The software shall be capable of accepting a request to create a draft DOI. ([#5](https://github.com/NASA-PDS/doi-service/issues/5)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to reserve a DOI. ([#6](https://github.com/NASA-PDS/doi-service/issues/6)) +## The software shall be capable of accepting a request to reserve a DOI. ([#6](https://github.com/NASA-PDS/doi-service/issues/6)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to release a DOI. ([#7](https://github.com/NASA-PDS/doi-service/issues/7)) +## The software shall be capable of accepting a request to release a DOI. ([#7](https://github.com/NASA-PDS/doi-service/issues/7)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to deactivate a DOI. ([#8](https://github.com/NASA-PDS/doi-service/issues/8)) +## The software shall be capable of accepting a request to deactivate a DOI. ([#8](https://github.com/NASA-PDS/doi-service/issues/8)) This requirement is not impacted by the current version -## The software shall be capable of accepting a request to update DOI metadata. ([#9](https://github.com/NASA-PDS/doi-service/issues/9)) +## The software shall be capable of accepting a request to update DOI metadata. ([#9](https://github.com/NASA-PDS/doi-service/issues/9)) This requirement is not impacted by the current version -## The software shall be capable of batch processing >1 DOI requests. ([#10](https://github.com/NASA-PDS/doi-service/issues/10)) +## The software shall be capable of batch processing >1 DOI requests. ([#10](https://github.com/NASA-PDS/doi-service/issues/10)) This requirement is not impacted by the current version # DOI metadata -## The software shall be capable of autonomously generating the minimum set of DOI metadata from PDS4 Collection, Bundle, Document products. ([#11](https://github.com/NASA-PDS/doi-service/issues/11)) +## The software shall be capable of autonomously generating the minimum set of DOI metadata from PDS4 Collection, Bundle, Document products. ([#11](https://github.com/NASA-PDS/doi-service/issues/11)) This requirement is not impacted by the current version -## The software shall validate a minimum set of metadata is provided when reserving, releasing, or updating a DOI. This minimum set of metadata will be defined by the PDS DOI Working Group. ([#12](https://github.com/NASA-PDS/doi-service/issues/12)) +## The software shall validate a minimum set of metadata is provided when reserving, releasing, or updating a DOI. This minimum set of metadata will be defined by the PDS DOI Working Group. ([#12](https://github.com/NASA-PDS/doi-service/issues/12)) This requirement is not impacted by the current version -## The software shall validate the DOI metadata when reserving, releasing, or updating a DOI. ([#13](https://github.com/NASA-PDS/doi-service/issues/13)) +## The software shall validate the DOI metadata when reserving, releasing, or updating a DOI. ([#13](https://github.com/NASA-PDS/doi-service/issues/13)) This requirement is not impacted by the current version # DOI interface support -## The software shall maintain a database of PDS DOIs and their current state. ([#14](https://github.com/NASA-PDS/doi-service/issues/14)) +## The software shall maintain a database of PDS DOIs and their current state. ([#14](https://github.com/NASA-PDS/doi-service/issues/14)) This requirement is not impacted by the current version -## The software shall maintain the ability to manage DOIs through OSTI ([#15](https://github.com/NASA-PDS/doi-service/issues/15)) +## The software shall maintain the ability to manage DOIs through OSTI ([#15](https://github.com/NASA-PDS/doi-service/issues/15)) This requirement is not impacted by the current version -## The software shall maintain the ability to manage DOIs through DataCite. ([#16](https://github.com/NASA-PDS/doi-service/issues/16)) +## The software shall maintain the ability to manage DOIs through DataCite. ([#16](https://github.com/NASA-PDS/doi-service/issues/16)) This requirement is not impacted by the current version # DOI-management -## The software shall provide a Status capability that will allow a user to query for the current status of a DOI ([#30](https://github.com/NASA-PDS/doi-service/issues/30)) +## The software shall provide a Status capability that will allow a user to query for the current status of a DOI ([#30](https://github.com/NASA-PDS/doi-service/issues/30)) This requirement is not impacted by the current version -## The software shall provide the capability of producing a DOI Status Report based upon a user-specified query ([#35](https://github.com/NASA-PDS/doi-service/issues/35)) +## The software shall provide the capability of producing a DOI Status Report based upon a user-specified query ([#35](https://github.com/NASA-PDS/doi-service/issues/35)) This requirement is not impacted by the current version # default -## As a node operator, I want to include a DOI as a related identifier in the DOI metadata for parent PDS4 products. ([#69](https://github.com/NASA-PDS/doi-service/issues/69)) +## As a node operator, I want to include a DOI as a related identifier in the DOI metadata for parent PDS4 products. ([#69](https://github.com/NASA-PDS/doi-service/issues/69)) This requirement is not impacted by the current version -## As a user, I want the DOI metadata for a product to be automatically updated when I have a new version of an accumulating bundle / collection. ([#97](https://github.com/NASA-PDS/doi-service/issues/97)) +## As a user, I want the DOI metadata for a product to be automatically updated when I have a new version of an accumulating bundle / collection. ([#97](https://github.com/NASA-PDS/doi-service/issues/97)) This requirement is not impacted by the current version -## As the PDS, I want to mint DOIs through DataCite ([#103](https://github.com/NASA-PDS/doi-service/issues/103)) +## As the PDS, I want to mint DOIs through DataCite ([#103](https://github.com/NASA-PDS/doi-service/issues/103)) This requirement is not impacted by the current version -## As a user, I want to see the lidvid of my DOIs in the email report ([#167](https://github.com/NASA-PDS/doi-service/issues/167)) +## As a user, I want to see the lidvid of my DOIs in the email report ([#167](https://github.com/NASA-PDS/doi-service/issues/167)) This requirement is not impacted by the current version -## As an operator, I want to reserve a DOI through DataCite ([#171](https://github.com/NASA-PDS/doi-service/issues/171)) +## As an operator, I want to reserve a DOI through DataCite ([#171](https://github.com/NASA-PDS/doi-service/issues/171)) This requirement is not impacted by the current version -## As an operator, I want query for one or more minted DOIs from DataCite ([#172](https://github.com/NASA-PDS/doi-service/issues/172)) +## As an operator, I want query for one or more minted DOIs from DataCite ([#172](https://github.com/NASA-PDS/doi-service/issues/172)) This requirement is not impacted by the current version -## As an operator, I want to query for a DOI's change history through DataCite ([#173](https://github.com/NASA-PDS/doi-service/issues/173)) +## As an operator, I want to query for a DOI's change history through DataCite ([#173](https://github.com/NASA-PDS/doi-service/issues/173)) This requirement is not impacted by the current version -## As an operator, I want to release a DOI through DataCite ([#174](https://github.com/NASA-PDS/doi-service/issues/174)) +## As an operator, I want to release a DOI through DataCite ([#174](https://github.com/NASA-PDS/doi-service/issues/174)) This requirement is not impacted by the current version -## As an operator, I want to update DOI metadata through DataCite ([#175](https://github.com/NASA-PDS/doi-service/issues/175)) +## As an operator, I want to update DOI metadata through DataCite ([#175](https://github.com/NASA-PDS/doi-service/issues/175)) This requirement is not impacted by the current version -## As an API user, I want to have pagination that is consistent with the PDS API. ([#176](https://github.com/NASA-PDS/doi-service/issues/176)) +## As an API user, I want to have pagination that is consistent with the PDS API. ([#176](https://github.com/NASA-PDS/doi-service/issues/176)) This requirement is not impacted by the current version -## As an API user I want to filter on lidvids with wildcards ([#177](https://github.com/NASA-PDS/doi-service/issues/177)) +## As an API user I want to filter on lidvids with wildcards ([#177](https://github.com/NASA-PDS/doi-service/issues/177)) This requirement is not impacted by the current version -## As an API user I want to filter on PDS3 Data Set IDs with wildcards ([#180](https://github.com/NASA-PDS/doi-service/issues/180)) +## As an API user I want to filter on PDS3 Data Set IDs with wildcards ([#180](https://github.com/NASA-PDS/doi-service/issues/180)) This requirement is not impacted by the current version -## As a user of the API, I want to see the DOI's title when I go GET /dois request ([#183](https://github.com/NASA-PDS/doi-service/issues/183)) +## As a user of the API, I want to see the DOI's title when I go GET /dois request ([#183](https://github.com/NASA-PDS/doi-service/issues/183)) This requirement is not impacted by the current version -## As an API user, I want to always have an update date for the DOIs ([#184](https://github.com/NASA-PDS/doi-service/issues/184)) +## As an API user, I want to always have an update date for the DOIs ([#184](https://github.com/NASA-PDS/doi-service/issues/184)) This requirement is not impacted by the current version -## As a SA, I want the operational deployment of the service to be secure ([#187](https://github.com/NASA-PDS/doi-service/issues/187)) +## As a SA, I want the operational deployment of the service to be secure ([#187](https://github.com/NASA-PDS/doi-service/issues/187)) This requirement is not impacted by the current version -## As a user, I want the application to support the history of PDS's DOIs, especially the one created for PDS3 products ([#192](https://github.com/NASA-PDS/doi-service/issues/192)) +## As a user, I want the application to support the history of PDS's DOIs, especially the one created for PDS3 products ([#192](https://github.com/NASA-PDS/doi-service/issues/192)) This requirement is not impacted by the current version -## As a system administrator, I want to be able to deploy pds_doi_service with python 3.6 ([#197](https://github.com/NASA-PDS/doi-service/issues/197)) +## As a system administrator, I want to be able to deploy pds_doi_service with python 3.6 ([#197](https://github.com/NASA-PDS/doi-service/issues/197)) This requirement is not impacted by the current version -## As a user, I want to use the API with ids containing a slash (/) ([#198](https://github.com/NASA-PDS/doi-service/issues/198)) +## As a user, I want to use the API with ids containing a slash (/) ([#198](https://github.com/NASA-PDS/doi-service/issues/198)) This requirement is not impacted by the current version -## As an operator, I want to know what version of the software I am running ([#200](https://github.com/NASA-PDS/doi-service/issues/200)) +## As an operator, I want to know what version of the software I am running ([#200](https://github.com/NASA-PDS/doi-service/issues/200)) This requirement is not impacted by the current version -## As an operator, I want to know how to deploy and use the API from the Sphinx documentation ([#201](https://github.com/NASA-PDS/doi-service/issues/201)) +## As an operator, I want to know how to deploy and use the API from the Sphinx documentation ([#201](https://github.com/NASA-PDS/doi-service/issues/201)) This requirement is not impacted by the current version -## As an operator, I want one place to go for all DOI Service / API / UI documentation ([#202](https://github.com/NASA-PDS/doi-service/issues/202)) +## As an operator, I want one place to go for all DOI Service / API / UI documentation ([#202](https://github.com/NASA-PDS/doi-service/issues/202)) This requirement is not impacted by the current version -## As a user of the command line, I don't want to see all the log info in the stdout ([#206](https://github.com/NASA-PDS/doi-service/issues/206)) +## As a user of the command line, I don't want to see all the log info in the stdout ([#206](https://github.com/NASA-PDS/doi-service/issues/206)) This requirement is not impacted by the current version -## As a command-line user, I want to be suggested to use -f option when a Warning exception is raised ([#207](https://github.com/NASA-PDS/doi-service/issues/207)) +## As a command-line user, I want to be suggested to use -f option when a Warning exception is raised ([#207](https://github.com/NASA-PDS/doi-service/issues/207)) This requirement is not impacted by the current version -## As a user, I want to run the commandline on windows ([#212](https://github.com/NASA-PDS/doi-service/issues/212)) +## As a user, I want to run the commandline on windows ([#212](https://github.com/NASA-PDS/doi-service/issues/212)) This requirement is not impacted by the current version -## As a user, I want to search dois without case sensitiveness ([#223](https://github.com/NASA-PDS/doi-service/issues/223)) +## As a user, I want to search dois without case sensitiveness ([#223](https://github.com/NASA-PDS/doi-service/issues/223)) This requirement is not impacted by the current version -## As a user, I would like to include licensing information with all PDS DOIs ([#224](https://github.com/NASA-PDS/doi-service/issues/224)) +## As a user, I would like to include licensing information with all PDS DOIs ([#224](https://github.com/NASA-PDS/doi-service/issues/224)) This requirement is not impacted by the current version -## As an admistrator of the application, I want to restrict access to API by specific referrer ([#228](https://github.com/NASA-PDS/doi-service/issues/228)) +## As an admistrator of the application, I want to restrict access to API by specific referrer ([#228](https://github.com/NASA-PDS/doi-service/issues/228)) This requirement is not impacted by the current version -## As a user, I want to include related DOIs in DOI metadata ([#232](https://github.com/NASA-PDS/doi-service/issues/232)) +## As a user, I want to include related DOIs in DOI metadata ([#232](https://github.com/NASA-PDS/doi-service/issues/232)) This requirement is not impacted by the current version -## As a PDS Operator, I want to perform a bulk update of a specific field across many DOI records ([#257](https://github.com/NASA-PDS/doi-service/issues/257)) +## As a PDS Operator, I want to perform a bulk update of a specific field across many DOI records ([#257](https://github.com/NASA-PDS/doi-service/issues/257)) This requirement is not impacted by the current version -## As a user, I want to search for ids without case sensitiviy ([#271](https://github.com/NASA-PDS/doi-service/issues/271)) +## As a user, I want to search for ids without case sensitiviy ([#271](https://github.com/NASA-PDS/doi-service/issues/271)) This requirement is not impacted by the current version -## As a user, I want to update the LIDVID associated with a DOI ([#278](https://github.com/NASA-PDS/doi-service/issues/278)) +## As a user, I want to update the LIDVID associated with a DOI ([#278](https://github.com/NASA-PDS/doi-service/issues/278)) This requirement is not impacted by the current version -## As a user, I want to update the bundle/collection metadata associated with a DOI for accumulating data sets ([#279](https://github.com/NASA-PDS/doi-service/issues/279)) +## As a user, I want to update the bundle/collection metadata associated with a DOI for accumulating data sets ([#279](https://github.com/NASA-PDS/doi-service/issues/279)) This requirement is not impacted by the current version -## As an API user, I want to know the status value which can be expected ([#280](https://github.com/NASA-PDS/doi-service/issues/280)) +## As an API user, I want to know the status value which can be expected ([#280](https://github.com/NASA-PDS/doi-service/issues/280)) This requirement is not impacted by the current version -## As a user, I want a simplified DOI lifecycle workflow ([#286](https://github.com/NASA-PDS/doi-service/issues/286)) +## As a user, I want a simplified DOI lifecycle workflow ([#286](https://github.com/NASA-PDS/doi-service/issues/286)) This requirement is not impacted by the current version -## Update default values to sync with SBN documentation ([#295](https://github.com/NASA-PDS/doi-service/issues/295)) +## Update default values to sync with SBN documentation ([#295](https://github.com/NASA-PDS/doi-service/issues/295)) This requirement is not impacted by the current version -## As a user, I want to sort by DOI, title, or identifier. ([#306](https://github.com/NASA-PDS/doi-service/issues/306)) +## As a user, I want to sort by DOI, title, or identifier. ([#306](https://github.com/NASA-PDS/doi-service/issues/306)) This requirement is not impacted by the current version -## Add Radio Science to set of possible nodes ([#317](https://github.com/NASA-PDS/doi-service/issues/317)) +## Add Radio Science to set of possible nodes ([#317](https://github.com/NASA-PDS/doi-service/issues/317)) -This requirement is not impacted by the current version \ No newline at end of file +This requirement is not impacted by the current version