setting up dataone

Owned by Former user (Deleted)
Last updated: Jul 21, 2016

 

Certificates

The 'abrin' username has access to this directory (shared drive). You will need an ecoinformatics.org identity to access this file. If you do not have an ecoinformatics.org account or if you have an account but do not remember your password, you may register or reset your password at the following URL (if creating this account, select "NCEAS/DataONE/Kepler" as the organization name):
Please be careful to protect the key file (via permissions settings), since anyone with it can act on behalf of the urn:node:TDAR Member Node within the DataONE network. Also, please do not share the certificate files over insecure protocols like email.
We cannot guarantee that we can keep a copy of your certificate, so please make an encrypted copy of it on a thumb drive or somewhere else that is safe.
To install these certificates, you will need to configure your web server software with the file location of the certificates, in the same way that you would do so for a server-side certificate from a commercial SSL Certificate Authority like Verisign or Thawte, etc. We do not have specific instructions for this procedure because it differs for all web server software packages. However, we can point you to examples of Member Node software applications that do this using Apache, and that should help you understand the configuration directives even if you are not using the Apache web server. Here is the links to a Java-based system and a Python-based system:
Metacat documentation on SSL setup:

on core, these changes are made to the catalina.properties for /tdar-tomcat/

GMN documentation on SSL setup:
Let us know if you have any trouble downloading the certificate zip file or other questions.



Registering user:
Before registering you MN, you will need to first register your contact subject identity in the DataONE production environment: https://cn.dataone.org/portal/. Once registered, please let us know and I will verify your identity in the CN LDAP. After this step, you may attempt to register your MN in the production environment.

to Add:
curl -i -E private/urn_node_TDAR.pem --header "Content-Type: multipart/form-data" --form "node=@./tdar.xml" -k -X POST "https://cn.dataone.org/cn/v1/node/"

to Update:
 
curl -i -E private/urn_node_TDAR.pem --header "Content-Type: multipart/form-data" --form "node=@./tdar.xml" -k -X PUT "https://cn.dataone.org/cn/v1/node/urn:node:TDAR"
 

 

DataOne config.xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/cn/xslt/dataone.types.v1.xsl"?>
<d1:node xmlns:d1="http://ns.dataone.org/service/types/v1" replicate="false" synchronize="true" type="mn" state="up">
    <identifier>urn:node:TDAR</identifier>
    <name>TDAR</name>
    <description>The Digital Archaeological Record (tDAR) is an international digital repository for the digital records of archaeological investigations. tDAR's use, development, and maintenance are governed by Digital Antiquity, an organization dedicated to ensuring the long-term preservation of irreplaceable archaeological data and to broadening the access to these data.</description>
    <baseURL>http://dataone.tdar.org/dataone</baseURL>
    <services>
        <service name="MNRead" version="v1" available="true"/>
        <service name="MNCore" version="v1" available="true"/>
        <service name="MNAuthorization" version="v1" available="false"/>
        <service name="MNStorage" version="v1" available="false"/>
        <service name="MNReplication" version="v1" available="false"/>
    </services>
    <synchronization>
        <schedule hour="20" mday="*" min="*" mon="*" sec="0" wday="?" year="*"/>
    </synchronization>
    <nodeReplicationPolicy>
        <spaceAllocated>1024</spaceAllocated>
    </nodeReplicationPolicy>
    <subject>CN=urn:node:TDAR,DC=dataone,DC=org</subject>
    <contactSubject>CN=Adam Brin A29701,O=Arizona State University,C=US,DC=cilogon,DC=org</contactSubject>
</d1:node>