DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2018-10-02T16:51:19ZDataONE Tasks
Redmine Member Nodes - Task #8723 (New): tDAR: Implemented IP Whitelisting on tDAR systems / Impacts to r...https://redmine.dataone.org/issues/87232018-10-02T16:51:19ZMonica Ihliemail@monicaihli.com
<p>tdar has implemented IP whitelisting on their member node. Requests from IP addresses not whitelisted will be refused. Was provided CN IPs for production. The reports that ping Tdar MN for up status will fail unless it happens to be executed from an IP that can be provided. This may or may not be considered a big enough issue to do something about. No harm is actually being done as long as the CNs can get in and do their business. </p>
Python Libraries - Task #7821 (New): Verify Expect: 100-Continue header on POST or PUT requestshttps://redmine.dataone.org/issues/78212016-05-31T20:55:02ZRobert Waltz
<p>We may be adding support for the 100-Continue header in order to successfully upload content on some member node servers.</p>
<p>More description of the header's use from a Java client:</p>
<pre> 'Expect: 100-Continue' handshake for the entity enclosing methods.
The purpose of the Expect: 100-Continue handshake is to allow the client
that is sending a request message with a request body to determine if
the origin server is willing to accept the request (based on the request
headers) before the client sends the request body. The use of the
Expect: 100-continue handshake can result in a noticeable performance
improvement for entity enclosing requests (such as POST and PUT) that
require the target server's authentication.
https://hc.apache.org/httpcomponents-client-4.2.x/tutorial/html/fundamentals.html
</pre> Member Nodes - MNDeployment #7163 (New): UN Environmental Programme World Conservation Monitoring...https://redmine.dataone.org/issues/71632015-06-07T17:14:16ZLaura Moyerslmoyers1@utk.edu
<p>Key holding: World database of protected lands<br>
Dependencies: They are in the process of implementing CSW. So, we need the slender node and we need them to get their CSW up.<br>
Location: Cambridge, England</p>
Python GMN - Story #7095 (New): Support HTTP redirect capability for GMN within the Vendor Specif...https://redmine.dataone.org/issues/70952015-05-12T16:20:39ZMark Servillamark.servilla@gmail.com
<p>GMN provides proxy capabilities to integrate existing content residing in a back-end data repository through its Vendor Specific Extension model. Only minimal support exists within the GMN-VSE model for HTTP redirects. Although the use of HTTP redirects is more of an exception within the the GMN-VSE model, it can provide a flexible mechanism for MNs who dynamically manage data and metadata objects.</p>
Member Nodes - MNDeployment #6359 (New): SiBBrhttps://redmine.dataone.org/issues/63592014-09-05T19:38:43ZBen Leinfelderleinfelder@nceas.ucsb.edu
<p>At a GBIF-sponsored workshop/meeting in Petropolis, I did a few seminars on Metacat and Morpho. There's potential interest in a MN if/when they set up a Metacat repository for their ecological data research as part of the larger biodiversity/LTER-style network they are building.<br>
<a href="http://www.sibbr.gov.br/">http://www.sibbr.gov.br/</a><br>
Primary contact: Luiz Gadelha <a href="mailto:lgadelha@lncc.br">lgadelha@lncc.br</a><br>
Debora Drucker (who we know from PPBIO/PELD) is also aware of this initiative and supports the idea of a centralized repository hosted at LNCC (national scientific computing lab).</p>
Member Nodes - MNDeployment #4227 (New): TRY Plant Trait Databasehttps://redmine.dataone.org/issues/42272014-01-17T11:48:28ZLaura Moyerslmoyers1@utk.edu
<p>Jens Kattge directs the international Plant Traits Database and is interested in joining DataONE as a Member Node. (Initial contact with Bill.)</p>
<p>Contact info:<br>
Jens Kattge <a href="mailto:jkattge@bgc-jena.mpg.de">jkattge@bgc-jena.mpg.de</a> <br>
website: <a href="http://www.try-db.org" class="external">www.try-db.org</a></p>
Infrastructure - Task #3763 (New): Visualize PyPI download statistics for Python componentshttps://redmine.dataone.org/issues/37632013-05-14T21:11:04ZRoger Dahldahl@unm.edu
<p>Create a tool that gets download statistics for DataONE software distributed on PyPI and generates graphs that show how number of downloads change over time.</p>
Infrastructure - Task #2147 (New): The Python stack does not support Unicode supplementary charac...https://redmine.dataone.org/issues/21472011-12-20T15:44:22ZRoger Dahldahl@unm.edu
<p>When given this identifier:</p>
<p>common-unicode-supplementary-escaped-</p>
Requirements - Requirement #581 (New): (Requirement) System supports multiple types of science me...https://redmine.dataone.org/issues/5812010-04-20T20:28:56ZDave Vieglaisdave.vieglais@gmail.com
<p>The <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> cyberinfrastructure should be able to support the range of science metadata types in common use.</p>
<p>Rationale</p>
<p>Science metadata describes the data in ways that support discovery, understanding, and re-use of the data. There are multiple types of science metadata in common use, and so the system should support a range of metadata formats commensurate with the needs of the community.</p>
<p>Fit Criteria</p>
<p>**** Multiple formats of metadata can be stored in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> system.</p>
<p>**** Multiple metadata formats are supported in the <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1req/wiki/DataONE">DataONE</a> operations (e.g. search) </p>
<p>**** New metadata formats can be supported by the system</p>
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 #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 #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 #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>