-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
96 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,96 @@ | ||
|
|
||
| Requirements Summary | ||
| ==================== | ||
|
|
||
| # default | ||
|
|
||
| ## As a user, I want to generate AIPs and SIPs using Registry ([#7](https://github.com/NASA-PDS/deep-archive/issues/7)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want the SIP manifest to include valid URLs ([#102](https://github.com/NASA-PDS/deep-archive/issues/102)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I would like to provide a custom base manifest URL ([#121](https://github.com/NASA-PDS/deep-archive/issues/121)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to automatically upload a deep archive package and open a new issue ([#122](https://github.com/NASA-PDS/deep-archive/issues/122)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user I want to generate a delta SIP (Submission Information Package) ([#125](https://github.com/NASA-PDS/deep-archive/issues/125)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to know that the software is still executing on long running jobs. ([#136](https://github.com/NASA-PDS/deep-archive/issues/136)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to produce deep archive products for deltas from a previous release ([#141](https://github.com/NASA-PDS/deep-archive/issues/141)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a developer, I want to know when the CI pipeline fails ([#143](https://github.com/NASA-PDS/deep-archive/issues/143)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want deep archive to support LBLX label extensions ([#157](https://github.com/NASA-PDS/deep-archive/issues/157)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a data custodian, I want the Deep Archive to work around invalid URLs in the Registry ([#162](https://github.com/NASA-PDS/deep-archive/issues/162)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to be warned when there are no non-aggregate products found in the registry ([#165](https://github.com/NASA-PDS/deep-archive/issues/165)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to include all versions of collections associated with a bundle referencing collections by LID using the Registry ([#181](https://github.com/NASA-PDS/deep-archive/issues/181)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| # NSSDCA-delivery-requirements | ||
|
|
||
| ## The tool shall be capable of generating a valid Archive Information Package transfer manifest and PDS4 XML label in accordance with the PDS4 Information Model ([#45](https://github.com/NASA-PDS/deep-archive/issues/45)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall be capable of generating a valid AIP and SIP products and PDS4 XML label in accordance with the PDS4 Information Model ([#46](https://github.com/NASA-PDS/deep-archive/issues/46)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall be capable of generating product manifests from an online Registry Service ([#47](https://github.com/NASA-PDS/deep-archive/issues/47)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall be capable of generating product manifests by crawling a file system using the information contained within the specified bundle and collection products ([#48](https://github.com/NASA-PDS/deep-archive/issues/48)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall generate a product manifest based upon the specification of a bundle as input ([#49](https://github.com/NASA-PDS/deep-archive/issues/49)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall include products in the manifests based upon the relationships described in the PDS4 bundle and collection metadata ([#50](https://github.com/NASA-PDS/deep-archive/issues/50)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall be capable of accepting a checksum manifest as input to use in place of Registry or on-demand product checksum generation ([#51](https://github.com/NASA-PDS/deep-archive/issues/51)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall generate a PDS4 label for the SIP and AIP using at least PDS4 Information Model v1.13.0.0 ([#52](https://github.com/NASA-PDS/deep-archive/issues/52)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The tool shall require AIP and SIP products contain only products with valid logical identifiers according to the PDS4 Standards Reference ([#53](https://github.com/NASA-PDS/deep-archive/issues/53)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## The Submission Information Package manifest shall be a tab-delimited table with one record per product and four fields per record containing the following fields: checksum value, checksum type, resolvable URL to data product, unique product lidvid for the associated product ([#54](https://github.com/NASA-PDS/deep-archive/issues/54)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version |