Bug #7896

Dryad data sets don't mark new versions correctly in SystemMetadata with obsoletes/obsoletedBy

Added by Matthew Jones over 7 years ago. Updated over 6 years ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Story Points:


Dryad currently has 74,299 metadata dcouments reported in its DataONE profile, while on their site they indicate having only 14,217 data packages ( I believe this is because Dryad registers each new version of their metadata and data files with a new timestamped PID, but has not provided the appropriate 'obsoletes' information in their system metadata to indicate that the newer PID replaces an original PID. Thus, these newer versions are being counted in DataONE as independent data sets, when in fact they are just revisions. For a concrete example, see:

Original metadata:
New version:

That new version is not marked as obsoleting the original, and so they both show up as independent data sets. Ideally, the obsoletes field would be set for the newer of the two. Dryad would also probably benefit from using the SID field in system metadata to indicate that the two versions are part of the same series with the given DOI (e.g., in this case, This lack of obsoletes fields should be easily fixed because the PIDs in Dryad seem to consistently use the underlying DOI with a timestamped version field, so a script could probably be written to update all of the system metadata using a simple timestamp comparison to determine version order for the PIDs.

I believe the same issues exist for resource maps and data files as well, although possibly to a lesser extent for the data files.

Related issues

Related to Member Nodes - MNDeployment #3118: Dryad Member Node Operational 2012-08-05


#1 Updated by Matthew Jones over 7 years ago

#2 Updated by Monica Ihli about 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

I am in the process of writing a program to compare the contents of system metadata as it appears on the MN to the system metadata on the CN, and create a report of discrepancies which will be provided to the MN operators.

We still face the issue of figuring out how to correct discrepancies once they are identified. One solution to consider is upgrading Dryad from v1 to v2, in order to give them the power for MN changes to system metadata to cascade to CN. This possibility should be discussed with MN.

#3 Updated by Monica Ihli about 7 years ago

  • Assignee changed from Ryan Scherle to Monica Ihli

#4 Updated by Matthew Jones over 6 years ago

Update: According to our summary page, Dryad now has 101,210 non-obsoleted metadata documents listed in our system, while there self-reported data sets have only grown to 17861 as reported on We are significantly inflating our data set counts by not properly marking versions in Dryad, and the gap is growing. Any thoughts on when this might get resolved?

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)