-
Notifications
You must be signed in to change notification settings - Fork 12
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
158 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,158 @@ | ||
|
|
||
| Requirements Summary | ||
| ==================== | ||
|
|
||
| # default | ||
|
|
||
| ## As a user, I want to execute content validation against every nth file ([#1](https://github.com/NASA-PDS/validate/issues/1)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want validate reporting output to support DD_Rule Report rule_type ([#13](https://github.com/NASA-PDS/validate/issues/13)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## Verify that all name/type attribute values correspond to names denoted context products ([#15](https://github.com/NASA-PDS/validate/issues/15)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to raise a FATAL error when a catalog file is invalid ([#16](https://github.com/NASA-PDS/validate/issues/16)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to be automatically notified when running validate that a newer version of the software is available ([#44](https://github.com/NASA-PDS/validate/issues/44)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## Add new target-manifest flag for user to provide a manifest (file) of file/directory paths to validate ([#50](https://github.com/NASA-PDS/validate/issues/50)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to be warned when there are alphanumeric characters between fields in Table_Character ([#57](https://github.com/NASA-PDS/validate/issues/57)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## Validate Table_Character groups and their specified lengths match the specified group_length ([#63](https://github.com/NASA-PDS/validate/issues/63)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate that all context objects specified in observational products are referenced in the parent bundle/collection Reference_List ([#69](https://github.com/NASA-PDS/validate/issues/69)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want validate to check number of records/fields specified in label matches the records in the actual data table ([#149](https://github.com/NASA-PDS/validate/issues/149)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate PDF files are PDF/A ([#164](https://github.com/NASA-PDS/validate/issues/164)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate a bundle that uses multiple versions of the Information Model / Discipline LDDs ([#188](https://github.com/NASA-PDS/validate/issues/188)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want validate to raise a WARNING when differing versions of IM are used within a bundle ([#210](https://github.com/NASA-PDS/validate/issues/210)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate all data types possible per the PDS4 Information Model ([#212](https://github.com/NASA-PDS/validate/issues/212)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate content for all possible PDS4 table types ([#217](https://github.com/NASA-PDS/validate/issues/217)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate content for all File_Area_* products ([#229](https://github.com/NASA-PDS/validate/issues/229)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate multiple bundles at once ([#237](https://github.com/NASA-PDS/validate/issues/237)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to verify bundle directories adhere directory naming standards per SR ([#239](https://github.com/NASA-PDS/validate/issues/239)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a developer, I want an API method enable specifying of non-registered context products ([#241](https://github.com/NASA-PDS/validate/issues/241)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want validate to throw an error when more than one primary product references the same physical file ([#245](https://github.com/NASA-PDS/validate/issues/245)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to run validate against object storage ([#266](https://github.com/NASA-PDS/validate/issues/266)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a developer, I want to utilize exit codes to differentiate failures of the process vs. validation errors ([#275](https://github.com/NASA-PDS/validate/issues/275)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate when a product and label are updated, but the label is not versioned ([#279](https://github.com/NASA-PDS/validate/issues/279)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## CCB-264: Make the Line Feed (LF) character an allowed record delimiter ([#292](https://github.com/NASA-PDS/validate/issues/292)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to the raise a WARNING if the object-defined size in the label does not match the file_size value ([#303](https://github.com/NASA-PDS/validate/issues/303)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate that all XML Schema collections in NASA PDS archives are secondary collections ([#307](https://github.com/NASA-PDS/validate/issues/307)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to check that all Internal References are valid references to other PDS4 products within the current validating bundle ([#308](https://github.com/NASA-PDS/validate/issues/308)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate that the label references the PDS4 common schematron file which is required by standards ([#309](https://github.com/NASA-PDS/validate/issues/309)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to check that all Internal References are valid references to other PDS4 products within the entire PDS4 system ([#316](https://github.com/NASA-PDS/validate/issues/316)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user I want to see the name of a table/array in errors, if one is specified ([#343](https://github.com/NASA-PDS/validate/issues/343)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to cache already downloaded schema/schematrons on the local file system ([#352](https://github.com/NASA-PDS/validate/issues/352)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate that the field_number values are sequential and match the label specification for maximum number of fields ([#359](https://github.com/NASA-PDS/validate/issues/359)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate all files referenced by a Product_Document ([#367](https://github.com/NASA-PDS/validate/issues/367)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## Improve PDF/A validation to include more robust reporting on failures ([#388](https://github.com/NASA-PDS/validate/issues/388)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to perform referential integrity checking against a registry ([#415](https://github.com/NASA-PDS/validate/issues/415)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want validate to throw an error when the LID specified for secondary context product in a collection inventory is not valid ([#462](https://github.com/NASA-PDS/validate/issues/462)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## Check for duplicate LIDVIDs in collection inventory ([#476](https://github.com/NASA-PDS/validate/issues/476)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version | ||
| ## As a user, I want to validate lblx file extension as a PDS4 label (CCB-260) ([#482](https://github.com/NASA-PDS/validate/issues/482)) | ||
|
|
||
|
|
||
| This requirement is not impacted by the current version |