DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2019-05-21T13:00:12ZDataONE Tasks
Redmine CN REST - Task #8810 (New): Verify configuration of portal certificateshttps://redmine.dataone.org/issues/88102019-05-21T13:00:12ZDave Vieglaisdave.vieglais@gmail.com
<p>Verify that the postinst scripts for dataone-cn-os-core and dataone-cn-portal are correctly setting the locations of the certificates for token signing.</p>
Infrastructure - Task #8369 (New): Verify operation and transfer DNShttps://redmine.dataone.org/issues/83692018-02-15T17:40:32ZDave Vieglaisdave.vieglais@gmail.com
<p>Verify that projects are being built properly and then switch DNS for both the jenkins repo and the maven repo.</p>
Member Nodes - Task #8247 (New): Verify upgraded metacat is operating correctly as a production m...https://redmine.dataone.org/issues/82472018-01-22T16:41:13ZDave Vieglaisdave.vieglais@gmail.comInfrastructure - Task #8066 (New): Verify completeness of unit test MetacatRdfXmlSubprocessorTesthttps://redmine.dataone.org/issues/80662017-04-11T23:47:32ZPeter Slaughterslaughter@nceas.ucsb.edu
<p>Verify that all prov relationships that are indexed via src/main/resources/application-context-prov-base.xml are inspected by the unit test MetacatRdfXmlSubprocessorTest.java which reads src/test/resources/rdfxml-example.xml.</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> DUG - Task #7475 (New): Work with Erin/ESIP to distribute the brochure widely to students/faculty...https://redmine.dataone.org/issues/74752015-11-09T22:38:20ZDave Vieglaisdave.vieglais@gmail.comInfrastructure - Decision #6705 (New): What behavior should be when a user request a sid when all...https://redmine.dataone.org/issues/67052014-12-10T20:07:24ZJing Taotao@nceas.ucsb.edu
<p>Here is the definition of "current" in this page <a href="http://jenkins-1.dataone.org/jenkins/job/API%20Documentation%20-%20trunk/ws/api-documentation/build/html/design/ContentMutability.html">http://jenkins-1.dataone.org/jenkins/job/API%20Documentation%20-%20trunk/ws/api-documentation/build/html/design/ContentMutability.html</a> :</p>
<p>DataONE defines the latest version as “current” if the object in question has a matching SID and no value in the “obsoletedBy” field, regardless if it is “archived” or not. Consumers of the data should inspect the system metadata and/or search results to determine if the object has been explicitly archived if they are concerned about using stale data.</p>
<p>We have two pids with the same sid and their system metadata looks like:</p>
<p>pid sid obsoletes obsoletedBy<br>
p1 s1 p2<br>
p2 s1 p1</p>
<p>If we call get(s1), p2 should be returned base on the above definition.</p>
<p>Now, we insert another object p3 with the update method. The p3 object has another sid - s2 and it obsoletes p2. So the system metadata will look like:<br>
pid sid obsoletes obsoletedBy<br>
p1 s1 p2<br>
p2 s1 p1 p3<br>
p3 s2 p2</p>
<p>If we call get(s2), p3 should be returned. </p>
<p>If we call get(s1), what should be returned? The p2 or the NotFound exception?<br>
Base on the above definition, I believe that the NotFound exception should be returned since there is no a pid which matches the s1 and does't have a value on the "obsoletedBy".</p>
Infrastructure - Bug #5582 (New): xinetd not supported via debian installhttps://redmine.dataone.org/issues/55822014-07-16T04:22:26ZRobert Waltz
<p>on stage and production nodes, xinetd is configured to allow check_mk_agent to be run from 129.237.201.155 or 128.111.84.5. </p>
<p>the configuration settings should either be automated with dataone-cn-os-core or be removed from operations.</p>
Member Nodes - Task #5122 (New): Verify/update information in TFRI's node registrationhttps://redmine.dataone.org/issues/51222014-04-17T15:19:36ZSkye Roseboomsroseboo@dataone.unm.edu
<p>It looks like the node registration information for TFRI has been recently updated - and some funny values have snuck in:</p>
<p><a href="https://cn.dataone.org/cn/v1/node/urn:node:TFRI">https://cn.dataone.org/cn/v1/node/urn:node:TFRI</a></p>
<p>In particular, these values:</p>
<p>Name - metacat (used to be TFRI Data Catalog)<br>
Description - TFRI metacat</p>
Infrastructure - Bug #3869 (New): wrong key set in portal/WEB-INF/client.xmlhttps://redmine.dataone.org/issues/38692013-07-24T17:30:08ZRobert Waltz
<p>In the production portal debian installation, the file</p>
<p>/var/lib/tomcat6/webapps/portal/WEB-INF/client.xml</p>
<p>incorporated the setting:</p>
<p>/etc/ssl/private/dataone_org.key.pk8</p>
<p>rather than</p>
<p>/etc/ssl/private/dataone.org.key.pk8</p>
<p>there are two files in /etc/ssl/private/ <br>
dataone_org.key and dataone.org.key<br>
-rw------- 1 root root 1675 2012-06-05 02:57 dataone_org.key<br>
-rw------- 1 root root 1675 2013-07-05 22:12 dataone.org.key</p>
<p>I assume producing the pk8 from dataone.org.key is correct, though there does not seem to be a diff between the two files?</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 #3757 (New): Verify Log reporting in MN Testerhttps://redmine.dataone.org/issues/37572013-05-10T17:42:29ZRobert Waltz
<p>Download a set of slices of the responses from getLogRecords endpoint on MNs and verify via schema that they are valid log records.</p>
<p>Log is the root type</p>
Infrastructure - Task #2791 (New): verify on dev machineshttps://redmine.dataone.org/issues/27912012-05-21T17:41:23ZRobert WaltzInfrastructure - Task #2685 (New): Where's the WIFFM on the DataONE web site for the researcher u...https://redmine.dataone.org/issues/26852012-05-01T15:31:10ZBruce Wilsonbwilso27@utk.edu
<p>For the DataONE web site, where is the WIFFM (What's In It For Me) in no more than 2-3 sentences. This was brought up in the UA/SC working group meeting. </p>
Infrastructure - Task #1226 (New): Verify that cn buildout is using the hudson generated Metacat ...https://redmine.dataone.org/issues/12262011-01-13T14:48:05ZDave Vieglaisdave.vieglais@gmail.com
<p>knb.war should be generated by hudson.</p>
<p>Ensure that: </p>
<ul>
<li><p>knb.war is being used by the cn-buildout</p></li>
<li><p>The latest build of knb.war is available through a persistent URL via hudson</p></li>
</ul>