NASA-PDS / operations

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

[nssdca-delivery] urn:nasa:pds:juno_jiram #302

Closed tinagueth closed 1 year ago

tinagueth commented 1 year ago

Discipline Node Information

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 commented 1 year ago

@tinagueth there are a number of integrity/unreferenced warnings as well as 3 errors regarding PDF/A compliance. Would you please take a look at the products in the package and address what you can? Please let me know of any issues when doing so. Thank you!

tinagueth commented 1 year ago

@c-suh I am not really sure what PDF/A compliance is. As Lyle does the validation part, would it be possible to get more information regarding those issues? Are they within the validation report, as I did not get any warnings when I ran the deep-archive part back when I was getting it ready for initial submission. Thank you.

jordanpadams commented 1 year ago

@tinagueth there is are some guidelines posted on our PDS4 Documentation web page: https://pds.nasa.gov/datastandards/documents/PDFA_Guidelines.pdf

jordanpadams commented 1 year ago

also per this comment:

Are they within the validation report, as I did not get any warnings when I ran the deep-archive part back when I was getting it ready for initial submission

They are in the validation report. deep-archive just generates the necessary delivery products. It is assumed Validate is executed and the archive is valid prior to running that tool.

tinagueth commented 1 year ago

@c-suh the validation report has been redone and can be found in the same location as the old version. Note that it is still called juno_jiramv10.txt. Would the .tar.gz file need to be updated as well for consistency? Thanks

c-suh commented 1 year ago

@tinagueth, thank you for the updated report (of the same name) and for resolving those errors and most of the warnings! if any files inside the .tar.gz have been changed, please do update/replace that file as well (same filename is fine). Thank you!

tinagueth commented 1 year ago

@c-suh To be on the safe side, I did redo the deep archive part as well. The .tar.gz file can be found in the same location as the validation report but is now named juno_jiram_v1.1_20221026.tar.gz. Thank you and hopefully it will be fine this time.

c-suh commented 1 year ago

@tinagueth 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:

tinagueth commented 1 year ago

@c-suh bundle has been written to archive