Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a user, I want to change the archive status for a collection and it's associated products #115

Closed
jordanpadams opened this issue Dec 21, 2021 · 0 comments
Assignees
Labels
B12.1 p.should-have requirement the current issue is a requirement

Comments

@jordanpadams
Copy link
Member

jordanpadams commented Dec 21, 2021

馃挭 Motivation

...so that I can enable external access to the product metadata from the API.

馃摉 Additional Details

鈿栵笍 Acceptance Criteria

Given a collection with associated products loaded in the registry
When I perform an registry-manager command set-archive-status on this lidvid to status {s}
Then I expect this lidvid and all the associated product lidvid to have status {s} in the registry database (field : "ops:Tracking_Meta.ops:archive_status")

The requirements applies to both the batch registry-manager and the new scalable harvest service.

鈿欙笍 Engineering Details

  • Update harvest client communicate with harvest server to trigger and update all the products to archive_status = archived
    • NOTE: The rationale here is to make it almost instantaneous execution from the node personnel, but the server-side will handle all the work
  • Update API to only return data that has archive_status == archived
@jordanpadams jordanpadams added requirement the current issue is a requirement needs:triage labels Dec 21, 2021
@jordanpadams jordanpadams changed the title As a user, I want to switch a collection and it's associated products from a protected status to operational. As a user, I want to change the archive status for a collection and it's associated products Jan 13, 2022
@jordanpadams jordanpadams transferred this issue from NASA-PDS/pds-registry-app Oct 6, 2022
@jordanpadams jordanpadams removed the Epic label Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B12.1 p.should-have requirement the current issue is a requirement
Projects
None yet
Development

No branches or pull requests

3 participants