@tariqksoliman as a heads up, here are some examples of some exist "service" products:

https://pds.nasa.gov/data/pds4/context-pds4/service/Product/
https://pds.nasa.gov/data/pds4/context-pds3/service/Product/

You may have already discussed this with @tloubrieu-jpl, but the easiest route to get something going here is to probably add some references to a couple of those products (e.g. references to investigations, instruments, bundles, collections, etc.), and then load those into your local Registry with Harvest. @CSeyb @katecrombie @rgdeen or @sarabond can probably help update a few of those products for you.

That will probably not get the full solution you are looking for (e.g. subsets of specific data sets), but it will probably get the 80% solution. Then we can try to figure out how to support that 20%

@tariqksoliman would it be OK with you if I adjusted the success criteria? Ideally this would return, at minimum, something similar to the definition of our current application/json response format: https://nasa-pds.github.io/pds-api/guides/search/responses.html

Let @tloubrieu-jpl or I know if you have any questions.

@tariqksoliman also, one additional note before all the files in the repo get reformatted, the team has agreed upon a Code Style Guide to try to avoid tab/space commits that make PRs impossible to review. The guide below includes some ways to configure Eclipse or IntelliJ to uses this style out of the box.

https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Java-Code-Style-Guide