[nssdca-delivery] PDS_ATM Pack #7

[tinagueth]

Discipline Node Information

• Delivering Node: PDS_ATM

• NSSDCA Delivery Package: pdsatm_pack7_20221110.tar.gz

• Validation report: pdsatm_pack7_validationreports.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

[c-suh]

@tinagueth, happy early Thanksgiving! A few notes:

• there is a recent release for v3.0.3 of the Validate tool! Please upgrade it at your earliest convenience.
• one of the 3 sets, go_uvs, did not pass validation because several files do not adhere to the PDS rules for file names (see Section 6C.1.1 Rules or page 60 of the Standards Reference). Specifically, the rule that "[t]he file name must not begin or end with a dash, underscore, or period" is broken by such files as G02A_EUV_TURNON__.xml. Please refer to go_uvs_v1.0_20221109-validate.txt for details and all affected files.
• the other sets have passed validation and been posted for NSSDCA processing! From tomorrow, you can check the status at https://nssdc.gsfc.nasa.gov/psi/ReportPDS4.jsp using the SIP LIDs below:

SIP LIDs: urn:nasa:pds:system_bundle:product_sip_deep_archive:go_ppr_v1.0_20221109 urn:nasa:pds:system_bundle:product_sip_deep_archive:vg_uvs_v1.0_20221109

[c-suh]

Per email exchange yesterday with Lyle where he pointed out my error concerning the errors, a Validate issue for the bug has been opened and the last package submitted to NSSDCA for processing. Starting tomorrow, its status can be checked 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:go_uvs_v1.0_20221109

[tinagueth]

@c-suh I saw the exchange and appreciate being included so I know what is going on, especially as I am not knowledgeable in the situation that occurred. I do hope this error can be resolved at some point. Thank you

[smclaughlin7]

@c-suh Could you please summarize the validation issue you discussed with Lyle? Depending on the issue it may impact some of our PDS4 ingest processes here at the NSSDCA. Is it perhaps related to new https://github.com/NASA-PDS/validate/issues/561? Thanks! cc: @tinagueth

[c-suh]

@smclaughlin7 sure! The validation issue is described in the newer https://github.com/NASA-PDS/validate/issues/562, which is that the Validate tool incorrectly enforces file naming requirements for base file names ending in a period, underscore, or hyphen. I had confused base names with file names, which Lyle was quick to catch and point out, e.g. G02A_EUV_TURNON__.xml is an acceptable file name because, yes, the base name ends in an underscore, but the entire file name itself does not. Let me know if you would like more details! cc: @tinagueth

[smclaughlin7]

@c-suh Thank you for this summary and pointing me to the relevant ticket https://github.com/NASA-PDS/validate/issues/562! Much appreciated.

[tinagueth]

@c-suh the AIP/SIP set for all 3 bundles have been archived.