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>
Member Nodes - Task #8645 (New): (Cyverse) Mutual acceptancehttps://redmine.dataone.org/issues/86452018-07-05T14:26:52ZAmy Forresteraforres4@utk.edu
<p>Verify that the content is synchronizing correctly and the search results appear as expected. Member node approves</p>
Member Nodes - Task #8633 (In Progress): DAAC: Re-Training & Re-Deployment Planninghttps://redmine.dataone.org/issues/86332018-07-02T02:41:53ZAmy Forresteraforres4@utk.edu
<p>MN Staff Turnover: Presentation about DataONE systems and technical requirements</p>
<ul>
<li>discuss feasibility of re-deploying with GMN</li>
</ul>
<p><a href="https://docs.google.com/document/d/1SSGL_BMqA1r9W0w_CvQKRmvK7gNOoez_sFXlA7yTWgk/edit?usp=sharing" class="external">DAAC Work Plan</a> Google Doc</p>
Member Nodes - Bug #8622 (New): IOE repository is not respondinghttps://redmine.dataone.org/issues/86222018-06-18T19:04:55ZDave Vieglaisdave.vieglais@gmail.com
<p>Possibly related to <a class="issue tracker-4 status-1 priority-4 priority-default child parent" title="Story: Upgrade Member Node to current version of Metacat (IOE) (New)" href="https://redmine.dataone.org/issues/8244">#8244</a></p>
<p>The IOE repository is not responding at the expected baseURL of:</p>
<p><a href="https://data.rcg.montana.edu/catalog/d1/mn">https://data.rcg.montana.edu/catalog/d1/mn</a></p>
<p>and instead returns an error that SSL connection is not available. Attempting to use http instead of https returns a 404 error.</p>
<p>Contact the server administrator and have them check the service availability.</p>
Member Nodes - Story #8535 (In Progress): Neotoma: Story: Discovery & Planninghttps://redmine.dataone.org/issues/85352018-04-09T21:14:39ZAmy Forresteraforres4@utk.edu
<p>Discovery: establish contact and build relationship with a potential new member node. Determine if DataONE and the repository are a good fit for one another and if the repository generally meets the requirements of DataONE member nodes. </p>
<p>Planning: If the repository and DataONE have agreed to proceed with deployment as a member node. Decisions will be made as to how to proceed with development. Node operators will receive training. </p>
<p>This story is complete when a determination is made to either proceed with planning a new deployment, or that joining DataONE is not an option for the repository at this time.</p>
<p><strong>Record initial communication here</strong></p>
Member Nodes - Task #8523 (In Progress): CAFF: Technical Requirements & Design Planninghttps://redmine.dataone.org/issues/85232018-03-26T15:07:59ZAmy Forresteraforres4@utk.edu
<ul>
<li>Confirm chosen deployment path.</li>
<li>Communicate knowledge of technical requirements for selected deployment. These can include:
<ul>
<li>SSL certificate.</li>
<li>FQDN.</li>
<li>Apache web server with Python 2.7 or Java (depending on stack).</li>
</ul></li>
<li>Confirm metadata format. Communicate expectations for metadata quality.</li>
<li>Specify in advance whether a separate test installation will be maintained in parallel with production. This is important for planning the deployment. A separate test will need distinct subdomain and SSL cert if not using wildcard.</li>
</ul>
<p><strong>Meet to present potential Member Node with Plan and confirm mutual acceptance</strong> <a href="https://docs.google.com/document/d/1nmn_hwHGkG6fpUO4BaiLNHNGJtGe_RKP1eVyf0tknYo/edit?usp=sharing" class="external">ABDS Work Plan</a> Google Doc</p>
<a name="Approval-of-Plan-Change-Status-gt-Testing"></a>
<h2 >Approval of Plan = Change Status > Testing<a href="#Approval-of-Plan-Change-Status-gt-Testing" class="wiki-anchor">¶</a></h2>
Member Nodes - Story #8358 (In Progress): Discovery & Planning (CAFF)https://redmine.dataone.org/issues/83582018-02-12T16:25:06ZAmy Forresteraforres4@utk.edu
<p>Discovery is about establishing contact and building a relationship with a potential new member node. In this phase, it is determined if DataONE and the repository are a good fit for one another and if the repository generally meets the requirements of DataONE member nodes. Broad discussions of deployment options may be reviewed as well.<br>
This story is complete when a determination is made to either proceed with planning a new deployment, or that joining DataONE is not an option for the repository at this time.</p>
Member Nodes - MNDeployment #8259 (New): Neotoma Paleoecology Databasehttps://redmine.dataone.org/issues/82592018-01-30T18:19:02ZAmy Forresteraforres4@utk.edu
<p>Neotoma is a multiproxy paleoecological database that covers the Pliocene-Quaternary, including modern microfossil samples. The database is an international collaborative effort among individuals from 19 institutions, representing multiple constituent databases. There are over 20 data-types within the Neotoma Paleoecological Database, including pollen microfossils, plant macrofossils, vertebrate fauna, diatoms, charcoal, biomarkers, ostracodes, physical sedimentology and water chemistry. Neotoma provides an underlying cyberinfrastructure that enables the development of common software tools for data ingest, discovery, display, analysis, and distribution, while giving domain scientists control over critical taxonomic and other data quality issues.</p>
Member Nodes - MNDeployment #8254 (Planning): ABDS - Arctic Biodiversity Data Service (CAFF)https://redmine.dataone.org/issues/82542018-01-26T19:23:54ZAmy Forresteraforres4@utk.edu
<p>Conservation of Arctic Flora and Fauna (CAFF - <a href="http://www.caff.is" class="external">www.caff.is</a>) is the biodiversity working group of the <a href="https://www.arctic-council.org/en/about-us" class="external">Arctic Council</a>. CAFF has a focus on data management and its Arctic Biodiversity Data Service (ABDS - <a href="http://www.abds.is" class="external">www.abds.is</a>) serves as the Arctic node in GBIF, OBIS, is the ARctic Biodiversity Observation Network in GEOBON etc </p>
Member Nodes - Story #8244 (New): Upgrade Member Node to current version of Metacat (IOE)https://redmine.dataone.org/issues/82442018-01-22T16:38:20ZDave Vieglaisdave.vieglais@gmail.com
<p>The MN operations have been placed in the care of Todd Kipfer. He has requested some assistance with use of Metacat, and especially bringing it to the latest version.</p>
Member Nodes - Task #7986 (New): GINA: Configure SSL Certificates for Productionhttps://redmine.dataone.org/issues/79862017-01-27T18:08:38ZLaura Moyerslmoyers1@utk.edu
<p>DataONE creates client certificate, MN installs client certificate, DataONE verifies successful installation of client certificate; MN obtains/installs server certificate (req'd for Tiers 2-4, optional for Tier 1 if MN wishes to use HTTPS), DataONE verifies successful installation of server certificate.</p>
Member Nodes - Task #7979 (New): GINA: Configure SSL Certificates for Testing Environmenthttps://redmine.dataone.org/issues/79792017-01-27T18:08:29ZLaura Moyerslmoyers1@utk.edu
<p>DataONE creates client certificate, MN installs client certificate, DataONE verifies successful installation of client certificate; MN obtains/installs server certificate (req'd for Tiers 2-4, optional for Tier 1 if MN wishes to use HTTPS), DataONE verifies successful installation of server certificate.</p>
Member Nodes - MNDeployment #7973 (New): Alaska Energy Data Gatewayhttps://redmine.dataone.org/issues/79732017-01-27T15:19:28ZLaura Moyerslmoyers1@utk.edu
<p>At a meeting 26 January 2017, it was mentioned that GINA is working with the Alaska Energy Data Gateway on a proposal where there is a component for implementing a DataONE Member Node for AEDG. This is still very early in the proposal stage, but the possibility exists for an AEDG MN in future.</p>
Member Nodes - Task #5899 (New): GBIF: Create news itemhttps://redmine.dataone.org/issues/58992014-07-17T21:07:35ZRoger Dahldahl@unm.edu
<p>Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective</p>
Infrastructure - Task #3768 (New): Add canonical DataONE description paper to citing DataONE web-...https://redmine.dataone.org/issues/37682013-05-16T22:20:56ZJohn Cobbjohnw.cobb+dataoneRM@gmail.com
<p>The page <a href="http://www.dataone.org/citing-dataone">http://www.dataone.org/citing-dataone</a> includes guidance for citations. There are two missing needs on this page (or perhaps they should be another page. </p>
<p>One: A citation need is to answer members of the DataONE community who want to acknowledge DataONE as a project and cyberinfrastructure. DataONE needs to provide a canonical preferred citation. I think this may be <a href="http://dx.doi.org/10.1016/j.ecoinf.2011.08.007">http://dx.doi.org/10.1016/j.ecoinf.2011.08.007</a>, ( can be found at <a href="http://www.sciencedirect.com/science/article/pii/S1574954111000768">http://www.sciencedirect.com/science/article/pii/S1574954111000768</a>)</p>
<p>Two: DataONE needs an acknowledgement block. Perhaps this exists but I am just not aware, What I am thinking of is something similar to<br>
<a href="https://www.olcf.ornl.gov/media-center/media-kit/">https://www.olcf.ornl.gov/media-center/media-kit/</a><br>
<a href="https://www.xsede.org/how-to-acknowledge-xsede">https://www.xsede.org/how-to-acknowledge-xsede</a></p>