[nssdca-delivery] urn:nasa:pds:gbo.ast.catalina.survey::1.0 20220311

[beatricemueller]

Discipline Node Information

• Delivering Node: please enter your DN here for record keeping purposes

• PDS_PSI

• NSSDCA Delivery Package: please upload the files output by PDS Deep Archive as a TAR.GZ or ZIP file here, or supply a URL to download from

• https://sbnarchive.psi.edu/pds4/surveys/catalina_extras/sips/deltas/20220311_deltas.zip

• Validation report: please upload a TXT report or screenshot of PDS4 Validate Tool run on your bundle. NSSDCA only accepts valid PDS4 bundles. be sure you run validate with the -R pds4.bundle flag enabled to ensure all integrity checks are completed successfully.

• https://sbnarchive.psi.edu/pds4/surveys/catalina_extras/validation/20220311.tar.gz

NOTE: If you have multiple delivery packages, we strongly encourage you to submit these in batches of 3 to 10 per issue with one ZIP file of the packages and another ZIP file of the validation reports. Please use a descriptive title, such as "Node Mission misc batch #".

---

Engineering Node Process

See the internal EN process at https://pds-engineering.jpl.nasa.gov/content/nssdca_interface_process

[beatricemueller]

@c-suh Note that the validation report might have errors, but any file that throws an error is pulled and is not submitted and will be submitted subsequently once fixed. This is an acceptable approach as discussed in #252

[c-suh]

@beatricemueller this set has been posted for NSSDCA processing. From tomorrow, you can check the status at https://nssdc.gsfc.nasa.gov/psi/ReportPDS4.jsp using the SIP LID below:

SIP LID:

• urn:nasa:pds:system_bundle:product_sip_deep_archive:gbo.ast.catalina.survey_v1.0_20220311_delta_20220623194937027150

[smclaughlin7]

@beatricemueller @c-suh Hi Bea, Regarding SIP LID

• urn:nasa:pds:system_bundle:product_sip_deep_archive:gbo.ast.catalina.survey_v1.0_20220311_delta_20220623194937027150

The NSSDCA finished ingesting (i.e., registering and downloading) all products identified in this SIP except for 7 that failed because the files for those products were moved from their original directory identified in the SIP to sub folders named “SUPERSEDED” before the NSSDCA ingested/downloaded them. Here's a list of the failed products: 7_products_failed_ingest.txt. (The NSSDCA is presently archiving all the successfully ingested/downloaded products to tape -- Yay!)

We're presently ingesting the remaining 3 CSS delta-SIPs, which will have the same issue if any products moved since you delivered the SIPs to EN in late June:

• urn:nasa:pds:system_bundle:product_sip_deep_archive:gbo.ast.catalina.survey_v1.0_20220318_delta_20220624185620740018::1.0
• urn:nasa:pds:system_bundle:product_sip_deep_archive:gbo.ast.catalina.survey_v1.0_20220325_delta_20220627173110587170::1.0
• urn:nasa:pds:system_bundle:product_sip_deep_archive:gbo.ast.catalina.survey_v1.0_20220401_delta_20220629164737571641::1.0

Once the NSSDCA has finished ingesting/downloading all the data for a SIP, which usually takes several days after Catherine posts the SIP for us, you can safely make changes to products contained in that SIP. However if any products are changed or moved after the SIP is delivered to EN/Github and before we have finished ingesting that SIP it will cause those products to fail our ingest process.

I don't think this is an issue because the 7 failed products appear to have been superseded, but you may want to run this by Jesse Stone so he's aware. Perhaps there's a trigger in the CSS pipeline that automatically moves older versions of a collection to a superseded directory?

Also once we get on a more regular, ~weekly delivery of CSS-delta SIPs, this issue might go away -- mostly.

Thanks for your patience as we ingest the CSS delta SIPs!

[c-suh]

@beatricemueller this package for gbo.ast.catalina.survey_v1.0_20220311_delta_20220623194937027150 has been archived!