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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update API to only return results where archive status in (archived, certified) #78

Closed
tloubrieu-jpl opened this issue Jan 12, 2022 · 5 comments
Assignees

Comments

@tloubrieu-jpl
Copy link
Member

tloubrieu-jpl commented Jan 12, 2022

See related requirements below. With archive_status set, we want to block access to only data that is archived and release.

Related Requirements

🦄 https://github.com/nasa-pds/pds-api/issues/106

@tloubrieu-jpl tloubrieu-jpl transferred this issue from nasa-pds-engineering-node/pds-registry-app Jan 12, 2022
@tloubrieu-jpl
Copy link
Member Author

closed by mistake

@tloubrieu-jpl tloubrieu-jpl reopened this Jan 20, 2022
@jordanpadams jordanpadams changed the title Manage archive status in the API Update API to only return results where archive status == archived Feb 4, 2022
@tdddblog
Copy link
Contributor

tdddblog commented Feb 4, 2022

@jordanpadams @tloubrieu-jpl "archived" only or both "archived" and "certified" as described in "Discussion from SWG" document?

@jordanpadams
Copy link
Member

@tdddblog Archived and certified! Thanks for checking on that

@jordanpadams jordanpadams changed the title Update API to only return results where archive status == archived Update API to only return results where archive status in (archived, certified) Feb 4, 2022
@tloubrieu-jpl
Copy link
Member Author

@tdddblog
I was thinking the configuration for which products status should be published through the API would be in the application.properties file. That might be obvious but I prefer to be explicit. Thanks

@jordanpadams
Copy link
Member

resolved per #99

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants