As a user, I want to generate AIPs and SIPs using Registry

[jordanpadams]

No description provided.

[tloubrieu-jpl]

@nutjob4life will work on the new version of the registry and API, but the tool still need to work if the data is not available in this new registry/api since they will not be fully deployed/initialized too soon.

[tloubrieu-jpl]

@nutjob4life :
The validation api end point is available on https://pds-gamma.jpl.nasa.gov/api/swagger-ui.html

The python API client is on https://github.com/NASA-PDS/pds-api-client

[tloubrieu-jpl]

@nutjob4life was not able to make the python api client work. @tloubrieu-jpl need to look.

[tloubrieu-jpl]

@nutjob4life is finalizing the on-going refactoring.

We'll discuss a better integration of demo client/server next Thursday.

[tloubrieu-jpl]

@nutjob4life I have updated the pds-gamma api service and it now works with the api client, see https://github.com/NASA-PDS/pds-api-notebook/tree/main

Let me know if you have questions on that.

[nutjob4life]

Confirmed! I can successfully use pds.api_client with https://pds-gamma.jpl.nasa.gov/api/. Thanks @tloubrieu-jpl

[nutjob4life]

Just to confirm, the user inputs to generate a SIP & AIP with this will be:

• Registry API to use (perhaps with a default like https://pds.nasa.gov/api/)
• LIDVID of the bundle for which to make the SIP and AIP

For example:

pds-deep-archive --registry https://pds-gamma.jpl.nasa.gov/api/  urn:nasa:pds:insight_documents::2.0

Or perhaps will it a single input:

• URL to a full LIDVID bundle within the ReST API

As in:

pds-deep-archive https://pds-gamma.jpl.nasa.gov/api/bundles/urn%3Anasa%3Apds%3Ainsight_documents%3A%3A2.0

What do you guys think @jordanpadams @tloubrieu-jpl 🤔

[jordanpadams]

@nutjob4life i prefer option pds-deep-archive --registry https://pds-gamma.jpl.nasa.gov/api/ urn:nasa:pds:insight_documents::2.0 . This seems the simplest for the user, and they shouldn't have to care/know the REST API query for their product (also in case the API changes).