DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2010-03-19T03:21:11ZDataONE Tasks
Redmine Requirements - Requirement #392 (New): (Requirement) Identity and access control should be intero...https://redmine.dataone.org/issues/3922010-03-19T03:21:11ZDave Vieglaisdave.vieglais@gmail.com
<p>There is a general requirement / suggestion by NSF that there should be interoperability between the various <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataNet">DataNet</a> projects. Rationale: It seems like identity and access control is a good place where considerable value can be demonstrated to the user community if credentials and access control rules worked across the data net projects.</p>
<p>Fit Criteria<br>
* Users can sign into <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> and DC with the same credentials<br>
* Once signed in to <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a>, access to DC services is seamless (no additional authentication required)</p>
Requirements - Requirement #391 (New): (Requirement) Enable different classes of users commensura...https://redmine.dataone.org/issues/3912010-03-17T16:15:31ZDave Vieglaisdave.vieglais@gmail.com
<p>There are several types of users that will be interacting with the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> infrastructure, as such it is necessary to ensure that user roles can be supported by the identity management infrastructure. Closely related to <a href="https://trac.dataone.org/ticket/390">https://trac.dataone.org/ticket/390</a></p>
<p>Rationale: Different user classes or groups provides an effective mechanismfor indicating the types of interaction that might be supported by the system. The alternative is to specifically assign privileges for each user - an<br>
approach that is inefficient and potentially insecure as it is easy to miss an<br>
individual when setting privileges for a large number of users.</p>
<p>Fit Criteria</p>
<ul>
<li><p>A well defined set of standard groups is identified and can be easily manage (e.g. administrators, data contributors, data readers)</p></li>
<li><p>Users can be assigned to and removed from groups </p></li>
<li><p>Additional groups can be created to support group functions as necessary </p></li>
<li><p>Users can create their own groups for ad-hoc collaboration when needed and without approval of system administrators </p></li>
<li><p>Access control rules can be associated with groups and operate as expected.</p></li>
</ul>
Requirements - Requirement #390 (New): (Requirement) Consistent mechanism for identifying usershttps://redmine.dataone.org/issues/3902010-03-17T16:10:03ZDave Vieglaisdave.vieglais@gmail.com
<p>It is necessary to provide a mechanism for users to be identified in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> system. There are several distinct roles that need to be supported for users.Rationale: Identity of users, contributors and other participants in <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> is necessary to ensure appropriate policies for data sharing (read, write), attribution, and notification (e.g. subscription to types of data).</p>
<p>Fit Criteria</p>
<ul>
<li>Users can identify themselves in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> system </li>
<li>Identity is consistent across all nodes (i.e. identity associated with an object is consistent regardless of where the object is retrieved from or acted on) </li>
<li>Users can associate various accounts with a single identity</li>
<li>Identity information is sufficient to ensure appropriate attribution to content </li>
<li>Authentication and authorization mechanisms are recognized consistently by all participant nodes and services of the cicore.<br></li>
<li>Existing user directories in use in environmental science community can directly contribute identities (not "yet another" identity system)</li>
</ul>
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 #384 (New): (Requirement) Enable efficient mechanisms for users to dis...https://redmine.dataone.org/issues/3842010-03-16T22:03:21ZDave Vieglaisdave.vieglais@gmail.com
<p>There will likely be a very large number of data and metadata objects cataloged by the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> infrastructure. These are accessible by their unique identifiers, but it is also necessary to provide mechanisms for users to discover content that is relevant to some purpose.</p>
<p>Rationale</p>
<p>Without a mechanism to search content, <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> will be little more than a large hash table - a useful functionality in itself but insufficient to help users discover useful information.</p>
<p>Fit Criteria</p>
<ul>
<li>A mechanism to search the entire holdings of <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> is available</li>
<li>Searches are possible using fields useful to to the users</li>
<li>Searches return accurate results</li>
<li>Searches support precise results</li>
<li>Searches are fast. (how fast?)</li>
<li>the user community is satisfied with the search functionality</li>
<li>Searches can be performed using tools familiar to the users (web browser, analytical tools)</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>
Requirements - Requirement #318 (New): (Requirement) Sponsor required Y1 functionalityhttps://redmine.dataone.org/issues/3182010-03-10T17:12:42ZDave Vieglaisdave.vieglais@gmail.com
<p>The project sponsor has specified that a minimum of three Coordinating Nodes and three Member Nodes will be stood up and operational at the end of the first year of the project (i.e. 2010-07-31).</p>
<p>Rationale:: It's something the sponsor, or the directors of the sponsor need to see for assurance of progress.</p>
<p>Fit Criteria:: By the end of year one of the project (i.e. 2010-07-31) there will be at least:</p>
<ul>
<li><p>three operational coordinating nodes</p></li>
<li><p>three operational member nodes</p></li>
<li><p>Basic mirroring of content between CNs and replication of content from MNs should be enabled.</p></li>
</ul>