Skip to content

Validate does not always throw an error when ASCII_File_Specification_Name contains a \ (backslash) #1369

@c-suh

Description

@c-suh

Checked for duplicates

No - I haven't checked

🐛 Describe the bug

When I did a Validate run on the sets from NASA-PDS/operations#694, I noticed that vl_labeled_release and vl_image_raw gave errors like the following:

ERROR  [error.table.field_value_data_type_mismatch]   data object transfer manifest or index 1, record 5, field 2: Value does not match its data type 'ASCII_File_Specification_Name': The directory spec '/browse\lander_1\axxx\' does not match the pattern '/?([A-Za-z0-9][A-Za-z0-9_-]*[A-Za-z0-9]/?|[A-Za-z0-9][^-_]/?)*'

But then all of the other labels pass as valid, but the transfer manifest all contain \ for the paths.

🕵️ Expected behavior

I expected these sets to pass Validate

📜 To Reproduce

  1. Download either the delivery package zip from the operations issue or the sets of named files from https://pds.nasa.gov/data/pds4/manifests/2025/.
  2. Run validate (e.g., % validate -t vl_image_raw_v1.0_20250905*.xml)
  3. Look at the output

🖥 Environment Info

  • Operating System: MacOS Sequoia 15.5

📚 Version of Software Used

v3.7.1

🩺 Test Data / Additional context

I thought this was the issue, as this was the only difference I found in the sets from operations#694 that passed/failed, but Jordan's comment below disproves it. Leaving the info here in case it can be helpful.

Section 6C.2.1 of the PDS Standards Reference states:

 • The directory 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), and
       underscore “_”     ASCII 0x5F

However, the regex string /?([A-Za-z0-9][A-Za-z0-9_-]*[A-Za-z0-9]/?|[A-Za-z0-9][^-_]/?)* specifically does not allow a dash or underscore in the subdirectories.


For the assignee to verify if this is the actual issue or if it's something else, I'm attaching the validation reports for these 2 as well as from another set in the same Operations ticket. All 3 have the issue with the forward slashes in the transfer manifest files, which has been fixed (but not yet i&t tested and released) in deep-archive.

Errors:

No error: nathairfacula_messenger_mdis_topography_domingue_2022_v1.0_20250904-validate.txt

🦄 Related requirements

🦄 #xyz

⚙️ Engineering Details

No response

🎉 Integration & Test

No response

Metadata

Metadata

Assignees

Labels

Type

Projects

Status

In Progress

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions