Skip to content

Commit

Permalink
Update requirements
Browse files Browse the repository at this point in the history
  • Loading branch information
pdsen-ci committed Oct 16, 2024
1 parent 20b198d commit e5628b5
Showing 1 changed file with 38 additions and 0 deletions.
38 changes: 38 additions & 0 deletions docs/requirements/v5.0.1/REQUIREMENTS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@

Requirements Summary
====================

# default

## As a registry user, I want to search on ref_lid_* from the registry metadata ([#50](https://github.com/NASA-PDS/registry-mgr/issues/50))


This requirement is not impacted by the current version
## As a user I want to delete whole bundles at once ([#52](https://github.com/NASA-PDS/registry-mgr/issues/52))


This requirement is not impacted by the current version
## As a user, I want to query OpenSearch for staged data via a CLI command ([#59](https://github.com/NASA-PDS/registry-mgr/issues/59))


This requirement is not impacted by the current version
## As a user, I want to manually update a product's file location (file_ref) ([#76](https://github.com/NASA-PDS/registry-mgr/issues/76))


This requirement is not impacted by the current version
## As a user, I want to set archive-status using packageId ([#69](https://github.com/NASA-PDS/registry-mgr/issues/69))


This requirement is not impacted by the current version
## As a registry manager, I want to update the OpenSearch schema from the latest LDD properties types. ([#74](https://github.com/NASA-PDS/registry-mgr/issues/74))


This requirement is not impacted by the current version
## As a user, I want to specify the list of products to be deleted from a file ([#77](https://github.com/NASA-PDS/registry-mgr/issues/77))


This requirement is not impacted by the current version
## As a user, I want to delete all products in my node registry ([#80](https://github.com/NASA-PDS/registry-mgr/issues/80))


This requirement is not impacted by the current version

0 comments on commit e5628b5

Please sign in to comment.