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

As a user, I want to know what are all the possible properties I can search against (/properties) #506

Closed
jordanpadams opened this issue Jul 19, 2024 · 3 comments Β· Fixed by #530
Assignees
Labels

Comments

@jordanpadams
Copy link
Member

jordanpadams commented Jul 19, 2024

Checked for duplicates

No - I haven't checked

πŸ§‘β€πŸ”¬ User Persona(s)

No response

πŸ’ͺ Motivation

...so that I can know all the available properties I can search by in the API.

πŸ“– Additional Details

No response

Acceptance Criteria

Given a running API service
When I perform GET /properties
Then I expect to receive the set of all properties available for search within the system

βš™οΈ Engineering Details

Note: This is a first barebones pass and what is returned by this endpoint. A more robust, detailed response will eventually be needed in order to support a more useful response (e.g. definitions)

πŸŽ‰ I&T

No response

@alexdunnjpl
Copy link
Contributor

@jordanpadams is this endpoint intended to ever support subsetting, or is it sufficient to (more or less) dump the union of all registry indices' _mapping content?

@jordanpadams
Copy link
Member Author

@alexdunnjpl I think for now a dump of the _mapping works for now. We probably want a smarter version of this that actually pulls information from the PDS4 Information Model, but I think for now, just a top of what is searchable will do.

@jordanpadams
Copy link
Member Author

@tloubrieu-jpl ☝️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🏁 Done
Status: 🏁 Done
Development

Successfully merging a pull request may close this issue.

2 participants