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 #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 - MNDeployment #8544 (Operational): Chinese Ecosystem Research Networkhttps://redmine.dataone.org/issues/85442018-04-16T21:04:04ZAmy Forresteraforres4@utk.edu
<p>{Chinese Ecosystem Research Network} Chinese Academy of Sciences Institute of Geographic sciences and Natural resources research -- <a href="http://english.igsnrr.cas.cn/">http://english.igsnrr.cas.cn/</a></p>
<p><a href="https://drive.google.com/open?id=1yF7vEWyG5xYGLmOT8Hf3uJCGH3ar9-wQcLIMSHaHfCg" class="external"><strong>MN Description Doc</strong></a></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 - Task #8522 (In Progress): CAFF: MN Communicationshttps://redmine.dataone.org/issues/85222018-03-26T15:07:59ZAmy Forresteraforres4@utk.edu
<ul>
<li> MN logo to GitHub (<a href="https://github.com/DataONEorg/member-node-info/tree/master/production/graphics">https://github.com/DataONEorg/member-node-info/tree/master/production/graphics</a>) </li>
<li>Completed MN Description document to Google Drive (<a href="https://drive.google.com/open?id=0B18azCDdsZfyUlI1WTBMMUlCckk">https://drive.google.com/open?id=0B18azCDdsZfyUlI1WTBMMUlCckk</a>)</li>
<li>Send MN communication channels to MN (<a href="https://redmine.dataone.org/projects/mns/wiki/MN_communication_channels">https://redmine.dataone.org/projects/mns/wiki/MN_communication_channels</a>)</li>
<li>Business requirements confirmed:
<ul>
<li>legal?</li>
<li>licensing?</li>
<li>data sharing restrictions / privacy concerns?</li>
</ul></li>
</ul>
Member Nodes - Task #8378 (In Progress): (OTS) replicate datahttps://redmine.dataone.org/issues/83782018-02-26T21:58:34ZAmy Forresteraforres4@utk.edu
<p>Encourage OTS to replicate data</p>
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 #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 - MNDeployment #6957 (Operational): NRDC - Nevada Research Data Centerhttps://redmine.dataone.org/issues/69572015-03-25T19:43:32ZLaura Moyerslmoyers1@utk.edu
<p>The NCCP, based at the University of Nevada, Reno, is a part of the Nevada EPSCoR project. They currently have about a dozen sensor sites collecting climate data, with the intent to add 1-2 sites each year for the next 2-3 years.</p>
<p>At present, the goal is to stand up a Tier 1 GMN exposing monthly aggregated data (immutable).</p>
<p>See <a href="http://sensor.nevada.edu">http://sensor.nevada.edu</a></p>
<p>Technical POCs are Richard Kelley and Moinul Hossain.</p>
<p>Initial meeting notes: <a href="https://epad.dataone.org/pad/p/NCCP_and_DataONE">https://epad.dataone.org/pad/p/NCCP_and_DataONE</a></p>
Member Nodes - MNDeployment #4700 (Operational): IARC (International Arctic Research Center) Data...https://redmine.dataone.org/issues/47002014-04-08T17:33:16ZLaura Moyerslmoyers1@utk.edu
<p>IARC (International Arctic Research Center) Data Archive at University of Alaska Fairbanks is interesting in becoming a MN.</p>
<p>IARC Data Archive (IDA) GeoNetwork Portal's purpose is:<br>
To improve access to and integrated use of Arctic climate-change data and information<br>
To provide long term archival storage of Arctic climate-change data and information<br>
To support decision making</p>
<p>via contact us 4/4/14:<br>
POC: Jim Long, <a href="mailto:jlong@iarc.uaf.edu">jlong@iarc.uaf.edu</a> or <a href="mailto:jlong14@alaska.edu">jlong14@alaska.edu</a></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>
Member Nodes - MNDeployment #3687 (Operational): Montana State University Institute on Ecosystemshttps://redmine.dataone.org/issues/36872013-03-22T17:00:41ZLaura Moyerslmoyers1@utk.edu
<p>From DataONE website "contact us" – How to Become a MN (Benefits? Allow me to do x?)</p>
<p>Website: <a href="http://www.montana.edu/">http://www.montana.edu/</a><br>
Entity: Montana State University<br>
POC: <a href="mailto:seth.kurtmason@msu.montana.edu">seth.kurtmason@msu.montana.edu</a><br>
Date of inquiry: 4/24/12<br>
Responder:<br><br>
Date of response:<br><br>
Response: </p>
Member Nodes - MNDeployment #3559 (Operational): ONESharehttps://redmine.dataone.org/issues/35592013-02-07T03:59:06ZDave Vieglaisdave.vieglais@gmail.comMember Nodes - MNDeployment #3201 (Operational): Taiwan Forestry Research Institutehttps://redmine.dataone.org/issues/32012012-09-05T02:43:08ZDave Vieglaisdave.vieglais@gmail.com
<p>This issue is to track the deployment or otherwise of the TFRI (Taiwan Forestry Research Institute) potential MN.</p>