[nssdca-delivery] PDS_ATM Pack#5

[tinagueth]

Discipline Node Information

• Delivering Node: PDS_ATM

• NSSDCA Delivery Package: pdsatm_pack5_20220801.tar.gz

• Validation report: pdsatm_pack5_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 just a friendly nudge to upgrade your Validate tool to the latest version (currently 2.3.0). Also a note that the moxie bundle has a file which was not found to be PDF/A-1b compliant. This is not a showstopper, so I'm passing it along to NSSDCA, and it might be fixed by upgrading Validate to its latest version, v2.3.0, so please upgrade the next chance you have. Thank you!

---

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 LIDs below:

SIP LIDs: urn:nasa:pds:system_bundle:product_sip_deep_archive:mars2020_meda_v1.0_20220801 urn:nasa:pds:system_bundle:product_sip_deep_archive:mars2020_moxie_v4.0_20220801

[smclaughlin7]

@tinagueth @c-suh For this SIP LID

_urn:nasa:pds:system_bundle:product_sip_deep_archive:mars2020_meda_v1.020220801

one product failed ingest, LIDVID _urn:nasa:pds:mars2020meda:document::4.0: For the file https://pds-atmospheres.nmsu.edu/PDS/data/PDS4/Mars2020/mars2020_meda/document/collection_document_inventory.csv expected MD5 checksum b74a535f0e80b49248cfb52744b11a1d per the SIP manifest, but got be4bb0d6850a460b57cf034ca337c511 on fetching the file. The Deep Archive Package for this submission was created on 2022-08-01 but it appears the document collection's inventory file and XML label were changed on 2022-08-02, which probably explains the checksum mismatch. Solution: Make a new Deep Archive Package for this bundle and submit it to EN. Thanks!

This SIP LID had been ingested without any issues (Yay!):

urn:nasa:pds:system_bundle:product_sip_deep_archive:mars2020_moxie_v4.0_20220801

[tinagueth]

@smclaughlin7 @c-suh I resubmitted the meda bundle, see #292 Hopefully the issue is resolved. Thanks, Tina

[smclaughlin7]

@tinagueth @c-suh Thanks for resubmitting the meda bundle as #292, which should resolve the checksum mismatch on the document collection's inventory file!

Just a heads up: I noticed https://atmos.nmsu.edu/PDS/data/PDS4/Mars2020/mars2020_meda/bundle.xml lists two secondary collections whose LIDs use the incorrect string "m2020_mission" for the mission bundle's LID instead of the correct string "mars2020_mission":

urn:nasa:pds:***m2020_mission***:document_camera Secondary bundle_has_document_collection

...

urn:nasa:pds:***m2020_mission***:miscellaneous Secondary bundle_has_miscellaneous_collection

This is not a big deal as far as NSSDCA ingest goes because we do not ingest secondary collections (or seocndary basic products). However for consistency with the mission bundle, those two secondary collection LIDs should be corrected in a future version of the meda bundle (and resubmitted to the NSSDCA if possible). I apologize for not catching this in previous submissions of the meda bundle!

Note: The mars2020 mission bundle product https://pds-geosciences.wustl.edu/m2020/urn-nasa-pds-mars2020_mission/bundle_mars2020_mission.xml has LID urn:nasa:pds:mars2020_mission.

Thanks!

[tinagueth]

@smclaughlin7 @c-suh Lyle fixed those issues. Should I resubmit it again and we close/ignore this submission?

[smclaughlin7]

@tinagueth @c-suh That was a rapid fix - Thanks!

I don't think Catherine has checked the meda bundle package you submitted this morning as #292.

Catherine, Is it OK if Tina remakes the deep archive package and validation report and uploads them to #292 with a note to please ingore the files submitted earlier today: https://github.com/NASA-PDS/operations/files/9352086/mars2020_meda_20220816.tar.gz and https://github.com/NASA-PDS/operations/files/9352092/meda_bundlev4.txt? Thanks!

[jordanpadams]

@smclaughlin7 @tinagueth that is fine. @c-suh is out on leave for the week, but I'm sure we will back on this next week.

[tinagueth]

@smclaughlin7 @c-suh @jordanpadams Thanks for letting us know about Catherine being on leave. How do I update a submission (i.e. #292 ) with the new tar.gz file (the validation report looks fine)? I have never done this before. Thanks

[smclaughlin7]

@jordanpadams Thanks for filling in while @c-suh is on leave! As @tinagueth noted, we don't know how to update #292 with a new tar.gz file. Can/should #292 be simply be closed since we don't want to process that delivery, then @tinagueth could open a new ticket for the new tar.gz file?

[jordanpadams]

@smclaughlin7 I just closed as wontfix. Go ahead with creating a new delivery.

[jordanpadams]

@tinagueth ☝️

[jordanpadams]

also @tinagueth @smclaughlin7 per wanting to update a tar.gz, you can just comment on the ticket. or I'm not sure if you are able to edit your submitted ticket or not:

[tinagueth]

@smclaughlin7 @jordanpadams I will re-submit the meda bundle in a bit. Also, when I try the edit part, it only lets me edit the name of the submitted delivery but not any of the attachments. Also, do note that #292 has to be closed/wontfixed update, not #288 as #288 also contains the moxie bundle, which had no problems.

[tinagueth]

@jordanpadams @smclaughlin7 @c-suh I resubmitted mars2020 meda_bundle again (#293) and gave the .tar.gz file a v1 indicator just to avoid any confusions. Thanks.

[smclaughlin7]

@tinagueth :thumbsup:

[tinagueth]

@c-suh moxie_bundle has been archived, along with re-submission #293 for meda_bundle