DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2010-05-28T20:10:08ZDataONE Tasks
Redmine Requirements - Requirement #632 (New): (Requirement) Monitor the DataONE infrastructurehttps://redmine.dataone.org/issues/6322010-05-28T20:10:08ZDave Vieglaisdave.vieglais@gmail.com
<p>The <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> project should have a monitoring system that is able to report on overall system health and notify administrators or oather responsible parties when problems arise.</p>
<p>Rationale</p>
<p><a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> is a distributed infrastructure with a premise of high availability. Monitoring helps with not only performance tuning, but also improves responsiveness to failures or unusual events should they emerge.</p>
<p>Fit Criteria</p>
<ul>
<li><p>System administrators should be notified if a node or service is not accessible.</p></li>
<li><p>reports on uptime, load, performance, capacity should be available to project participants and perhaps the public.</p></li>
</ul>
Requirements - Requirement #580 (New): (Requirement) All software developed on the project should...https://redmine.dataone.org/issues/5802010-04-15T22:52:38ZDave Vieglaisdave.vieglais@gmail.com
<p>It is necessary (desired and indicted in proposal) that all products developed on the project would be released with an appropriate, recognized open source license.</p>
<p>h2. Rationale</p>
<p>Open source is a good thing. See <a href="http://www.opensource.org/docs/definition.php">http://www.opensource.org/docs/definition.php</a> for more details.</p>
<p>h2. Fit Criteria</p>
<ul>
<li>All software developed on the project includes an approved open source license</li>
<li>Selected licenses do not conflict with the licenses used by components that are extended or utilized by custom software developed on the project</li>
<li>A software license audit can be successfully passed. </li>
</ul>
Requirements - Requirement #468 (New): (Requirement) Design the cyberinfrastructure for the project.https://redmine.dataone.org/issues/4682010-03-25T16:51:33ZDave Vieglaisdave.vieglais@gmail.com
<p>One of those obvious requirements that just needs to be captured for consistency.</p>
<p>Rationale</p>
<p>Building infrastructure without a design is generally a bad thing to do, and typically leads to problems. e.g. things built in the wrong order, pieces that don't work as expected, incompatibilities between independently developed components, etc. </p>
<p>Fit Criteria</p>
<ul>
<li>A design is available for all software being developed</li>
<li>The design can be effectively communicated with project participants</li>
<li>The design addresses the expected functionality, requirements, and capabilities.</li>
</ul>
Requirements - Requirement #455 (New): (Requirement) Installation of critical software must be we...https://redmine.dataone.org/issues/4552010-03-25T13:52:04ZDave Vieglaisdave.vieglais@gmail.com
<p>Custom software being developed on the project should be easy to install, especially for cases where the software fills a critical role in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> infrastructure (e.g. CN, MN, or ITK components / applications)</p>
<p>Rationale</p>
<p>Software that is difficult to install is not only annoying but likely to introduce bugs due to uncertainties about various stages of installation (e.g. library dependencies, configuration settings, assumed system capabilities). The installation process for all software developed on the project must be documented, and where possible, automated through one of the well known package installation mechanisms appropriate for the target operating system(s).</p>
<p>Fit Criteria</p>
<ul>
<li><p>Software can be installed by a third party without consulting the developer</p></li>
<li><p>No complaints about hassles installing software</p></li>
<li><p>Software can be distributed through a well known packaging system</p></li>
</ul>
Requirements - Requirement #439 (New): (Requirement) Maintain original copies of all science meta...https://redmine.dataone.org/issues/4392010-03-25T03:27:13ZDave Vieglaisdave.vieglais@gmail.com
<p>Original copies of science metadata will be preserved.</p>
<p>Rationale</p>
<p>The science metadata provides the detailed information describing a data set, including but not limited to who collected the data, what the data was collected for, how it was collected, and what the data values represent. This information is crucial for interpreting the associated data and for determining if a data set may be appropriate for some other use (including discovery and relevance).</p>
<p>Fit Criteria</p>
<ul>
<li>Original copies of science metadata are stored within XXX minutes of appearing</li>
<li>Copies of science metadata can be verified as being exact duplicates</li>
</ul>
Requirements - Requirement #433 (New): (Requirement) Data and metadata is replicated to at least ...https://redmine.dataone.org/issues/4332010-03-25T03:01:56ZDave Vieglaisdave.vieglais@gmail.com
<p>Data is copied verbatim to at least one other node.</p>
<p>Rationale<br>
Replicating information helps to ensure availability after (random or intentional) node inaccessibility. Choices for multiple data retrieval locations improves access efficiency and scalability.</p>
<p>Fit Criteria</p>
<ul>
<li>Copies of data and metadata are available from more than a single node</li>
<li>Node failure does not prevent data availability</li>
<li>Data and metadata are replicated to at least one other node within XXX minutes of appearing on a Member Node</li>
</ul>
Requirements - Requirement #412 (New): (Requirement) Identifiers always refer to the same objecthttps://redmine.dataone.org/issues/4122010-03-24T15:47:20ZDave Vieglaisdave.vieglais@gmail.com
<p>Identifiers are the fundamental mechanism for retrieving content from the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> system, and there is an expectation that an identifier will always refer to the same content.</p>
<p>In the case of data, the bytes of the retrieved object must always be the same, regardless of which node it is being retrieved from (checksum consistency).</p>
<p>In the case of science metadata, the behavior is not as precise. The original science metadata is always preserved (on a CN). The copies of science metadata distributed to Member Nodes <em>may</em> change depending on the functionality of the member node. </p>
<p>Rationale</p>
<p>Data consistency is an important aspect of preservation and enhances the re-use of information.</p>
<p>Fit Criteria</p>
<ul>
<li><p>Independently computed checksums of a randomly selected data object drawn from any nodes match the original value in the system metadata</p></li>
<li><p>Objects retrieved from a CN always match the system metadata checksum.</p></li>
</ul>
Requirements - Requirement #409 (New): (Requirement) Develop a reference implementation of the Me...https://redmine.dataone.org/issues/4092010-03-24T13:41:38ZDave Vieglaisdave.vieglais@gmail.com
<p>A reference implementation of the Member Node software should be developed in a standalone system that is able to be connected with a variety of data sources.</p>
<p>Rationale</p>
<p>This will be less efficient than directly implementing MN functionality on the target repository (e.g. MN API in Metacat), but provides a flexible alternative for rapid deployment.</p>
<p>Fit Criteria</p>
<ul>
<li>The reference implementation is able to operate as a standalone Member Node</li>
<li>Fully implements the Member Node APIs</li>
<li>Passes all tests of MN functionality</li>
</ul>
Requirements - Requirement #408 (New): (Requirement) Implement a Coordinating Node software stackhttps://redmine.dataone.org/issues/4082010-03-24T12:55:59ZDave Vieglaisdave.vieglais@gmail.com
<p>This is a requirement to meet the objectives of the proposed work. </p>
<p>It is referenced by the Cooperative Agreement as a target for year one milestone.</p>
Requirements - Requirement #389 (New): (Requirement) Implement a Member Node based on the ORNL DAAChttps://redmine.dataone.org/issues/3892010-03-17T14:16:25ZDave Vieglaisdave.vieglais@gmail.com
<p>The "ORNL DAAC":<a href="http://daac.ornl.gov/">http://daac.ornl.gov/</a> (Oak Ridge National Laboratory Distributed Active Archive Center) was identified as a candidate Member Node for the year one implementation (<a class="issue tracker-8 status-1 priority-5 priority-high3" title="Requirement: (Requirement) Sponsor required Y1 functionality (New)" href="https://redmine.dataone.org/issues/318">#318</a>, <a class="issue tracker-8 status-1 priority-3 priority-lowest" title="Requirement: (Requirement) Deploy at least three Member Nodes (New)" href="https://redmine.dataone.org/issues/386">#386</a>) during the source:/documents/Committees/CCIT/20091117_CCIT_Knoxville meeting.</p>
<p>Rationale</p>
<p>The ORNL DAAC has significant holdings relevant to the overall goals of the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> project. The system has hooks into which the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> MN APIs can be integrated. The "NBII clearing house":<a href="http://mercury.ornl.gov/clearinghouse/">http://mercury.ornl.gov/clearinghouse/</a> is based on similar / the same technology so enabling MN capabilities with the DAAC should do likewise for the NBII clearing house.</p>
<p>Fit Criteria</p>
<ul>
<li>The necessary <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> MN APIs are implemented on the ORNL DAAC</li>
<li>Holdings of the DAAC are accessible through the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> MN APIs</li>
</ul>
Requirements - Requirement #388 (New): (Requirement) Implement a Member Node based on Dryadhttps://redmine.dataone.org/issues/3882010-03-17T13:56:57ZDave Vieglaisdave.vieglais@gmail.com
<p>Dryad was one of the four targets identified for participation as a member node for the year one milestone (<a class="issue tracker-8 status-1 priority-5 priority-high3" title="Requirement: (Requirement) Sponsor required Y1 functionality (New)" href="https://redmine.dataone.org/issues/318">#318</a>, <a class="issue tracker-8 status-1 priority-3 priority-lowest" title="Requirement: (Requirement) Deploy at least three Member Nodes (New)" href="https://redmine.dataone.org/issues/386">#386</a>). This decision was made at the source:/documents/Committees/CCIT/20091117_CCIT_Knoxville meeting.</p>
<p>Rationale</p>
<p>"Dryad":<a href="http://datadryad.org/repo">http://datadryad.org/repo</a> provides an API that is a good match for operating as a <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> Member Node and has significant holdings relevant to the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> project.</p>
<p>Fit Criteria</p>
<ul>
<li>The <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> MN APIs are implemented such that Dryad can participate in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure</li>
<li>The data and metadata holdings of Dryad are made available to the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> network</li>
</ul>
Requirements - Requirement #387 (New): (Requirement) Implement a Member Node based on Metacathttps://redmine.dataone.org/issues/3872010-03-17T13:48:37ZDave Vieglaisdave.vieglais@gmail.com
<p>Metacat was one of the four targets identified for participation as a member node for the year one milestone (<a class="issue tracker-8 status-1 priority-5 priority-high3" title="Requirement: (Requirement) Sponsor required Y1 functionality (New)" href="https://redmine.dataone.org/issues/318">#318</a>, <a class="issue tracker-8 status-1 priority-3 priority-lowest" title="Requirement: (Requirement) Deploy at least three Member Nodes (New)" href="https://redmine.dataone.org/issues/386">#386</a>). This decision was made at the source:/documents/Committees/CCIT/20091117_CCIT_Knoxville meeting.</p>
<p>Rationale</p>
<p>Metacat provides a good API for interaction with the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure and significant holdings relevant to <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> are available through the various Metacat instances around the world.</p>
<p>Fit Criteria</p>
<ul>
<li>The <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> MN APIs are implemented on Metacat</li>
<li>Metacat is able to operate as a Member Node in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure</li>
</ul>
Requirements - Requirement #386 (New): (Requirement) Deploy at least three Member Nodeshttps://redmine.dataone.org/issues/3862010-03-17T13:39:36ZDave Vieglaisdave.vieglais@gmail.com
<p>As part of the cooperative agreement, it is necessary for <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> to stand up three Member Nodes by the end of the first year.</p>
<p>Rationale</p>
<p>This is a requirement of the CA. The intent is perhaps to demonstrate significant progress on the implementation of the proposed infrastructure.</p>
<p>Fit Criteria</p>
<ul>
<li>Prototype member node functionality is designed</li>
<li>Targets for the prototype member nodes have been identified</li>
<li>Software implementations for the target member nodes are available</li>
<li>Deployed member nodes effectively participate in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure</li>
</ul>
Requirements - Requirement #337 (New): (Requirement) Deploy three coordinating nodeshttps://redmine.dataone.org/issues/3372010-03-12T14:48:28ZTest Dataone Userdvieglais@gmail.com
<p>As indicated in the proposal, we need to deploy three coordinating nodes. One at UNM, one at NCEAS, one at ORC.</p>
<p>Rationale</p>
<p>This is a requirement of the cooperative agreement for the year one milestones (<a class="issue tracker-8 status-1 priority-5 priority-high3" title="Requirement: (Requirement) Sponsor required Y1 functionality (New)" href="https://redmine.dataone.org/issues/318">#318</a>) (prototype implementations of the CNs installed and synchronizing content between themselves). It is also a stated goal in the proposal.</p>
<p>Fit Criteria</p>
<ul>
<li><p>Three coordinating node instances installed, one at UNM, one at NCEAS, one at ORC</p></li>
<li><p>CNs synchronizing content</p></li>
<li><p>CNs retrieving content (science metadata) from MNs</p></li>
<li><p>Clients able to retrieve content from CNs</p></li>
<li><p>Clients able to search CNs</p></li>
</ul>
Requirements - Requirement #317 (In Progress): (Requirement) Identifiers for all objectshttps://redmine.dataone.org/issues/3172010-03-10T16:57:35ZDave Vieglaisdave.vieglais@gmail.com
<p>All objects in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> system have an identifier that is unique within all of the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> infrastructure and can be used to retrieve the object from the system.</p>
<p>Rationale:</p>
<p>Unique identifiers provide the fundamental, low level mechanism for<br>
interacting with content stored in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> system. Unique identifiers help prevent duplication and improve re-usability of information.</p>
<p>Fit Criteria:</p>
<ul>
<li><p>Any object stored within <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> receives an identifier that is unique within the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> infrastructure.</p></li>
<li><p>Any object with a <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> identifier can be retrieved from the infrastructure.</p></li>
<li><p>Attempts to create a duplicate identifier are prevented.</p></li>
</ul>