https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2018-04-16T14:32:03ZDataONE TasksMember Nodes - Task #8511: Figshare: Develop or Implement MN Softwarehttps://redmine.dataone.org/issues/8511?journal_id=302382018-04-16T14:32:03ZMonica Ihliemail@monicaihli.com
<ul></ul><p>Figshare confirms that identifier handling can vary from source to source. Will ensure that identifier handling is individually mediated within adapter code. </p>
Member Nodes - Task #8511: Figshare: Develop or Implement MN Softwarehttps://redmine.dataone.org/issues/8511?journal_id=304732018-06-14T14:04:55ZAmy Forresteraforres4@utk.edu
<ul></ul><p>6/13/18: from Tudor Panescu <a href="mailto:tudor@figshare.com">tudor@figshare.com</a></p>
<blockquote>
<p>As the Cary Institute has just recently moved to production, I wanted to be sure to share this update with you, but also to provide you with this information, which I believe you'll find helpful as we finalize everything: <a href="https://api.figshare.com/v2/oai?verb=ListRecords&metadataPrefix=oai_dc&set=portal_376">https://api.figshare.com/v2/oai?verb=ListRecords&metadataPrefix=oai_dc&set=portal_376</a>. </p>
</blockquote>
Member Nodes - Task #8511: Figshare: Develop or Implement MN Softwarehttps://redmine.dataone.org/issues/8511?journal_id=307702018-08-28T14:12:49ZMonica Ihliemail@monicaihli.com
<ul></ul><p><strong>Finalizing Figshare Identifier handling:</strong></p>
<ul>
<li>“no matter how many versions a figshare items has, in OAI-PMH you will always see one record (with a persistent OAI identifier). What changes between versions is the value of, for example, dc:identifier field, which will reflect the latest DOI that was minted for that specific item.”</li>
<li>Minor changes may not be reflected in version number (dc: identifier) change.</li>
<li>However, even minor changes WILL appear in OAI harvest, regardless of whether or not identifier changes, because date modified will change.</li>
<li>So our question: Do we want to enforce versioning via checksum or can we just allow the MN to decide what versions they want to enforce.</li>
<li>ANSWER: We will FOR NOW use contents of OAI-PMH identifier (system identifier) for SID dc:identifier (doi) as the PID for now, understanding that some minor revisions will not be captured. However, will explore future solutions for improving upon this.</li>
<li>Will look at adding a log entry to keep track of how often a record appears with new modified date but without a change to dc:identifier field</li>
</ul>
Member Nodes - Task #8511: Figshare: Develop or Implement MN Softwarehttps://redmine.dataone.org/issues/8511?journal_id=309032018-09-25T14:20:07ZMonica Ihliemail@monicaihli.com
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Assignee</strong> set to <i>Monica Ihli</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul>