<%@ page language="java" %> <%@ page import="java.util.Set,java.util.Map,java.util.Vector,edu.ucsb.nceas.utilities.PropertiesMetaData" %> <%@ page import="edu.ucsb.nceas.utilities.MetaDataGroup,edu.ucsb.nceas.utilities.MetaDataProperty" %> <% /** * '$RCSfile$' * Copyright: 2008 Regents of the University of California and the * National Center for Ecological Analysis and Synthesis * For Details: http://www.nceas.ucsb.edu/ * * '$Author: tao $' * '$Date: 2014-04-29 23:47:09 +0000 (Tue, 29 Apr 2014) $' * '$Revision: 8755 $' * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */ %> DataONE Configuration <%@ include file="./head-section.jsp"%> <%@ include file="./header-section.jsp"%>

DataONE Configuration

DataONE configuration is optional; choose 'Skip' below to proceed to the next configuration section, unless you want to join the DataONE federation.

DataONE is a federation of data repositories (called Member Nodes) that work together to create a seamless, interoperable network to store, preserve, discover, and publish scientific data. Becoming a DataONE Member Node is a means of distributing data and metadata using a common set of standards, making it easy to build software systems that can interact with any of the federated repository nodes. Metacat can be used to join the DataONE federation by configuring Metacat to act as a Member Node and applying with DataONE to become a Member Node. Once a node's application is approved and Metacat is configured, metadata will be synchronized in the network for easy discovery, and replicas of data and metadata can be housed on other Member Nodes for archival safe-keeping. In addition, a Metacat Member Node can optionally provide space to store replicas of data from other Member Nodes that wish to preserve their data in the federation.

To configure Metacat as a Member Node, you must first obtain a Member Node X.509 certificate that will be used to authenticate this node, and you must have a registered and verified account with DataONE that can be used as the point of contact for the candidate Member Node. Once you have this information, fill out the form below with the proper configuration information, and then click 'Register', which will send the registration data to DataONE. A unique Member Node ID will be assigned and should only be used for this node and never shared or altered.


<%@ include file="page-message-section.jsp"%>

Member Node Services

Enable or disable DataONE Member Node Services for this deployment
<% boolean enableServices = false; String enableServicesString = (String) request.getAttribute("dataone.mn.services.enabled"); if (enableServicesString != null) { enableServices = Boolean.parseBoolean(enableServicesString); } if (enableServices) { %> <% } else {%> <% } %>

Member Node Configuration

General information identifiying this node, its owner, and contents. You will need a certificate to identify the node, and a DataONE account to act as a node contact.
"/>
"/>
"/>
"/>
"/>
"/>
"/>
<% boolean synchronize = false; String nodeSynchronize = (String) request.getAttribute("dataone.nodeSynchronize"); if (nodeSynchronize != null) { synchronize = Boolean.parseBoolean(nodeSynchronize); } if (synchronize) { %> <% } else {%> <% } %>

 

Synchronization Schedule

The schedule on which metadata should be synchronized with DataONE, expressed as a crontab entry.
"/>
"/>
"/>
"/>
"/>
"/>
"/>

Replication

Configuration for replication, including whether this node can be used to house replicas of objects from other nodes, as well as default replication policies for the objects originating on this Member Node.
<% boolean replicate = false; String nodeReplicate = (String) request.getAttribute("dataone.nodeReplicate"); if (nodeReplicate != null) { replicate = Boolean.parseBoolean(nodeReplicate); } if (replicate) { %> <% } else {%> <% } %>
"/>
"/>
"/>
<% // do we know if it is an update or a new registration? boolean isUpdate = false; String isUpdateString = (String) request.getAttribute("dataone.isUpdate"); if (isUpdateString != null) { isUpdate = Boolean.parseBoolean(isUpdateString); } // do we know if it is pending approval? boolean isSubmitted = false; String isSubmittedString = (String) request.getAttribute("dataone.mn.registration.submitted"); if (isSubmittedString != null) { isSubmitted = Boolean.parseBoolean(isSubmittedString); } %> <%if (isUpdate) { %> <%} else if (isSubmitted) { %> <%} else { %> <%} %> <% // if have we already configured this section, then we cannot skip it boolean previouslyConfigured = false; String previouslyConfiguredString = (String) request.getAttribute("configutil.dataoneConfigured"); if (previouslyConfiguredString != null) { previouslyConfigured = Boolean.parseBoolean(previouslyConfiguredString); } %> <%if (!previouslyConfigured) { %> <%} %>
<%@ include file="./footer-section.jsp"%>