Closed jordanpadams closed 7 months ago
Reached out to CSDO and they have an agreement with AWS to allow some data sets into the registry, but per their recommendation, we should just pursue the submission on our own. Process is defined here: https://github.com/awslabs/open-data-registry/
📆 October status: In work. On schedule.
New internal wiki page has been created for that.
📆 November status: Working ongoing. On schedule
📆 December status: Increased scope to complete full onboarding process for AWS Open Data Registry vs. initial scope to prep the data for the Registry. The process is a bit more involved, and requires support from SBN to document how to use the data. This will be an ongoing effort that will require numerous players, so it can be done in parallel with other efforts. Not impact on delivery expected.
MCP cannot do the AWS account for us, so working with Open Data Registry's in AWS. Deadline = 2 weeks!
📆 01/2024 status: In work. Completion date delayed 1 sprint. No impact on delivery.
💡 Description
Here is the data providers guide provided by NASA CSDO (Andy M.), which looks a little different than what the online site says: https://assets.opendata.aws/aws-onboarding-handbook-for-data-providers-en-US.pdf
From that document:
https://github.com/NASA-PDS/planetary-data-cloud/issues/89
https://github.com/NASA-PDS/planetary-data-cloud/issues/90
https://github.com/NASA-PDS/planetary-data-cloud/issues/91
https://github.com/NASA-PDS/planetary-data-cloud/issues/92
Skip Terms & Conditions step. Per CSDO, this is covered by the Space Act Agreement.
https://github.com/NASA-PDS/planetary-data-cloud/issues/93
https://github.com/NASA-PDS/planetary-data-cloud/issues/94
[X] ~Complete process for submitting initial request to AWS for Open Data registry (@viviant100)~
86 is a start for this, but per the updated information above, this will be completed as part of #92