NSSDCA Delivery: urn:nasa:pds:ast_binary_parameters_compilation::3.0 #61
Comments
|
Hello @neese,
Please post or send a corrected file. As an additional note, PDS Deep Archive has been recently updated to v0.4.0, and it appears |
|
@neese 4 of the 5 bundles have been submitted to the NSSDCA and are currently in processing. Using the SIP LID(s) below, you can check the status of this submission at https://nssdc.gsfc.nasa.gov/psi/ReportPDS4.jsp. SIP LID(s): |
|
Catherine,
Looks like the problem is that there is a filename in the bundle only one character long. (6.tab and 6.xml). This is not a violation of the file naming rules (below). We think the validator is wrongly rejecting it because of a side effect of the regular expression enforcing that the filename not begin or end with a dash, underscore, or period.
I think the bundle should be accepted as-is, but let me know what I should do.
Carol
6C.1.1 Rules
The following rules govern selection of file names.
• The file name must be unique within a directory. The same file name may appear in
different directories.
• The file name must be no longer than 255 characters (and be commensurate with other
length limits, such as for path names).
• The file name must be case-insensitive; for example, “MyFile.txt” and “myfile.txt” are not
permitted in the same directory.
• The file name must be constructed from the character set
A-Z ASCII 0x41 through 0x5A,
a-z ASCII 0x61 through 0x7A,
0-9 ASCII 0x30 through 0x39,
dash “-” ASCII 0x2D,
underscore “_” ASCII 0x5F, and
period “.” ASCII 0x2E.
• The file name must not begin or end with a dash, underscore, or period.
• The file name must include at least one period followed by an extension. A file name may
have more than one period, but PDS will consider all periods other than the final one to
be part of the base name.
… On Feb 15, 2021, at 8:35 PM, Catherine Suh ***@***.***> wrote:
Hello @neese <https://www.google.com/url?q=https://github.com/neese&source=gmail-imap&ust=1614051360000000&usg=AOvVaw3jx_BaYC_yAnBraDDHMmP_>, gbo_ast_fieber-beyer_spectra_v2.0_20210211_aip_v1.0.xml has failed validation with the following error:
FAIL: gbo_ast_fieber-beyer_spectra_v2.0_20210211_aip_v1.0.xml
Begin Content Validation: gbo_ast_fieber-beyer_spectra_v2.0_20210211_transfer_manifest_v1.0.tab
ERROR [error.table.field_value_data_type_mismatch] table 1, record 129, field 2: Value does not match its data type 'ASCII_File_Specification_Name': The filename spec '6.xml' does not match the pattern '[A-Za-z0-9][A-Za-z0-9-.]*[A-Za-z0-9].[A-Za-z0-9]+'
ERROR [error.table.field_value_data_type_mismatch] table 1, record 130, field 2: Value does not match its data type 'ASCII_File_Specification_Name': The filename spec '6.tab' does not match the pattern '[A-Za-z0-9][A-Za-z0-9-.]*[A-Za-z0-9].[A-Za-z0-9]+'
End Content Validation: gbo_ast_fieber-beyer_spectra_v2.0_20210211_transfer_manifest_v1.0.tab
Please post or send a corrected file.
As an additional note, PDS Deep Archive has been recently updated to v0.4.0, and it appears
you are using an earlier version. Please upgrade at your earliest convenience:
https://nasa-pds.github.io/pds-deep-archive/installation/index.html#upgrade-software <https://www.google.com/url?q=https://nasa-pds.github.io/pds-deep-archive/installation/index.html%23upgrade-software&source=gmail-imap&ust=1614051360000000&usg=AOvVaw3gR_9x1VNlRZmgdLoypPI_>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <https://www.google.com/url?q=https://github.com/NASA-PDS/pdsen-operations/issues/61%23issuecomment-779559228&source=gmail-imap&ust=1614051360000000&usg=AOvVaw12iIUyks2-GeVnEKwuTk4s>, or unsubscribe <https://www.google.com/url?q=https://github.com/notifications/unsubscribe-auth/AGJQ4AE2RDX2VJT2TK7D2ADS7HRZ7ANCNFSM4XPDERZQ&source=gmail-imap&ust=1614051360000000&usg=AOvVaw3F6n13af93zr1iS9sgJXAz>.
|
|
Hi Carol @neese, Thank you for the information; the rules are certainly pertinent! I will take a look at the logic, check in with the requisite people, and get back to you by hopefully next week at the latest. |
|
@c-suh if this looks like a bug, please create a ticket in validate and we can look to make a fix. |
|
Hi @jordanpadams and @neese, I've opened a ticket at NASA-PDS/validate#299. Carol, depending on the status of the linked issue, I will proceed. However, the other 4 bundles have been successfully archived! (If verifying results from https://nssdc.gsfc.nasa.gov/psi/reportpds4.action, please excuse the results which say "Failed"; this was due to my having forgotten the introduction of a new component to the process, and I caused duplicate submissions of the bundles. ) |
|
@c-suh I think we can proceed with submitting all the bundles as long as that is the only error validate throws. as long as NSSDCA receives it, we should be fine. we can check with validate and make that fix when we can. @neese in the future, if you encounter false errors in validate, please file a bug report here: https://github.com/NASA-PDS/validate/issues/new/choose . We do our best to interpret the standards and implement accordingly, but bugs happen 🐛 🐞 😄 |
|
@neese the last set has been submitted to the NSSDCA and is currently in processing. Using the SIP LID below, you can check the status of this submission at https://nssdc.gsfc.nasa.gov/psi/ReportPDS4.jsp. SIP LID:
|
|
@neese @c-suh We/NSSDCA are in the process of ingesting the 11 SIPs submitted last week and the one submitted yesterday. Here are the LIDVIDs: urn:nasa:pds:system_bundle:product_sip_deep_archive:ast-lightcurve-database_v2.0_20210222::1.0 And as @c-suh noted, you can check statuses at https://nssdc.gsfc.nasa.gov/psi/ReportPDS4.jsp. To get a list of all SBN-PSI's SIPs, select "Planetary Science Institute Subnode" for Provider Site. You can narrow the results by entering a start/stop date, keeping in mind this is the date when NSSDCA automatically pulled the SIP from online repository https://pds.nasa.gov/data/pds4/manifests/, which typically a day after EN/Ops posted the SIP. To check the status of the most recent 12 SIPs, I recommend entering a start date of "2021-02-24". The resulting report will show those 12 submissions. In a PDS4 report, a remark of "Sent to ingest" in the "SIP Details" area along with a status of "Pre-Ingest" for a bundle or collection in the "Bundle/Collection LIDVID" area means we're still ingesting and archiving the contents of the submission. When we've successfully finished archiving to tape, we update the status to "Archived". Just an FYI, for one PDS4 SIP/bundle submission, create one NSSDCA collection for the bundle product and one NSSDCA collection for each of the primary collection identified in the bundle product. As you use the PDS4 Reporting tool, please let me know if there's additional information you would like to see or to be able to search on. We expect to be refining the interface as we get more submissions and as more nodes use it. Thanks! |
|
@smclaughlin7 thank you for the information! I've made note of the multiple pieces of information and regarding additional info from the PDS4 Reporting tool, although I do not have any thoughts at the moment, no doubt @jordanpadams would have relevant and helpful input. |
|
@neese the 5 sets from this ticket have been successfully archived. |
|
@smclaughlin7 the output report should suffice right now. one minor helpful tidbit would be include some ℹ️ or ❓ icon or some easy to access help info next to the output report that briefly mention what |
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/deep_archive_deliveries/sbnpsi_batch_1_20210211.zip
Engineering Node Process
See the internal EN process at https://pds-engineering.jpl.nasa.gov/content/nssdca_interface_process
The text was updated successfully, but these errors were encountered: