search

NASA-PDS / registry-api

Web API service for the PDS Registry, providing the implementation of the PDS Search API (https://github.com/nasa-pds/pds-api) for the PDS Registry.
https://nasa-pds.github.io/pds-api
Apache License 2.0
3 stars 5 forks source link

As a user, I want to easily link telescope to their facility (or the other way around) #550

Open tloubrieu-jpl opened 1 month ago

tloubrieu-jpl commented 1 month ago

Checked for duplicates

Yes - I've already checked

🧑‍🔬 User Persona(s)

Web front-end developer.

💪 Motivation

...so that I don't need to do computationally intensive operations on the client side.

📖 Additional Details

That could be something like:

http://pds.nasa.gov/api/search/1/classes/context/{facility lidvid}/members

Which would return all the telescope lidvids.

But this would need to be refined with @anilnatha and possibly the requirement could be extended to other investigation/instrument_host/istrument relationship.

Acceptance Criteria

Given When I perform Then I expect

⚙️ Engineering Details

I am just logging that from a web mod meeting, in case we can help here.

🎉 I&T

No response

jordanpadams commented 1 month ago

@tloubrieu-jpl this seems like a data curation exercise to include these references in the context products. Not really something that the API should try to figure out.

I think this would be better as:

/products/{facility_identifier}/telescopes

or 

/classes/context/{facility_identifier}/telescopes

Trying to figure out what "members" means in all variants of context products can get super confusing and weird. e.g. instrument_host/members could be instrument packages or instruments or both depending upon the instrument_host hard to really tell. I don't think we want to take on that interpretation responsibility.