DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2010-03-25T02:08:10ZDataONE Tasks
Redmine Requirements - Requirement #431 (New): (Requirement) Software developed for infrastructure should...https://redmine.dataone.org/issues/4312010-03-25T02:08:10ZDave Vieglaisdave.vieglais@gmail.com
<p>Software should be implemented according the the design and specifications.</p>
<p>Rationale</p>
<p>Software being developed to implement the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure includes a number of different components and systems that interact to provide an expected level of functionality expressed in the design and specifications documentation. Hence the software needs to conform to the specifications, and the specifications need to be sufficiently complete.</p>
<p>Fit Criteria</p>
<ul>
<li>Software passes unit testing</li>
<li>Applications meet or exceed performance metrics</li>
<li>Apps interact as expected</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 #410 (New): (Requirement) The infrastructure must support long term pr...https://redmine.dataone.org/issues/4102010-03-24T15:23:06ZDave Vieglaisdave.vieglais@gmail.com
<p>The infrastructure developed by <a href="DataNets in general" class="external">[DataONE]</a> must promote the preservation of data. This is a requirement of the RFP</p>
<p>There are many aspects to preservation. These are addressed by the requirements on which this entry depends (i.e. Blocked By)</p>
<p>Rationale</p>
<p>Preservation of data encourages re-use of existing content.</p>
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 #385 (New): (Requirement) Support arbitrary unique identifiershttps://redmine.dataone.org/issues/3852010-03-16T22:09:36ZDave Vieglaisdave.vieglais@gmail.com
<p><a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyber-infrastructure will need to support a wide ranger of identifiers including, but not limited to: unique strings, LSIDs, Handles, DOIs, URIs.</p>
<p>Rationale</p>
<p><a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> will be integrated with many types of data provider which utilize a variety of identifier schemes. It is not feasible to expect all data providers to be able to handle arbitrary object identifiers when replicating content between member nodes. Hence, the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> core cyber-infrastructure should be identifier agnostic.</p>
<p>Fit Criteria</p>
<ul>
<li>Any type of unique identifier can be supported by Coordinating Nodes</li>
<li>Some Member Nodes can be adapted to support any type of identifier</li>
</ul>
Requirements - Requirement #383 (New): (Requirement) System supports data storagehttps://redmine.dataone.org/issues/3832010-03-16T21:35:55ZDave Vieglaisdave.vieglais@gmail.com
<p>The <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure must provide a mechanism supporting the storage of data and metadata (seems kind of obvious, but it is a requirement).</p>
<p>Rationale</p>
<p>This is a fundamental requirement of the infrastructure addressing the RFP.</p>
<p>Fit Criteria</p>
<ul>
<li><p>data and metadata can be stored into the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure and be retrieved at a later time</p></li>
<li><p>Existing data with associated metadata can be added to the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> infrastructure</p></li>
</ul>
Requirements - Requirement #374 (New): (Requirement) Periodic Reporting to Sponsorhttps://redmine.dataone.org/issues/3742010-03-16T18:11:33ZDave Vieglaisdave.vieglais@gmail.com
<p>It is a requirement that the project provides quarterly and annual reports to the project sponsor.</p>
<p>Rationale</p>
<p>The reporting indicates overall project progress and related information for the sponsor organization.</p>
<p>Fit Criteria</p>
<ul>
<li>Reports are produced on schedule</li>
<li>reports provide appropriate information</li>
<li>Reports are easy to generate</li>
</ul>
Requirements - Requirement #371 (New): (Requirement) Provide a suite of collaboration tools and i...https://redmine.dataone.org/issues/3712010-03-16T17:59:05ZDave Vieglaisdave.vieglais@gmail.com
<p>Collaboration tools are critical for maintaining project content and fostering communications between project members. </p>
<p>Rationale</p>
<p>This is a distributed project and some discipline is necessary to ensure that all project participants have at least the opportunity to discover and share information needed to ensure progress of the project. Appropriate tools supporting collaboration need to be enabled and participants need suitable instruction and documentation about their use.</p>
<p>Fit Criteria</p>
<ul>
<li>All project information is stored in an accessible location</li>
<li>Project participants are aware of the mechanisms for storing, sharing, and discovering content</li>
<li>No documents sent around by email</li>
<li>Participants have the necessary materials to self-educate and ask questions where necessary about the collaboration tools</li>
</ul>
Requirements - Requirement #339 (New): (Requirement) Web presence to provide publicly accessible ...https://redmine.dataone.org/issues/3392010-03-12T15:25:30ZDave Vieglaisdave.vieglais@gmail.com
<p><a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> is a high profile project that has the potential to influence a very large audience. As such, it is beneficial to provide a resource where the public (i.e. non-authenticated users) can discover information about the project, see updated news items and generally keep informed about project progress and activities.</p>
<p>Rationale</p>
<p><a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> provides infrastructure for the community so it is useful to help the community keep informed about the cool stuff we're doing.</p>
<p>Fit Criteria</p>
<ul>
<li>events and news are advertised on the web site</li>
<li>mechanisms are provided for subscribing to notifications (feeds, email)</li>
<li>some measurement of community awareness increases over the life of the project. </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>