Äcdocutils.nodes
document
q)Åq}q(U	nametypesq}q(X���cyberinfrastructure visionqàX���nbii metadata clearing houseqàX	���ornl daacqàX���dataone overviewq	NX���dataoneq
àX"���knowledge network for biodiversityqàX;���partnership for interdisciplinary studies of coastal oceansqàX���dryadq
àX���datanet programqàuUsubstitution_defsq}qUparse_messagesq]qUcurrent_sourceqNU
decorationqNUautofootnote_startqKUnameidsq}q(hUcyberinfrastructure-visionqhUnbii-metadata-clearing-houseqhU	ornl-daacqh	Udataone-overviewqh
UdataoneqhU"knowledge-network-for-biodiversityqhU;partnership-for-interdisciplinary-studies-of-coastal-oceansqh
UdryadqhUdatanet-programq uUchildrenq!]q"cdocutils.nodes
section
q#)Åq$}q%(U	rawsourceq&U�Uparentq'hUsourceq(X]���/var/lib/jenkins/jobs/API_Documentation_trunk/workspace/api-documentation/source/overview.txtq)Utagnameq*Usectionq+U
attributesq,}q-(Udupnamesq.]Uclassesq/]Ubackrefsq0]Uidsq1]q2haUnamesq3]q4h	auUlineq5KUdocumentq6hh!]q7(cdocutils.nodes
title
q8)Åq9}q:(h&X���DataONE Overviewq;h'h$h(h)h*Utitleq<h,}q=(h.]h/]h0]h1]h3]uh5Kh6hh!]q>cdocutils.nodes
Text
q?X���DataONE Overviewq@ÖÅqA}qB(h&h;h'h9ubaubcdocutils.nodes
paragraph
qC)ÅqD}qE(h&Xú��The major goal of NSFs `DataNet program`_ is to catalyze development of a
system addressing the vision outlined in Chapter 3 (Data, Data Analysis, and
Visualization) of NSF‚Äôs `Cyberinfrastructure Vision`_ for 21st Century
Discovery in which ‚Äúscience and engineering digital data are routinely
deposited in well-documented form, are regularly and easily consulted and
analyzed by specialists and non-specialists alike, are openly accessible while
suitably protected, and are reliably preserved.‚Äù The DataNet project DataONE_
(Data Observation Network for Earth) is a federated data network built to
improve access to Earth science data, and to support science by:h'h$h(h)h*U	paragraphqFh,}qG(h.]h/]h0]h1]h3]uh5Kh6hh!]qH(h?X���The major goal of NSFs qIÖÅqJ}qK(h&X���The major goal of NSFs h'hDubcdocutils.nodes
reference
qL)ÅqM}qN(h&X���`DataNet program`_UresolvedqOKh'hDh*U	referenceqPh,}qQ(UnameX���DataNet programUrefuriqRX2���http://www.nsf.gov/pubs/2007/nsf07601/nsf07601.htmqSh1]h0]h.]h/]h3]uh!]qTh?X���DataNet programqUÖÅqV}qW(h&U�h'hMubaubh?Xà��� is to catalyze development of a
system addressing the vision outlined in Chapter 3 (Data, Data Analysis, and
Visualization) of NSF‚Äôs qXÖÅqY}qZ(h&Xà��� is to catalyze development of a
system addressing the vision outlined in Chapter 3 (Data, Data Analysis, and
Visualization) of NSF‚Äôs h'hDubhL)Åq[}q\(h&X���`Cyberinfrastructure Vision`_hOKh'hDh*hPh,}q](UnameX���Cyberinfrastructure VisionhRX.���http://www.nsf.gov/pubs/2007/nsf0728/index.jspq^h1]h0]h.]h/]h3]uh!]q_h?X���Cyberinfrastructure Visionq`ÖÅqa}qb(h&U�h'h[ubaubh?X;�� for 21st Century
Discovery in which ‚Äúscience and engineering digital data are routinely
deposited in well-documented form, are regularly and easily consulted and
analyzed by specialists and non-specialists alike, are openly accessible while
suitably protected, and are reliably preserved.‚Äù The DataNet project qcÖÅqd}qe(h&X;�� for 21st Century
Discovery in which ‚Äúscience and engineering digital data are routinely
deposited in well-documented form, are regularly and easily consulted and
analyzed by specialists and non-specialists alike, are openly accessible while
suitably protected, and are reliably preserved.‚Äù The DataNet project h'hDubhL)Åqf}qg(h&X���DataONE_hOKh'hDh*hPh,}qh(UnameX���DataONEhRX���http://dataone.org/qih1]h0]h.]h/]h3]uh!]qjh?X���DataONEqkÖÅql}qm(h&U�h'hfubaubh?Xã���
(Data Observation Network for Earth) is a federated data network built to
improve access to Earth science data, and to support science by:qnÖÅqo}qp(h&Xã���
(Data Observation Network for Earth) is a federated data network built to
improve access to Earth science data, and to support science by:h'hDubeubcdocutils.nodes
block_quote
qq)Åqr}qs(h&U�h'h$h(Nh*Ublock_quoteqth,}qu(h.]h/]h0]h1]h3]uh5Nh6hh!]qvcdocutils.nodes
enumerated_list
qw)Åqx}qy(h&U�h,}qz(Usuffixq{U.h1]h0]h.]Uprefixq|U�h/]h3]Uenumtypeq}Uarabicq~uh'hrh!]q(cdocutils.nodes
list_item
qÄ)ÅqÅ}qÇ(h&X=���engaging the relevant science, data, and policy communities;
h,}qÉ(h.]h/]h0]h1]h3]uh'hxh!]qÑhC)ÅqÖ}qÜ(h&X<���engaging the relevant science, data, and policy communities;qáh'hÅh(h)h*hFh,}qà(h.]h/]h0]h1]h3]uh5Kh!]qâh?X<���engaging the relevant science, data, and policy communities;qäÖÅqã}qå(h&háh'hÖubaubah*U	list_itemqçubhÄ)Åqé}qè(h&X;���facilitating easy, secure, and persistent storage of data;
h,}qê(h.]h/]h0]h1]h3]uh'hxh!]qëhC)Åqí}qì(h&X:���facilitating easy, secure, and persistent storage of data;qîh'héh(h)h*hFh,}qï(h.]h/]h0]h1]h3]uh5Kh!]qñh?X:���facilitating easy, secure, and persistent storage of data;qóÖÅqò}qô(h&hîh'híubaubah*hçubhÄ)Åqö}qõ(h&Xs���disseminating integrated and user-friendly tools for data discovery,
analysis, visualization, and decision-making.
h,}qú(h.]h/]h0]h1]h3]uh'hxh!]qùhC)Åqû}qü(h&Xr���disseminating integrated and user-friendly tools for data discovery,
analysis, visualization, and decision-making.q†h'höh(h)h*hFh,}q°(h.]h/]h0]h1]h3]uh5Kh!]q¢h?Xr���disseminating integrated and user-friendly tools for data discovery,
analysis, visualization, and decision-making.q£ÖÅq§}q•(h&h†h'hûubaubah*hçubeh*Uenumerated_listq¶ubaubcdocutils.nodes
image
qß)Åq®}q©(h&X,���.. image:: images/ReferenceArchitecture.png
h'h$h(h)h*Uimageq™h,}q´(UuriX ���images/ReferenceArchitecture.pngq¨h1]h0]h.]h/]U
candidatesq≠}qÆU*h¨sh3]uh5Kh6hh!]ubhC)ÅqØ}q∞(h&XL���*Figure 1.* An overview of the major components of the DataONE architecture.q±h'h$h(h)h*hFh,}q≤(h.]h/]h0]h1]h3]uh5Kh6hh!]q≥(cdocutils.nodes
emphasis
q¥)Åqµ}q∂(h&X���*Figure 1.*h,}q∑(h.]h/]h0]h1]h3]uh'hØh!]q∏h?X	���Figure 1.qπÖÅq∫}qª(h&U�h'hµubah*Uemphasisqºubh?XA��� An overview of the major components of the DataONE architecture.qΩÖÅqæ}qø(h&XA��� An overview of the major components of the DataONE architecture.h'hØubeubcdocutils.nodes
comment
q¿)Åq¡}q¬(h&X��.. image:: images/core_components.png

@startuml images/core_components.png
[lib_common]
package ITK {
  [lib_client]
}

[Member Node]

[Coordinating Node]

[lib_client] .. [lib_common]
[Member Node] .. [lib_common]
[Coordinating Node] .. [lib_common]
@endumlh'h$h(h)h*Ucommentq√h,}qƒ(U	xml:spaceq≈Upreserveq∆h1]h0]h.]h/]h3]uh5K-h6hh!]q«h?X��.. image:: images/core_components.png

@startuml images/core_components.png
[lib_common]
package ITK {
  [lib_client]
}

[Member Node]

[Coordinating Node]

[lib_client] .. [lib_common]
[Member Node] .. [lib_common]
[Coordinating Node] .. [lib_common]
@endumlq»ÖÅq…}q (h&U�h'h¡ubaubhC)ÅqÀ}qÃ(h&X'��There are three major components in the DataONE infrastructure: Member Nodes
which represent data repositories, Coordinating Nodes which serve data
management and discovery services, and the Investigator Toolkit which contains
a variety of end user tools for interacting with the infrastructure.qÕh'h$h(h)h*hFh,}qŒ(h.]h/]h0]h1]h3]uh5K.h6hh!]qœh?X'��There are three major components in the DataONE infrastructure: Member Nodes
which represent data repositories, Coordinating Nodes which serve data
management and discovery services, and the Investigator Toolkit which contains
a variety of end user tools for interacting with the infrastructure.q–ÖÅq—}q“(h&hÕh'hÀubaubhC)Åq”}q‘(h&XO��Participation in the DataONE infrastructure as a Member Node or by using the
Investigator Toolkit (i.e. implementing or utilizing DataONE service
interfaces) provides several fundamental services upon which additional
infrastructure, services, applications and communities may be built. These
core, community building services include:q’h'h$h(h)h*hFh,}q÷(h.]h/]h0]h1]h3]uh5K3h6hh!]q◊h?XO��Participation in the DataONE infrastructure as a Member Node or by using the
Investigator Toolkit (i.e. implementing or utilizing DataONE service
interfaces) provides several fundamental services upon which additional
infrastructure, services, applications and communities may be built. These
core, community building services include:qÿÖÅqŸ}q⁄(h&h’h'h”ubaubcdocutils.nodes
bullet_list
q€)Åq‹}q›(h&U�h'h$h(h)h*Ubullet_listqﬁh,}qﬂ(Ubulletq‡X���-h1]h0]h.]h/]h3]uh5K9h6hh!]q·(hÄ)Åq‚}q„(h&XR���promotion of data preservation through automated replication of data and
metadata
h'h‹h(h)h*hçh,}q‰(h.]h/]h0]h1]h3]uh5Nh6hh!]qÂhC)ÅqÊ}qÁ(h&XQ���promotion of data preservation through automated replication of data and
metadataqËh'h‚h(h)h*hFh,}qÈ(h.]h/]h0]h1]h3]uh5K9h!]qÍh?XQ���promotion of data preservation through automated replication of data and
metadataqÎÖÅqÏ}qÌ(h&hËh'hÊubaubaubhÄ)ÅqÓ}qÔ(h&X_���support for arbitrary globally unique identifiers with guaranteed resolution
and dereferencing
h'h‹h(h)h*hçh,}q(h.]h/]h0]h1]h3]uh5Nh6hh!]qÒhC)ÅqÚ}qÛ(h&X^���support for arbitrary globally unique identifiers with guaranteed resolution
and dereferencingqÙh'hÓh(h)h*hFh,}qı(h.]h/]h0]h1]h3]uh5K<h!]qˆh?X^���support for arbitrary globally unique identifiers with guaranteed resolution
and dereferencingq˜ÖÅq¯}q˘(h&hÙh'hÚubaubaubhÄ)Åq˙}q˚(h&X)���extensible search and discovery services
h'h‹h(h)h*hçh,}q¸(h.]h/]h0]h1]h3]uh5Nh6hh!]q˝hC)Åq˛}qˇ(h&X(���extensible search and discovery servicesr���h'h˙h(h)h*hFh,}r��(h.]h/]h0]h1]h3]uh5K?h!]r��h?X(���extensible search and discovery servicesr��ÖÅr��}r��(h&j���h'h˛ubaubaubhÄ)År��}r��(h&X;���federated management of user identities and access control
h'h‹h(h)h*hçh,}r��(h.]h/]h0]h1]h3]uh5Nh6hh!]r	��hC)År
��}r��(h&X:���federated management of user identities and access controlr��h'j��h(h)h*hFh,}r
��(h.]h/]h0]h1]h3]uh5KAh!]r��h?X:���federated management of user identities and access controlr��ÖÅr��}r��(h&j��h'j
��ubaubaubeubh¿)År��}r��(h&X���[[ Member Node APIs diagram ]]h'h$h(h)h*h√h,}r��(h≈h∆h1]h0]h.]h/]h3]uh5KEh6hh!]r��h?X���[[ Member Node APIs diagram ]]r��ÖÅr��}r��(h&U�h'j��ubaubhC)År��}r��(h&Xã��Member Nodes are primarily existing data repositories (e.g. the `Knowledge
Network for Biodiversity`_, `ORNL DAAC`_, `Partnership for Interdisciplinary
Studies of Coastal Oceans`_) that already fill an important role in their
respective communities supporting data management, curation, discovery and
access functions. There are two main technical aspects to Member Node
participation in DataONE - the service interfaces to be implemented (i.e. the
:doc:`Member Node APIs</apis/MN_APIs>`), and the content that is to be served.
At a fundamental level, all content in DataONE is treated as discrete,
immutable objects, each of which has a unique identifier. A Member Node would
be considered functionally complete if it were able to support the required
services interfaces for :term:`Tier 1` participation (i.e. public access, read
only content), and so enable the discovery of all objects available on the
Member Node (through :func:`MNRead.listObjects`), low level description of
each object (through :func:`MNRead.getSystemMetadata`), retrieval of the
object given it's identifier (:func:`MNRead.get`), and reporting of activity
(:func:`MNCore.getLogRecords`).h'h$h(h)h*hFh,}r��(h.]h/]h0]h1]h3]uh5KFh6hh!]r��(h?X@���Member Nodes are primarily existing data repositories (e.g. the r��ÖÅr��}r��(h&X@���Member Nodes are primarily existing data repositories (e.g. the h'j��ubhL)År ��}r!��(h&X%���`Knowledge
Network for Biodiversity`_hOKh'j��h*hPh,}r"��(UnameX"���Knowledge Network for BiodiversityhRX���http://knb.ecoinformatics.org/r#��h1]h0]h.]h/]h3]uh!]r$��h?X"���Knowledge
Network for Biodiversityr%��ÖÅr&��}r'��(h&U�h'j ��ubaubh?X���, r(��ÖÅr)��}r*��(h&X���, h'j��ubhL)År+��}r,��(h&X���`ORNL DAAC`_hOKh'j��h*hPh,}r-��(UnameX	���ORNL DAAChRX���http://daac.ornl.gov/r.��h1]h0]h.]h/]h3]uh!]r/��h?X	���ORNL DAACr0��ÖÅr1��}r2��(h&U�h'j+��ubaubh?X���, r3��ÖÅr4��}r5��(h&X���, h'j��ubhL)År6��}r7��(h&X>���`Partnership for Interdisciplinary
Studies of Coastal Oceans`_hOKh'j��h*hPh,}r8��(UnameX;���Partnership for Interdisciplinary Studies of Coastal OceanshRX���http://www.piscoweb.org/r9��h1]h0]h.]h/]h3]uh!]r:��h?X;���Partnership for Interdisciplinary
Studies of Coastal Oceansr;��ÖÅr<��}r=��(h&U�h'j6��ubaubh?X��) that already fill an important role in their
respective communities supporting data management, curation, discovery and
access functions. There are two main technical aspects to Member Node
participation in DataONE - the service interfaces to be implemented (i.e. the
r>��ÖÅr?��}r@��(h&X��) that already fill an important role in their
respective communities supporting data management, curation, discovery and
access functions. There are two main technical aspects to Member Node
participation in DataONE - the service interfaces to be implemented (i.e. the
h'j��ubcsphinx.addnodes
pending_xref
rA��)ÅrB��}rC��(h&X&���:doc:`Member Node APIs</apis/MN_APIs>`rD��h'j��h(h)h*Upending_xrefrE��h,}rF��(UreftypeX���docrG��UrefwarnrH��àU	reftargetrI��X
���/apis/MN_APIsU	refdomainU�h1]h0]Urefexplicitàh.]h/]h3]UrefdocrJ��X���overviewrK��uh5KFh!]rL��cdocutils.nodes
inline
rM��)ÅrN��}rO��(h&jD��h,}rP��(h.]h/]rQ��(UxrefrR��jG��eh0]h1]h3]uh'jB��h!]rS��h?X���Member Node APIsrT��ÖÅrU��}rV��(h&U�h'jN��ubah*UinlinerW��ubaubh?X"��), and the content that is to be served.
At a fundamental level, all content in DataONE is treated as discrete,
immutable objects, each of which has a unique identifier. A Member Node would
be considered functionally complete if it were able to support the required
services interfaces for rX��ÖÅrY��}rZ��(h&X"��), and the content that is to be served.
At a fundamental level, all content in DataONE is treated as discrete,
immutable objects, each of which has a unique identifier. A Member Node would
be considered functionally complete if it were able to support the required
services interfaces for h'j��ubjA��)År[��}r\��(h&X���:term:`Tier 1`r]��h'j��h(h)h*jE��h,}r^��(UreftypeX���termjH��àjI��X���tier 1U	refdomainX���stdr_��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5KFh!]r`��jM��)Åra��}rb��(h&j]��h,}rc��(h.]h/]rd��(jR��j_��X���std-termre��eh0]h1]h3]uh'j[��h!]rf��h?X���Tier 1rg��ÖÅrh��}ri��(h&U�h'ja��ubah*jW��ubaubh?Xâ��� participation (i.e. public access, read
only content), and so enable the discovery of all objects available on the
Member Node (through rj��ÖÅrk��}rl��(h&Xâ��� participation (i.e. public access, read
only content), and so enable the discovery of all objects available on the
Member Node (through h'j��ubjA��)Årm��}rn��(h&X���:func:`MNRead.listObjects`ro��h'j��h(h)h*jE��h,}rp��(UreftypeX���funcjH��âjI��X���MNRead.listObjectsU	refdomainX���pyrq��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��Upy:classrr��NU	py:modulers��Nuh5KFh!]rt��cdocutils.nodes
literal
ru��)Årv��}rw��(h&jo��h,}rx��(h.]h/]ry��(jR��jq��X���py-funcrz��eh0]h1]h3]uh'jm��h!]r{��h?X���MNRead.listObjects()r|��ÖÅr}��}r~��(h&U�h'jv��ubah*Uliteralr��ubaubh?X1���), low level description of
each object (through rÄ��ÖÅrÅ��}rÇ��(h&X1���), low level description of
each object (through h'j��ubjA��)ÅrÉ��}rÑ��(h&X ���:func:`MNRead.getSystemMetadata`rÖ��h'j��h(h)h*jE��h,}rÜ��(UreftypeX���funcjH��âjI��X���MNRead.getSystemMetadataU	refdomainX���pyrá��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��jr��Njs��Nuh5KFh!]rà��ju��)Årâ��}rä��(h&jÖ��h,}rã��(h.]h/]rå��(jR��já��X���py-funcrç��eh0]h1]h3]uh'jÉ��h!]ré��h?X���MNRead.getSystemMetadata()rè��ÖÅrê��}rë��(h&U�h'jâ��ubah*j��ubaubh?X2���), retrieval of the
object given it's identifier (rí��ÖÅrì��}rî��(h&X2���), retrieval of the
object given it's identifier (h'j��ubjA��)Årï��}rñ��(h&X���:func:`MNRead.get`ró��h'j��h(h)h*jE��h,}rò��(UreftypeX���funcjH��âjI��X
���MNRead.getU	refdomainX���pyrô��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��jr��Njs��Nuh5KFh!]rö��ju��)Årõ��}rú��(h&jó��h,}rù��(h.]h/]rû��(jR��jô��X���py-funcrü��eh0]h1]h3]uh'jï��h!]r†��h?X���MNRead.get()r°��ÖÅr¢��}r£��(h&U�h'jõ��ubah*j��ubaubh?X���), and reporting of activity
(r§��ÖÅr•��}r¶��(h&X���), and reporting of activity
(h'j��ubjA��)Årß��}r®��(h&X���:func:`MNCore.getLogRecords`r©��h'j��h(h)h*jE��h,}r™��(UreftypeX���funcjH��âjI��X���MNCore.getLogRecordsU	refdomainX���pyr´��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��jr��Njs��Nuh5KFh!]r¨��ju��)År≠��}rÆ��(h&j©��h,}rØ��(h.]h/]r∞��(jR��j´��X���py-funcr±��eh0]h1]h3]uh'jß��h!]r≤��h?X���MNCore.getLogRecords()r≥��ÖÅr¥��}rµ��(h&U�h'j≠��ubah*j��ubaubh?X���).r∂��ÖÅr∑��}r∏��(h&X���).h'j��ubeubhC)Årπ��}r∫��(h&Xi��There are basically three types of object being made available by Member Nodes
and processed by DataONE: :term:`data object`s, :term:`science metadata`
objects, and :term:`resource map documents`. Each of these are identifiable by
their unique identifier (PID), and each has associated System Metadata which
describes the type, size, and so forth of the object.h'h$h(h)h*hFh,}rª��(h.]h/]h0]h1]h3]uh5KWh6hh!]rº��(h?Xi���There are basically three types of object being made available by Member Nodes
and processed by DataONE: rΩ��ÖÅræ��}rø��(h&Xi���There are basically three types of object being made available by Member Nodes
and processed by DataONE: h'jπ��ubjA��)År¿��}r¡��(h&X.���:term:`data object`s, :term:`science metadata`r¬��h'jπ��h(h)h*jE��h,}r√��(UreftypeX���termjH��àjI��X&���data object`s, :term:`science metadataU	refdomainX���stdrƒ��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5KWh!]r≈��jM��)År∆��}r«��(h&j¬��h,}r»��(h.]h/]r…��(jR��jƒ��X���std-termr ��eh0]h1]h3]uh'j¿��h!]rÀ��h?X&���data object`s, :term:`science metadatarÃ��ÖÅrÕ��}rŒ��(h&U�h'j∆��ubah*jW��ubaubh?X���
objects, and rœ��ÖÅr–��}r—��(h&X���
objects, and h'jπ��ubjA��)År“��}r”��(h&X���:term:`resource map documents`r‘��h'jπ��h(h)h*jE��h,}r’��(UreftypeX���termjH��àjI��X���resource map documentsU	refdomainX���stdr÷��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5KWh!]r◊��jM��)Årÿ��}rŸ��(h&j‘��h,}r⁄��(h.]h/]r€��(jR��j÷��X���std-termr‹��eh0]h1]h3]uh'j“��h!]r›��h?X���resource map documentsrﬁ��ÖÅrﬂ��}r‡��(h&U�h'jÿ��ubah*jW��ubaubh?X¶���. Each of these are identifiable by
their unique identifier (PID), and each has associated System Metadata which
describes the type, size, and so forth of the object.r·��ÖÅr‚��}r„��(h&X¶���. Each of these are identifiable by
their unique identifier (PID), and each has associated System Metadata which
describes the type, size, and so forth of the object.h'jπ��ubeubhC)År‰��}rÂ��(h&X∆���:term:`Data objects` are treated as opaque blobs. The object availability is
registered by the coordinating nodes, and the blob is retrievable via the
:func:`MNRead.get` method given its identifier.h'h$h(h)h*hFh,}rÊ��(h.]h/]h0]h1]h3]uh5K]h6hh!]rÁ��(jA��)ÅrË��}rÈ��(h&X���:term:`Data objects`rÍ��h'j‰��h(h)h*jE��h,}rÎ��(UreftypeX���termjH��àjI��X���data objectsU	refdomainX���stdrÏ��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5K]h!]rÌ��jM��)ÅrÓ��}rÔ��(h&jÍ��h,}r��(h.]h/]rÒ��(jR��jÏ��X���std-termrÚ��eh0]h1]h3]uh'jË��h!]rÛ��h?X���Data objectsrÙ��ÖÅrı��}rˆ��(h&U�h'jÓ��ubah*jW��ubaubh?XÉ��� are treated as opaque blobs. The object availability is
registered by the coordinating nodes, and the blob is retrievable via the
r˜��ÖÅr¯��}r˘��(h&XÉ��� are treated as opaque blobs. The object availability is
registered by the coordinating nodes, and the blob is retrievable via the
h'j‰��ubjA��)År˙��}r˚��(h&X���:func:`MNRead.get`r¸��h'j‰��h(h)h*jE��h,}r˝��(UreftypeX���funcjH��âjI��X
���MNRead.getU	refdomainX���pyr˛��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��jr��Njs��Nuh5K]h!]rˇ��ju��)År���}r��(h&j¸��h,}r��(h.]h/]r��(jR��j˛��X���py-funcr��eh0]h1]h3]uh'j˙��h!]r��h?X���MNRead.get()r��ÖÅr��}r��(h&U�h'j���ubah*j��ubaubh?X��� method given its identifier.r	��ÖÅr
��}r��(h&X��� method given its identifier.h'j‰��ubeubhC)År��}r
��(h&XŸ���:term:`Science metadata` objects are metadata documents such as EML, FGDC,
ISO19115 and so forth that provide metadata describing some data object(s).
These are represented in XML according to their respective schema.h'h$h(h)h*hFh,}r��(h.]h/]h0]h1]h3]uh5Kah6hh!]r��(jA��)År��}r��(h&X���:term:`Science metadata`r��h'j��h(h)h*jE��h,}r��(UreftypeX���termjH��àjI��X���science metadataU	refdomainX���stdr��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5Kah!]r��jM��)År��}r��(h&j��h,}r��(h.]h/]r��(jR��j��X���std-termr��eh0]h1]h3]uh'j��h!]r��h?X���Science metadatar��ÖÅr��}r��(h&U�h'j��ubah*jW��ubaubh?X¡��� objects are metadata documents such as EML, FGDC,
ISO19115 and so forth that provide metadata describing some data object(s).
These are represented in XML according to their respective schema.r��ÖÅr ��}r!��(h&X¡��� objects are metadata documents such as EML, FGDC,
ISO19115 and so forth that provide metadata describing some data object(s).
These are represented in XML according to their respective schema.h'j��ubeubhC)År"��}r#��(h&X¢���:term:`Resource map` documents describe the relationships between data and
metadata - they are basically RDF documents that conform to the OAI-ORE
specifications.h'h$h(h)h*hFh,}r$��(h.]h/]h0]h1]h3]uh5Keh6hh!]r%��(jA��)År&��}r'��(h&X���:term:`Resource map`r(��h'j"��h(h)h*jE��h,}r)��(UreftypeX���termjH��àjI��X���resource mapU	refdomainX���stdr*��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5Keh!]r+��jM��)År,��}r-��(h&j(��h,}r.��(h.]h/]r/��(jR��j*��X���std-termr0��eh0]h1]h3]uh'j&��h!]r1��h?X���Resource mapr2��ÖÅr3��}r4��(h&U�h'j,��ubah*jW��ubaubh?Xé��� documents describe the relationships between data and
metadata - they are basically RDF documents that conform to the OAI-ORE
specifications.r5��ÖÅr6��}r7��(h&Xé��� documents describe the relationships between data and
metadata - they are basically RDF documents that conform to the OAI-ORE
specifications.h'j"��ubeubhC)År8��}r9��(h&X€���From an object or class inheritance perspective, science metadata and resource
maps might be considered specializations of the data object type in that more
functionality is provided to DataONE by those types of object.r:��h'h$h(h)h*hFh,}r;��(h.]h/]h0]h1]h3]uh5Kih6hh!]r<��h?X€���From an object or class inheritance perspective, science metadata and resource
maps might be considered specializations of the data object type in that more
functionality is provided to DataONE by those types of object.r=��ÖÅr>��}r?��(h&j:��h'j8��ubaubhC)År@��}rA��(h&XÊ���From a purely technical perspective, a Member Node may be completely
functional and not provide any metadata or resource map documents. It will
mean that the content provided will not be discoverable through the search
interfaces.rB��h'h$h(h)h*hFh,}rC��(h.]h/]h0]h1]h3]uh5Kmh6hh!]rD��h?XÊ���From a purely technical perspective, a Member Node may be completely
functional and not provide any metadata or resource map documents. It will
mean that the content provided will not be discoverable through the search
interfaces.rE��ÖÅrF��}rG��(h&jB��h'j@��ubaubhC)ÅrH��}rI��(h&X(��Member Nodes may implement a subset of the full suite of :doc:`Member Node
APIs</apis/MN_APIs>`, and in this way participate in the network with minimal
effort (e.g. as a "read only" or :term:`Tier 1` Member Node). Member Nodes
that implement the full suite of APIs (a :term:`Tier 4` Member Node) will be
able to accept data from other Member Nodes which in turn assists with data
preservation by ensuring multiple copies of all content are available, thus
reducing the risk that content will be lost or inaccessible if a Member Node
should go offline.h'h$h(h)h*hFh,}rJ��(h.]h/]h0]h1]h3]uh5Krh6hh!]rK��(h?X9���Member Nodes may implement a subset of the full suite of rL��ÖÅrM��}rN��(h&X9���Member Nodes may implement a subset of the full suite of h'jH��ubjA��)ÅrO��}rP��(h&X&���:doc:`Member Node
APIs</apis/MN_APIs>`rQ��h'jH��h(h)h*jE��h,}rR��(UreftypeX���docrS��jH��àjI��X
���/apis/MN_APIsU	refdomainU�h1]h0]Urefexplicitàh.]h/]h3]jJ��jK��uh5Krh!]rT��jM��)ÅrU��}rV��(h&jQ��h,}rW��(h.]h/]rX��(jR��jS��eh0]h1]h3]uh'jO��h!]rY��h?X���Member Node
APIsrZ��ÖÅr[��}r\��(h&U�h'jU��ubah*jW��ubaubh?X[���, and in this way participate in the network with minimal
effort (e.g. as a "read only" or r]��ÖÅr^��}r_��(h&X[���, and in this way participate in the network with minimal
effort (e.g. as a "read only" or h'jH��ubjA��)År`��}ra��(h&X���:term:`Tier 1`rb��h'jH��h(h)h*jE��h,}rc��(UreftypeX���termjH��àjI��X���tier 1U	refdomainX���stdrd��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5Krh!]re��jM��)Årf��}rg��(h&jb��h,}rh��(h.]h/]ri��(jR��jd��X���std-termrj��eh0]h1]h3]uh'j`��h!]rk��h?X���Tier 1rl��ÖÅrm��}rn��(h&U�h'jf��ubah*jW��ubaubh?XE��� Member Node). Member Nodes
that implement the full suite of APIs (a ro��ÖÅrp��}rq��(h&XE��� Member Node). Member Nodes
that implement the full suite of APIs (a h'jH��ubjA��)Årr��}rs��(h&X���:term:`Tier 4`rt��h'jH��h(h)h*jE��h,}ru��(UreftypeX���termjH��àjI��X���tier 4U	refdomainX���stdrv��h1]h0]Urefexplicitâh.]h/]h3]jJ��jK��uh5Krh!]rw��jM��)Årx��}ry��(h&jt��h,}rz��(h.]h/]r{��(jR��jv��X���std-termr|��eh0]h1]h3]uh'jr��h!]r}��h?X���Tier 4r~��ÖÅr��}rÄ��(h&U�h'jx��ubah*jW��ubaubh?X
�� Member Node) will be
able to accept data from other Member Nodes which in turn assists with data
preservation by ensuring multiple copies of all content are available, thus
reducing the risk that content will be lost or inaccessible if a Member Node
should go offline.rÅ��ÖÅrÇ��}rÉ��(h&X
�� Member Node) will be
able to accept data from other Member Nodes which in turn assists with data
preservation by ensuring multiple copies of all content are available, thus
reducing the risk that content will be lost or inaccessible if a Member Node
should go offline.h'jH��ubeubhC)ÅrÑ��}rÖ��(h&Xı���Member Nodes may eventually number in the thousands as progressively smaller
repositories come online, perhaps even to the level of individual labs
deploying their own Member Node to take advantage of the broad infrastructure
enabled by DataONE.rÜ��h'h$h(h)h*hFh,}rá��(h.]h/]h0]h1]h3]uh5K{h6hh!]rà��h?Xı���Member Nodes may eventually number in the thousands as progressively smaller
repositories come online, perhaps even to the level of individual labs
deploying their own Member Node to take advantage of the broad infrastructure
enabled by DataONE.râ��ÖÅrä��}rã��(h&jÜ��h'jÑ��ubaubh¿)Årå��}rç��(h&X$���[[ Coordinating Node APIs diagram ]]h'h$h(h)h*h√h,}ré��(h≈h∆h1]h0]h.]h/]h3]uh5KÇh6hh!]rè��h?X$���[[ Coordinating Node APIs diagram ]]rê��ÖÅrë��}rí��(h&U�h'jå��ubaubhC)Årì��}rî��(h&X˚��Coordinating Nodes make critical services available through the
:doc:`APIs</apis/CN_APIs>` that enable identifier resolution, data
preservation, data discovery, and supplement the federated identity system.
Coordinating Nodes replicate all content between themselves, an in doing so
create a small set (3-6 nodes) of geographically and institutionally isolated
systems that ensure ongoing operation of the infrastructure should any
particular node be inaccessible. Coordinating Nodes maintain complete copies
of all science metadata (detailed descriptions of science data objects and
collections) and system metadata (low level metadata describing the type,
size, ownership, and locations of data and) and index this information to
enable data discovery services.h'h$h(h)h*hFh,}rï��(h.]h/]h0]h1]h3]uh5KÉh6hh!]rñ��(h?X@���Coordinating Nodes make critical services available through the
ró��ÖÅrò��}rô��(h&X@���Coordinating Nodes make critical services available through the
h'jì��ubjA��)Årö��}rõ��(h&X���:doc:`APIs</apis/CN_APIs>`rú��h'jì��h(h)h*jE��h,}rù��(UreftypeX���docrû��jH��àjI��X
���/apis/CN_APIsU	refdomainU�h1]h0]Urefexplicitàh.]h/]h3]jJ��jK��uh5KÉh!]rü��jM��)År†��}r°��(h&jú��h,}r¢��(h.]h/]r£��(jR��jû��eh0]h1]h3]uh'jö��h!]r§��h?X���APIsr•��ÖÅr¶��}rß��(h&U�h'j†��ubah*jW��ubaubh?X°�� that enable identifier resolution, data
preservation, data discovery, and supplement the federated identity system.
Coordinating Nodes replicate all content between themselves, an in doing so
create a small set (3-6 nodes) of geographically and institutionally isolated
systems that ensure ongoing operation of the infrastructure should any
particular node be inaccessible. Coordinating Nodes maintain complete copies
of all science metadata (detailed descriptions of science data objects and
collections) and system metadata (low level metadata describing the type,
size, ownership, and locations of data and) and index this information to
enable data discovery services.r®��ÖÅr©��}r™��(h&X°�� that enable identifier resolution, data
preservation, data discovery, and supplement the federated identity system.
Coordinating Nodes replicate all content between themselves, an in doing so
create a small set (3-6 nodes) of geographically and institutionally isolated
systems that ensure ongoing operation of the infrastructure should any
particular node be inaccessible. Coordinating Nodes maintain complete copies
of all science metadata (detailed descriptions of science data objects and
collections) and system metadata (low level metadata describing the type,
size, ownership, and locations of data and) and index this information to
enable data discovery services.h'jì��ubeubh¿)År´��}r¨��(h&X%���[[ ITK APIs and components diagram ]]h'h$h(h)h*h√h,}r≠��(h≈h∆h1]h0]h.]h/]h3]uh5Këh6hh!]rÆ��h?X%���[[ ITK APIs and components diagram ]]rØ��ÖÅr∞��}r±��(h&U�h'j´��ubaubhC)År≤��}r≥��(h&X+��Investigator Toolkit is a suite of software libraries, tools, and applications
that support interaction with the DataONE infrastructure through the
:doc:`REST</apis/REST_interface>` service APIs exposed by the
:doc:`Coordinating</apis/CN_APIs>` and :doc:`Member</apis/MN_APIs>` Nodes. Low
level libraries are initially available in Python and Java which assist
application developers to take advantage of the core services exposed by
DataONE participants. For example, an R plugin has been developed using the
Java library. Enabling this plugin within a R script enables discovery,
retrieval, and storage of content directly in the DataONE infrastructure.
Similar extensions are being developed for workflow tools such as Kepler,
VisTrails and Science Pipes to enable interaction with the core DataONE
services.h'h$h(h)h*hFh,}r¥��(h.]h/]h0]h1]h3]uh5Kíh6hh!]rµ��(h?Xî���Investigator Toolkit is a suite of software libraries, tools, and applications
that support interaction with the DataONE infrastructure through the
r∂��ÖÅr∑��}r∏��(h&Xî���Investigator Toolkit is a suite of software libraries, tools, and applications
that support interaction with the DataONE infrastructure through the
h'j≤��ubjA��)Årπ��}r∫��(h&X!���:doc:`REST</apis/REST_interface>`rª��h'j≤��h(h)h*jE��h,}rº��(UreftypeX���docrΩ��jH��àjI��X���/apis/REST_interfaceU	refdomainU�h1]h0]Urefexplicitàh.]h/]h3]jJ��jK��uh5Kíh!]ræ��jM��)Årø��}r¿��(h&jª��h,}r¡��(h.]h/]r¬��(jR��jΩ��eh0]h1]h3]uh'jπ��h!]r√��h?X���RESTrƒ��ÖÅr≈��}r∆��(h&U�h'jø��ubah*jW��ubaubh?X��� service APIs exposed by the
r«��ÖÅr»��}r…��(h&X��� service APIs exposed by the
h'j≤��ubjA��)År ��}rÀ��(h&X"���:doc:`Coordinating</apis/CN_APIs>`rÃ��h'j≤��h(h)h*jE��h,}rÕ��(UreftypeX���docrŒ��jH��àjI��X
���/apis/CN_APIsU	refdomainU�h1]h0]Urefexplicitàh.]h/]h3]jJ��jK��uh5Kíh!]rœ��jM��)År–��}r—��(h&jÃ��h,}r“��(h.]h/]r”��(jR��jŒ��eh0]h1]h3]uh'j ��h!]r‘��h?X���Coordinatingr’��ÖÅr÷��}r◊��(h&U�h'j–��ubah*jW��ubaubh?X��� and rÿ��ÖÅrŸ��}r⁄��(h&X��� and h'j≤��ubjA��)År€��}r‹��(h&X���:doc:`Member</apis/MN_APIs>`r›��h'j≤��h(h)h*jE��h,}rﬁ��(UreftypeX���docrﬂ��jH��àjI��X
���/apis/MN_APIsU	refdomainU�h1]h0]Urefexplicitàh.]h/]h3]jJ��jK��uh5Kíh!]r‡��jM��)År·��}r‚��(h&j›��h,}r„��(h.]h/]r‰��(jR��jﬂ��eh0]h1]h3]uh'j€��h!]rÂ��h?X���MemberrÊ��ÖÅrÁ��}rË��(h&U�h'j·��ubah*jW��ubaubh?X�� Nodes. Low
level libraries are initially available in Python and Java which assist
application developers to take advantage of the core services exposed by
DataONE participants. For example, an R plugin has been developed using the
Java library. Enabling this plugin within a R script enables discovery,
retrieval, and storage of content directly in the DataONE infrastructure.
Similar extensions are being developed for workflow tools such as Kepler,
VisTrails and Science Pipes to enable interaction with the core DataONE
services.rÈ��ÖÅrÍ��}rÎ��(h&X�� Nodes. Low
level libraries are initially available in Python and Java which assist
application developers to take advantage of the core services exposed by
DataONE participants. For example, an R plugin has been developed using the
Java library. Enabling this plugin within a R script enables discovery,
retrieval, and storage of content directly in the DataONE infrastructure.
Similar extensions are being developed for workflow tools such as Kepler,
VisTrails and Science Pipes to enable interaction with the core DataONE
services.h'j≤��ubeubhC)ÅrÏ��}rÌ��(h&Xp��The DataONE infrastructure was released for public use in July 2012 and at
that point supported identifier resolution, content discovery and retrieval
and the federated identity management infrastructure. The replication service
was implemented with release 1.1 of the infrastructure which occurred in May
of 2013 and completed the core services of the infrastructure.rÓ��h'h$h(h)h*hFh,}rÔ��(h.]h/]h0]h1]h3]uh5Küh6hh!]r��h?Xp��The DataONE infrastructure was released for public use in July 2012 and at
that point supported identifier resolution, content discovery and retrieval
and the federated identity management infrastructure. The replication service
was implemented with release 1.1 of the infrastructure which occurred in May
of 2013 and completed the core services of the infrastructure.rÒ��ÖÅrÚ��}rÛ��(h&jÓ��h'jÏ��ubaubcdocutils.nodes
target
rÙ��)Årı��}rˆ��(h&XH���.. _DataNet program:  http://www.nsf.gov/pubs/2007/nsf07601/nsf07601.htmU
referencedr˜��Kh'h$h(h)h*Utargetr¯��h,}r˘��(hRhSh1]r˙��h ah0]h.]h/]h3]r˚��hauh5K¶h6hh!]ubjÙ��)År¸��}r˝��(h&XN���.. _Cyberinfrastructure Vision: http://www.nsf.gov/pubs/2007/nsf0728/index.jspj˜��Kh'h$h(h)h*j¯��h,}r˛��(hRh^h1]rˇ��hah0]h.]h/]h3]r���hauh5K®h6hh!]ubjÙ��)År��}r��(h&X ���.. _DataONE: http://dataone.org/j˜��Kh'h$h(h)h*j¯��h,}r��(hRhih1]r��hah0]h.]h/]h3]r��h
auh5K™h6hh!]ubjÙ��)År��}r��(h&X ���.. _Dryad: http://datadryad.org/h'h$h(h)h*j¯��h,}r��(hRX���http://datadryad.org/h1]r	��hah0]h.]h/]h3]r
��h
auh5K¨h6hh!]ubjÙ��)År��}r��(h&XY���.. _Partnership for Interdisciplinary Studies of Coastal Oceans: http://www.piscoweb.org/j˜��Kh'h$h(h)h*j¯��h,}r
��(hRj9��h1]r��hah0]h.]h/]h3]r��hauh5KÆh6hh!]ubjÙ��)År��}r��(h&XF���.. _Knowledge Network for Biodiversity: http://knb.ecoinformatics.org/j˜��Kh'h$h(h)h*j¯��h,}r��(hRj#��h1]r��hah0]h.]h/]h3]r��hauh5K∞h6hh!]ubjÙ��)År��}r��(h&X$���.. _ORNL DAAC: http://daac.ornl.gov/j˜��Kh'h$h(h)h*j¯��h,}r��(hRj.��h1]r��hah0]h.]h/]h3]r��hauh5K≤h6hh!]ubjÙ��)År��}r��(h&XH���.. _NBII Metadata Clearing House: http://mercury.ornl.gov/clearinghouse/h'h$h(h)h*j¯��h,}r��(hRX&���http://mercury.ornl.gov/clearinghouse/h1]r��hah0]h.]h/]h3]r��hauh5K¥h6hh!]ubeubah&U�Utransformerr��NU
footnote_refsr ��}r!��Urefnamesr"��}r#��(X���cyberinfrastructure vision]r$��h[aX���dataone]r%��hfaX"���knowledge network for biodiversity]r&��j ��aX	���ornl daac]r'��j+��aX;���partnership for interdisciplinary studies of coastal oceans]r(��j6��aX���datanet program]r)��hMauUsymbol_footnotesr*��]r+��Uautofootnote_refsr,��]r-��Usymbol_footnote_refsr.��]r/��U	citationsr0��]r1��h6hUcurrent_liner2��NUtransform_messagesr3��]r4��(cdocutils.nodes
system_message
r5��)År6��}r7��(h&U�h,}r8��(h.]UlevelKh1]h0]Usourceh)h/]h3]UlineK¨UtypeUINFOr9��uh!]r:��hC)År;��}r<��(h&U�h,}r=��(h.]h/]h0]h1]h3]uh'j6��h!]r>��h?X+���Hyperlink target "dryad" is not referenced.r?��ÖÅr@��}rA��(h&U�h'j;��ubah*hFubah*Usystem_messagerB��ubj5��)ÅrC��}rD��(h&U�h,}rE��(h.]UlevelKh1]h0]Usourceh)h/]h3]UlineK¥Utypej9��uh!]rF��hC)ÅrG��}rH��(h&U�h,}rI��(h.]h/]h0]h1]h3]uh'jC��h!]rJ��h?XB���Hyperlink target "nbii metadata clearing house" is not referenced.rK��ÖÅrL��}rM��(h&U�h'jG��ubah*hFubah*jB��ubeUreporterrN��NUid_startrO��KU
autofootnotesrP��]rQ��U
citation_refsrR��}rS��Uindirect_targetsrT��]rU��UsettingsrV��(cdocutils.frontend
Values
rW��orX��}rY��(Ufootnote_backlinksrZ��KUrecord_dependenciesr[��NUrfc_base_urlr\��Uhttps://tools.ietf.org/html/r]��U	tracebackr^��àUpep_referencesr_��NUstrip_commentsr`��NU
toc_backlinksra��Uentryrb��U
language_coderc��Uenrd��U	datestampre��NUreport_levelrf��KU_destinationrg��NU
halt_levelrh��KU
strip_classesri��Nh<NUerror_encoding_error_handlerrj��Ubackslashreplacerk��Udebugrl��NUembed_stylesheetrm��âUoutput_encoding_error_handlerrn��Ustrictro��U
sectnum_xformrp��KUdump_transformsrq��NU
docinfo_xformrr��KUwarning_streamrs��NUpep_file_url_templatert��Upep-%04dru��Uexit_status_levelrv��KUconfigrw��NUstrict_visitorrx��NUcloak_email_addressesry��àUtrim_footnote_reference_spacerz��âUenvr{��NUdump_pseudo_xmlr|��NUexpose_internalsr}��NUsectsubtitle_xformr~��âUsource_linkr��NUrfc_referencesrÄ��NUoutput_encodingrÅ��Uutf-8rÇ��U
source_urlrÉ��NUinput_encodingrÑ��U	utf-8-sigrÖ��U_disable_configrÜ��NU	id_prefixrá��U�U	tab_widthrà��KUerror_encodingrâ��UUTF-8rä��U_sourcerã��h)Ugettext_compactrå��àU	generatorrç��NUdump_internalsré��NUsmart_quotesrè��âUpep_base_urlrê��U https://www.python.org/dev/peps/rë��Usyntax_highlightrí��Ulongrì��Uinput_encoding_error_handlerrî��jo��Uauto_id_prefixrï��Uidrñ��Udoctitle_xformró��âUstrip_elements_with_classesrò��NU
_config_filesrô��]Ufile_insertion_enabledrö��àUraw_enabledrõ��KU
dump_settingsrú��NubUsymbol_footnote_startrù��K�Uidsrû��}rü��(h jı��hj��hj��hj��hj¸��hj��hh$hj��hj��uUsubstitution_namesr†��}r°��h*h6h,}r¢��(h.]h1]h0]Usourceh)h/]h3]uU	footnotesr£��]r§��Urefidsr•��}r¶��ub.