https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2012-10-03T15:59:42ZDataONE TasksInfrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=137092012-10-03T15:59:42ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Assignee</strong> set to <i>Jing Tao</i></li></ul><p>I think Morpho should keep track of revision history using it's own mechanism and should only be inspired by the DataONE approach. This way we can implement the revision tracking feature using our existing Metacat docids (that encode the revision history in their value) and then moving to the opaque identifiers will be simple when we add support for DataONE.</p>
<p>The general utility is something like:<br>
List RevisionManager.getInstance().getAllRevisions(String identifier)<br>
String RevisionManager.getInstance().getObsoletes(String identifier)<br>
String RevisionManager.getInstance().getObsoletedBy(String identifier)<br>
RevisionManager.getInstance().setObsoletes(String old, String new)<br>
RevisionManager.getInstance().setObsoletedBy(String old, String new)</p>
<p>I'm not sure how best to serialize this information for the actual implementation. Simplest might be two properties files (obsoletes.properties and obsoletedBy.properties) that have key=value pairs of identifiers. Would be a bit of processing (lots of properties.get() calls!) to get the complete list of revisions for any given identifier, but would be very simple storage mechanism.</p>
Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=140372012-10-11T15:33:27ZDave Vieglaisdave.vieglais@gmail.com
<ul><li><strong>Target version</strong> changed from <i>Sprint-2012.37-Block.5.3</i> to <i>Sprint-2012.41-Block.6.1</i></li></ul> Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=140872012-10-14T15:09:14ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li><li><strong>Category</strong> set to <i>Morpho</i></li></ul><p>We have a plan for the implementation (xml+apache configuration lib) that will be generalized for use with Metacat docids and also DataONE systemmetadata versioning.</p>
<p>Matt, Jing, and Ben decide that the revision chain will be different between local and remote locations. For example, an object can be created (<a class="changeset" title="Initial diretory structure." href="https://redmine.dataone.org/projects/d1/repository/revisions/1">r1</a>) and edited locally (<a class="changeset" title="Added initial draft of CCIT WBS" href="https://redmine.dataone.org/projects/d1/repository/revisions/2">r2</a>, <a class="changeset" title="Added some suggestions for naming folders in the meetings folder." href="https://redmine.dataone.org/projects/d1/repository/revisions/3">r3</a>) before being saved to the network for the first time (<a class="changeset" title="Added some suggestions for naming folders in the meetings folder." href="https://redmine.dataone.org/projects/d1/repository/revisions/3">r3</a>, no revision history). So the RevisionManager will be per-store (local vs remote).</p>
Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=142552012-10-24T18:20:05ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Target version</strong> changed from <i>Sprint-2012.41-Block.6.1</i> to <i>Sprint-2012.44-Block.6.2</i></li></ul> Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=145532012-12-12T16:51:00ZChris Jonescjones@nceas.ucsb.edu
<ul><li><strong>Target version</strong> changed from <i>Sprint-2012.44-Block.6.2</i> to <i>Sprint-2012.50-Block.6.4</i></li></ul> Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=154682013-03-01T18:33:38ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Target version</strong> changed from <i>Sprint-2012.50-Block.6.4</i> to <i>2013.10-Block.2.1</i></li></ul> Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=156862013-03-02T05:30:25ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Parent task</strong> changed from <i>#3075</i> to <i>#3635</i></li></ul> Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=156882013-03-02T05:32:13ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Parent task</strong> changed from <i>#3635</i> to <i>#3074</i></li></ul> Infrastructure - Task #3107: Need a mechanism to keep track the identifer's history (revision)https://redmine.dataone.org/issues/3107?journal_id=158052013-03-25T22:54:15ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>translation missing: en.field_remaining_hours</strong> set to <i>0.0</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>This has been implemented in Morpho. There is some ongoing discussion in the team about how to handle network vs local revision history, but all that traffic is in Bugzilla and the soon to be ecoinformatics redmine instance. <a href="http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5736">http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5736</a></p>