https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2013-02-11T18:38:43ZDataONE TasksMember Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=152342013-02-11T18:38:43ZSkye Roseboomsroseboo@dataone.unm.edu
<ul><li><strong>Parent task</strong> set to <i>#3568</i></li></ul> Member Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=152922013-02-18T16:42:30ZSkye Roseboomsroseboo@dataone.unm.edu
<ul><li><strong>Assignee</strong> deleted (<del><i>Skye Roseboom</i></del>)</li></ul> Member Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=153502013-02-22T17:39:54ZSkye Roseboomsroseboo@dataone.unm.edu
<ul><li><strong>Category</strong> set to <i>296</i></li><li><strong>Assignee</strong> set to <i>John Kunze</i></li></ul><p>First step is to determine if this content should be available from the MN. If it should no longer be available on the CN, we need to 'archive' the pids to remove these docs from search index and other services.</p>
Member Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=153512013-02-22T18:00:25ZSkye Roseboomsroseboo@dataone.unm.edu
<ul><li><strong>Target version</strong> set to <i>Operational</i></li></ul> Member Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=153522013-02-22T18:00:25ZSkye Roseboomsroseboo@dataone.unm.edu
<ul><li><strong>Parent task</strong> changed from <i>#3568</i> to <i>#3559</i></li><li><strong>Project</strong> changed from <i>Infrastructure</i> to <i>Member Nodes</i></li><li><strong>Category</strong> deleted (<del><i>296</i></del>)</li><li><strong>Assignee</strong> deleted (<del><i>John Kunze</i></del>)</li></ul> Member Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=153602013-02-22T18:26:24ZSkye Roseboomsroseboo@dataone.unm.edu
<ul></ul><p>An example of a document that has been harvested by CN from ONEShare:</p>
<p><a href="https://cn-unm-1.dataone.org/cn/v1/meta/ark:/99999/fk4h42dbf/1/mrt-eml.xml">https://cn-unm-1.dataone.org/cn/v1/meta/ark:/99999/fk4h42dbf/1/mrt-eml.xml</a></p>
<p>however resolving that document will not work:</p>
<p><a href="https://cn-unm-1.dataone.org/cn/v1/resolve/ark:/99999/fk4h42dbf/1/mrt-eml.xml">https://cn-unm-1.dataone.org/cn/v1/resolve/ark:/99999/fk4h42dbf/1/mrt-eml.xml</a><br>
<a href="https://oneshare.unm.edu/knb/d1/mn/v1/object/ark:%2F99999%2Ffk4h42dbf%2F1%2Fmrt-eml.xml">https://oneshare.unm.edu/knb/d1/mn/v1/object/ark:%2F99999%2Ffk4h42dbf%2F1%2Fmrt-eml.xml</a><br>
<a href="https://oneshare.unm.edu/knb/d1/mn/v1/meta/ark:%2F99999%2Ffk4h42dbf%2F1%2Fmrt-eml.xml">https://oneshare.unm.edu/knb/d1/mn/v1/meta/ark:%2F99999%2Ffk4h42dbf%2F1%2Fmrt-eml.xml</a></p>
Member Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=154012013-02-22T20:43:23ZJohn Kunzejak@ucop.edu
<ul></ul><p>Here is a list of the PIDs that are most likely still in the CN, but have been removed from our ONEShare MN. I think it's the same as the original list.</p>
<p>They were submitted in error by our tech writer and should all no longer be available on the CN, so please 'archive' those PIDS.</p>
<p>ark:/99999/fk40c5hpb/1/17.01.2013_<em>-</em>_18.01.2013-DailyReport.csv<br>
ark:/99999/fk40c5hpb/1/mrt-dataone-map.rdf<br>
ark:/99999/fk40c5hpb/1/mrt-eml.xml<br>
ark:/99999/fk4h42dbf/1/mrt-dataone-map.rdf<br>
ark:/99999/fk4h42dbf/1/mrt-eml.xml<br>
ark:/99999/fk4h42dbf/1/SecondFile-algae.csv<br>
ark:/99999/fk4h42dbf/1/SecondFile-Oct_7to15.csv<br>
ark:/99999/fk4h42dbf/1/SecondFile-pop_size.csv<br>
ark:/99999/fk4h42dbf/1/SecondFile-scope_data.csv</p>
<p>Is there a way we can do this ourselves in the future?</p>
Member Nodes - Task #3567: Unresolvable content on CN from ONESharehttps://redmine.dataone.org/issues/3567?journal_id=277072016-06-03T13:43:45ZLaura Moyerslmoyers1@utk.edu
<ul></ul><p>This is what I am seeing as of 6/2/16, which is not exactly the same as what we were seeing before (bolded ones are the same):</p>
<p><em>ark:/99999/fk40c5hpb/1/17.01.2013_<em>-</em>_18.01.2013-DailyReport.csv</em><br>
ark:/99999/fk4d813mb/1/mrt-dataone-map.rdf<br>
ark:/99999/fk4d813mb/1/mrt-eml.xml<br>
<em>ark:/99999/fk4h42dbf/1/SecondFile-algae.csv<br>
ark:/99999/fk4h42dbf/1/SecondFile-Oct_7to15.csv<br>
ark:/99999/fk4h42dbf/1/SecondFile-pop_size.csv<br>
ark:/99999/fk4h42dbf/1/SecondFile-scope_data.csv</em><br>
ark:/99999/fk4d813mb/1/CTD_data3.xlsx</p>
<p>It is likely that I have missed some in my cursory review. We need someone from ONEShare to investigate the content currently on the production ONEShare MN (i.e. discoverable via DataONE) and determine which objects should be archived. DataONE can help by showing/telling the ONEShare person how to accomplish this.</p>