search

NASA-PDS / operations

Tickets for the PDSEN Operations Team
Other
5 stars 1 forks source link

[nssdca-delivery] urn:nasa:pds:astromat::1.0 and urn:nasa:pds:insight_ida::2.0 #519

Open alknight-wustl opened 5 months ago

alknight-wustl commented 5 months ago

Discipline Node Information

alknight-wustl commented 5 months ago

The Geosciences Node is aware of the error present in the validation report for urn:nasa:pds:astromat::1.0. The error is caused by a person's name. We are not planning on correcting it at this time.

c-suh commented 5 months ago

@alknight-wustl thank you for the heads up about the error. These 2 sets have 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:

smclaughlin7 commented 4 months ago

@alknight-wustl (and perhaps @jordanpadams) re: SIP LID urn:nasa:pds:system_bundle:product_sip_deep_archive:astromat_v1.0_20240528

We/NSSDCA would appreciate it if you/Geosciences could provide an explanation why there is no context product (i.e., no Internal_Reference) for Observing_System_Component "Electron Microprobe" in the bundle product, https://pds-geosciences.wustl.edu/lab/urn-nasa-pds-astromat/bundle_astromat_chem.xml? Perhpas this was intentional?

(We do understand the schema does not require Internal_Reference for Observing_System_Component.)

Thanks!

alknight-wustl commented 4 months ago

@smclaughlin7 I believe the Observing_System_Component "Electron Microprobe" was a typical commercial laboratory instrument, and we usually don't create new context products for such instruments.

smclaughlin7 commented 4 months ago

@alknight-wustl Thank you. This is good to know. Our frontend process for PDS4 submissions did not process SIP

because it could not find the element (for a Context product) in in the bundle product. It assumes the element will be present. (it uses that element to link PDS4 submissions to instrument records in our database.)

This is the first bundle we've received where an Observing_System_Component does not have an associated Context product. Given this and the fact that the IM does not require ., I'll work with our software dev team to revise our frontend process accordingly. It may be awhile before they can get to this, so we will keep this SIP at a status of "Proferred" in our system. Please let me know if this delay will affect updating this bundle in the near future. (The bundle should not be changed until we have ingested it.)

I'm cc'ing @c-suh and @jordanpadams so they're aware of this delay. Thanks!

alknight-wustl commented 4 months ago

@smclaughlin7 Sounds good! We don't expect to be updating the bundle in the near future, so the delay shouldn't be an issue for us.

smclaughlin7 commented 1 month ago

@alknight-wustl Good news! We/NSSDCA enhanced our PDS4 frontend process to continue processing a SIP when a bundle or collection product does not include , , or ..

We successfully reprocessed the outstanding Astromaterials SIP from June through our enhanced frontend. You 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:astromat_v1.0_20240528

I'm cc'ing @c-suh and @jordanpadams so they're aware this issue is resolved.

Thanks for your patience!

alknight-wustl commented 1 month ago

@smclaughlin7 Great -- thank you so much!