https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2016-09-30T22:32:56ZDataONE TasksMember Nodes - Bug #7896: Dryad data sets don't mark new versions correctly in SystemMetadata with obsoletes/obsoletedByhttps://redmine.dataone.org/issues/7896?journal_id=280842016-09-30T22:32:56ZMatthew Jonesjones@nceas.ucsb.edu
<ul><li><strong>Related to</strong> <i><a class="issue tracker-9 status-9 priority-6 priority-high2 parent" href="/issues/3118">MNDeployment #3118</a>: Dryad Member Node</i> added</li></ul> Member Nodes - Bug #7896: Dryad data sets don't mark new versions correctly in SystemMetadata with obsoletes/obsoletedByhttps://redmine.dataone.org/issues/7896?journal_id=284992017-02-13T19:28:17ZMonica Ihliemail@monicaihli.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><p>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.</p>
<p>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.</p>
Member Nodes - Bug #7896: Dryad data sets don't mark new versions correctly in SystemMetadata with obsoletes/obsoletedByhttps://redmine.dataone.org/issues/7896?journal_id=285002017-02-13T19:53:07ZMonica Ihliemail@monicaihli.com
<ul><li><strong>Assignee</strong> changed from <i>Ryan Scherle</i> to <i>Monica Ihli</i></li></ul> Member Nodes - Bug #7896: Dryad data sets don't mark new versions correctly in SystemMetadata with obsoletes/obsoletedByhttps://redmine.dataone.org/issues/7896?journal_id=290332017-07-24T06:45:47ZMatthew Jonesjones@nceas.ucsb.edu
<ul></ul><p>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 <a href="http://datadryad.org">http://datadryad.org</a>. 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? </p>