https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2013-01-30T20:28:54ZDataONE TasksMember Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=151392013-01-30T20:28:54ZMatthew Jonesjones@nceas.ucsb.edu
<ul><li><strong>Due date</strong> set to <i>2014-01-31</i></li><li><strong>Target version</strong> set to <i>Deploy by end of Y5Q2</i></li><li><strong>translation missing: en.field_remaining_hours</strong> set to <i>0.0</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=163042013-06-18T19:49:39ZMatthew Jonesjones@nceas.ucsb.edu
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>I got the following reply from D. Blankman, and I responded describing the process of becoming a MN, giving a link to the checklist, and asking for a contact for LTER_Europe.</p>
<p>D. Blankman wrote:</p>
<p>Matt,</p>
<p>Sorry I haven't gotten back to you. LTER-Europe would definitely be interested in becoming part of DataOne. There is also an Asia-Pacific metacat that TERN/Taiwan is managing that should be a DataOne node as well.</p>
<p>Let me know what we need to do.</p>
<p>David<br>
David Blankman<br>
Chair, ILTER Information Management Committee<br>
Director, Information Management, Israel LTER</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=163052013-06-18T19:50:19ZMatthew Jonesjones@nceas.ucsb.edu
<ul><li><strong>Subject</strong> changed from <i>Deploy ILTER - Europe member node</i> to <i>ILTER - Europe</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=165012013-07-17T14:51:49ZMatthew Jonesjones@nceas.ucsb.edu
<ul></ul><p>Hi David,</p>
<p>Thanks for the update on the Israel node. I will remove it from our tracking system. Other answers to your questions are inline below...</p>
<blockquote>
<p>On Wed, Jul 17, 2013 at 6:10 AM, David Blankman <a href="mailto:dblankman1@gmail.com">dblankman1@gmail.com</a> wrote:<br>
Matt,</p>
<p>First, the Israel metacat is no longer in existence. </p>
<p>We will be discussing DataOne at the ILTER meeting in Korea in October and will come to a decision as to how we are going to work, e.g. will Japan, Malaysia, Australia (all have metacats) join independently or will <br>
they replicate to a regional metacat hosted in Taiwan. Is there an advantage of one strategy versus another?</p>
</blockquote>
<p>Yes, there are pros and cons of each. Advantages of running multiple nodes include 1) ability to share costs for storage, 2) ability to replicate data at multiple local nodes, and 3) keeping data closer to the users of the node, which can be important on some networks. Disadvantages include 1) multiple systems have to be created and maintained.</p>
<blockquote>
<p>Am I correct that LTER-Europe can start out as just a member node and then later on replicate?</p>
</blockquote>
<p>Yes. You can start by just providing metadata and exposing your data for download, and then later turn on replication services. Metacat has a switch in the configuration that allows you to do this.</p>
<blockquote>
<p>Is DataOne at the point where we can replicate only LTER networks?</p>
</blockquote>
<p>Yes, DataONE is, but there are issues. Each MN can determine which data sets they accept for replication. The process is that the Source MN flags a data set for replication, then the CN looks for a Target MN that can host the dataset, and then asks the Target MN to replicate the data, which the Target MN can either accept or decline. However, Metacat doesn't currently provide a mechanism for this -- it accepts all replication requests if it has space available. So you would have to make modifications to support this kind of a filter. We want to add more features for selecting which data to replicate and how much space to make available, but we haven't had the resources to implement this yet.</p>
<blockquote>
<p>Also am I correct that we can replicate metadata only and be selective about the data we would be willing to replicate?</p>
</blockquote>
<p>Yes, replication policies (as well as access policies) are done on a per-object basis, and can be separately specified for metadata and data objects; That said, all metadata gets replicated to all of the Coordinating Nodes, even though it may be access restricted. </p>
<blockquote>
<p>For now, I will be the technical contact for the LTER-Europe DataOne node. We now have the metacat working along with Harvesting, so we are ready to start participating in DataOne. The other key person from <br>
the system administration perspective is Mike Wilson (<a href="mailto:mw@ceh.ac.uk">mw@ceh.ac.uk</a>). He is probably the best person to contact about coordinating certificates and similar system administration issues. </p>
</blockquote>
<p>Great, thanks. I will pass Mike's name on to our development team and we'll follow up.</p>
<p>Matt</p>
<blockquote>
<p>David</p>
<p>David Blankman<br>
Chair, ILTER Information Management Committee<br>
Director, Information Management, Israel LTER</p>
</blockquote>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=170762013-08-23T12:56:50ZBruce Wilsonbwilso27@utk.edu
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Planning</i></li></ul><p>Reclassifying to Planning as status to match current state per the MN Deployment checklist.</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=171032013-08-23T16:47:05ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Assignee</strong> changed from <i>Matthew Jones</i> to <i>Ben Leinfelder</i></li></ul><p>Sent to David and Mike Wilson, 8/23/2013<br>
<br>
Hi David,<br>
I wanted to keep the ball rolling with ILTER-Europe joining DataONE.<br>
Since you are already running a Metacat server, it should be quite easy for you to contribute to DataONE as a Member Node.<br>
You can start at the "Deploy" stage as outlined in our checklist: <a href="http://mule1.dataone.org/OperationDocs/member_node_deployment/mn_checklist.html">http://mule1.dataone.org/OperationDocs/member_node_deployment/mn_checklist.html</a><br>
And it would be a good idea to ensure your Metacat deployment has been configured as described in the Metacat DataONE documentation section: <a href="http://knb.ecoinformatics.org/knb/docs/dataone.html">http://knb.ecoinformatics.org/knb/docs/dataone.html</a></p>
<p>While it is not explicitly required, we prefer that our Member Nodes use SSL and procure a server certificate from a trusted commercial Certificate Authority. If you would like to enable SSL communication but cannot buy or otherwise obtain an SSL certificate for your server, DataONE can issue a server certificate for your use. But this is not preferred since it will not be trusted by any other systems that do not explicitly trust the DataONE CA.</p>
<p>Let me know how the configuration comes along and we can go from there.</p>
<p>Thanks!<br>
-ben</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=172472013-09-24T17:16:44ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Status</strong> changed from <i>Planning</i> to <i>Ready</i></li></ul><p>They have configured SSL for the ILTER-Europe node.<br>
<a href="https://data.lter-europe.net/knb/d1/mn/v1/node">https://data.lter-europe.net/knb/d1/mn/v1/node</a></p>
<hr>
<p>Now that we have a certificate for the Metacat. What else is needed to get the LTER-Europe registered as a MemberNode?<br>
David</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=172872013-10-01T17:40:42ZBruce Wilsonbwilso27@utk.edu
<ul><li><strong>MN Tier</strong> set to <i>Tier 1</i></li><li><strong>Software stack</strong> set to <i>Metacat</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=172892013-10-01T17:45:22ZBruce Wilsonbwilso27@utk.edu
<ul><li><strong>NodeIdentifier</strong> set to <i>urn:node:ILTER-EUROPE</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=172982013-10-01T18:04:19ZBruce Wilsonbwilso27@utk.edu
<ul><li><strong>Base URL</strong> set to <i>http://www.lter-europe.net/</i></li><li><strong>Subject</strong> changed from <i>ILTER - Europe</i> to <i>LTER - Europe</i></li><li><strong>NodeIdentifier</strong> changed from <i>urn:node:ILTER-EUROPE</i> to <i>urn:node:LTER-EUROPE</i></li></ul><p>Updating name to LTER-Europe to match what's on their web site</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=173042013-10-01T18:47:47ZChris Jonescjones@nceas.ucsb.edu
<ul><li><strong>Latitude</strong> set to <i>51.50</i></li><li><strong>Longitude</strong> set to <i>-0.13</i></li></ul><p>Added coordinates to their server in London, although the location may be VLAN-based, so we'd have to verify this.</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=173292013-10-02T16:29:49ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/diff/17329?detail_id=24004">diff</a>)</li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=183222014-01-17T15:39:58ZBruce Wilsonbwilso27@utk.edu
<ul><li><strong>Target version</strong> changed from <i>Deploy by end of Y5Q2</i> to <i>Deploy by end of Y5Q3</i></li><li><strong>Due date</strong> changed from <i>2014-01-31</i> to <i>2014-04-30</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=183912014-01-29T17:51:59ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>NodeIdentifier</strong> changed from <i>urn:node:LTER-EUROPE</i> to <i>urn:node:LTER_EUROPE</i></li><li><strong>Subject</strong> changed from <i>LTER - Europe</i> to <i>LTER_EUROPE</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=183922014-01-29T17:54:17ZBen Leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/diff/18392?detail_id=25481">diff</a>)</li><li><strong>Status</strong> changed from <i>Ready</i> to <i>Testing</i></li></ul><p>This node is registered in production and we are simply waiting on CN stability and administrative approval.</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=195012014-05-01T15:50:25ZLaura Moyerslmoyers1@utk.edu
<ul><li><strong>Target version</strong> changed from <i>Deploy by end of Y5Q3</i> to <i>Deploy by end of Y5Q4</i></li><li><strong>Due date</strong> changed from <i>2014-04-30</i> to <i>2014-07-31</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=196702014-05-23T19:01:40ZBruce Wilsonbwilso27@utk.edu
<ul><li><strong>Status</strong> changed from <i>Testing</i> to <i>In Review</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=197772014-06-20T17:59:08ZLaura Moyerslmoyers1@utk.edu
<ul><li><strong>Target version</strong> changed from <i>Deploy by end of Y5Q4</i> to <i>Operational</i></li><li><strong>MN_Date_Online</strong> set to <i>2014-06-18</i></li><li><strong>Status</strong> changed from <i>In Review</i> to <i>Operational</i></li><li><strong>MN Description</strong> set to <i> LTER-Europe (the Long-Term Ecosystem Research network) helps to coordinate ILTER activities in Europe and represents European-level interests in ILTER. Over 450 sites holding extremely varied data are part of this network of 21 National LTER-Networks.</i></li><li><strong>Subject</strong> changed from <i>LTER_EUROPE</i> to <i>LTER-EUROPE</i></li><li><strong>Due date</strong> changed from <i>2014-07-31</i> to <i>2013-09-24</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=203592014-07-31T14:56:11ZLaura Moyerslmoyers1@utk.edu
<ul></ul><p>Formally announced 6/18/14.</p>
Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=249312015-04-16T00:12:57ZLaura Moyerslmoyers1@utk.edu
<ul><li><strong>Assignee</strong> changed from <i>Ben Leinfelder</i> to <i>Laura Moyers</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=294762018-01-10T01:14:07ZDave Vieglaisdave.vieglais@gmail.com
<ul><li><strong>Sprint</strong> set to <i>Ongoing Operational</i></li></ul> Member Nodes - MNDeployment #3232: LTER-EUROPEhttps://redmine.dataone.org/issues/3232?journal_id=308072018-09-04T14:37:53ZAmy Forresteraforres4@utk.edu
<ul></ul><p><strong>9/4/18:</strong> from Christoph Wohner, Ecosystem Research & Environmental Information Management <a href="mailto:Christoph.Wohner@umweltbundesamt.at">Christoph.Wohner@umweltbundesamt.at</a> <strong>re: LTER-europe status (-1)</strong> as of 8/20/18</p>
<blockquote>
<p>DEIMS is currently migrated to a new server and is undergoing some changes in terms of the software stack in use.</p>
<p>For the time being we turned off Metacat as we have deployed a new service that incorporates more and nodes and systems that DEIMS had.<br>
However, we are currently still setting up a few things and are in touch with <strong>Wim Hugo</strong> <a href="mailto:wim@saeon.ac.za">wim@saeon.ac.za</a>, who is responsible for the new data strategy of ILTER.<br>
Therefore it might take a couple of weeks until it can be harvested again.</p>
</blockquote>