As a user, I want to validate when a product and label are updated, but the label is not versioned

[smclaughlin7]

Background: When the NSSDCA ingested OSIRIS-REx Mission bundle v8.0 which SBN-PSI submitted on 7 December, our staff noticed the inventory file for the context collection product had a different checksum but the byte count and product version (VID) were identical to those in v7.0 of the bundle that we ingested in September. Since the checksum differed, our ingest system assigned a unique internal identifier to this new inventory file, then downloaded and archived it as intended. We compared both archived instances and discovered that they contain identical records but the order was changed between bundle v7.0 and v8.0 and the VID for the context collection was incremented. We alerted Carol Neese. She will follow to make sure this does not happen again.

Concern: The NSSDCA is concerned this scenario is a PDS data integrity issue, where one or more bits of a product component is tweaked -- the checksum changes -- but the VID is not updated. Although this occurred in a small context collection product, it could happen in a large image archive for example.

Solution: This checksum/VID discrepancy should be caught on the PDS side and before a product reaches the deep archive at the NSSDCA. Although the Validate Tool can be forced to compare checksums of components with those in a manifest file, it does not seem to guarantee this discrepancy would be caught. Could Validate Tool and/or perhaps the Registry Service be enhanced to look for cases where one or more bits of a component of a registered product** has changed (i.e., its checksum) but its VID was not incremented?

** Assumes basic products, in additional to collection and bundle products, are registered.

Additional Information: The attached file, Compare_OREx_Mission_Bundle_v7_and_v8_Context.zip, contains:

• the Context collection product found in v7.0 and v8.0 of the OSIRIS-REx mission bundle, and
• the Submission Information Package (SIP) files for both deliveries to the NSSDCA. Compare_OREx_Mission_Bundle_v7_and_v8_Context.zip

Note: This should also apply to collections that refer to products that have changed