Closed mace-space closed 1 year ago
@mace-space would you mind attaching the run log if you still have it?
I don't think it is an issue with Validate after all, but rather due to the options chosen? I attach two logs:
-t
and doesn't appear to actually run any referential integrity checks-R pds4.bundle -v 2
and does flag warnings @mace-space correct. that is the issue. for production validation, you pretty much want to always use the pds4.bundle
rule, unless you are running validate multiple times in a pipeline of some kind. let us know if you run into any other issues.
Checked for duplicates
Yes - I've already checked
🐛 Describe the bug
Referential integrity check appears to miss warnings about collection_data.csv and data products in a bundle of raw RSS Voyager data (link to data below).
Transfer manifest contains the following entries:
and the corresponding data and browse collections do contain these files.
However, the collection_data.csv lists:
P,urn:nasa:pds:voyager2_rss_jupiter_raw:data:vg2j_14mr_1979191t131728::1.0
ending in 8, rather than 7.(The collection_browse.csv does list the correct file:
P,urn:nasa:pds:voyager2_rss_jupiter_raw:browse:vg2j_14mr_1979191t131727::1.0
)🕵️ Expected behavior
I expected Validate to at least flag a warning, but everything passed. Validate ought to verify the completeness and accuracy of collection inventories.
Request that Validate flags a warning about referential integrity if the collection CSV members and files in the collection do not match.
📜 To Reproduce
Bundle can be found at https://pds-rings.seti.org/review-data/voyager_rss_jupiter_raw/
🖥 Environment Info
No response
📚 Version of Software Used
Validate 3.0.3, Validate 3.2.0
🩺 Test Data / Additional context
No response
🦄 Related requirements
No response
⚙️ Engineering Details
No response