Äcdocutils.nodes
document
q)Åq}q(U	nametypesq}q(X���what premis suggestsqNXX���requirement 7: record provenance information (e.g., prinicpal, timestamp, event, rights)qNX���descriptionqNX5���requirement 1: perform replication on digital objectsq	NX���introductionq
NXV���requirement 6: record software and hardware specifications for future object renderingqNX
���discussionqNX6���getting a handle on systems metadata for the long haulq
NX
���conclusionqNX,���requirement 5: support digital object re-useqNX/���requirement 4: support digital object discoveryqNX���system metadata requirementsqNXJ���requirement 8: record information to ensure viability of preserved objectsqNX"���dataone use cases and requirementsqNX
���referencesqNX-���requirement 2: perform preservation migrationqNXE���requirement 3: record specific types of relationships between objectsqNX8���requirement 10: ensure that principals are authenticatedqNXM���requirement 9: record information to ensure authenticity of preserved objectsqNX���what bagit and oai-ore provideqNuUsubstitution_defsq}qUparse_messagesq]q(cdocutils.nodes
system_message
q)Åq}q (U	rawsourceq!U�Uparentq"cdocutils.nodes
section
q#)Åq$}q%(h!U�U
referencedq&Kh"h#)Åq'}q((h!U�h"h#)Åq)}q*(h!U�h"h#)Åq+}q,(h!U�h"hUsourceq-Xr���/var/lib/jenkins/jobs/API_Documentation_trunk/workspace/api-documentation/source/design/SystemMetadataAnalysis.txtq.Utagnameq/Usectionq0U
attributesq1}q2(Udupnamesq3]Uclassesq4]Ubackrefsq5]Uidsq6]q7U6getting-a-handle-on-systems-metadata-for-the-long-haulq8aUnamesq9]q:h
auUlineq;KUdocumentq<hUchildrenq=]q>(cdocutils.nodes
title
q?)Åq@}qA(h!X6���Getting a Handle on Systems Metadata for the Long HaulqBh"h+h-h.h/UtitleqCh1}qD(h3]h4]h5]h6]h9]uh;Kh<hh=]qEcdocutils.nodes
Text
qFX6���Getting a Handle on Systems Metadata for the Long HaulqGÖÅqH}qI(h!hBh"h@ubaubcdocutils.nodes
field_list
qJ)ÅqK}qL(h!U�h"h+h-h.h/U
field_listqMh1}qN(h3]h4]h5]h6]h9]uh;Kh<hh=]qOcdocutils.nodes
field
qP)ÅqQ}qR(h!U�h"hKh-h.h/UfieldqSh1}qT(h3]h4]h5]h6]h9]uh;Kh<hh=]qU(cdocutils.nodes
field_name
qV)ÅqW}qX(h!X	���RevisionsqYh"hQh-h.h/U
field_nameqZh1}q[(h3]h4]h5]h6]h9]uh;K�h=]q\hFX	���Revisionsq]ÖÅq^}q_(h!hYh"hWubaubcdocutils.nodes
field_body
q`)Åqa}qb(h!X°��======== ============================================================
Date     Comment
======== ============================================================
20100416 (Sandusky) Additional text; discussions of PREMIS, BagIt, ORE
20100402 (Allen, Sandusky) Additional text
20100326 (Allen) Added more text and structure
20100312 (Allen) First draft
======== ============================================================
h1}qc(h3]h4]h5]h6]h9]uh"hQh=]qdcdocutils.nodes
table
qe)Åqf}qg(h!U�h1}qh(h3]h4]h5]h6]h9]uh"hah=]qicdocutils.nodes
tgroup
qj)Åqk}ql(h!U�h1}qm(h6]h5]h3]h4]h9]UcolsKuh"hfh=]qn(cdocutils.nodes
colspec
qo)Åqp}qq(h!U�h1}qr(h6]h5]h3]h4]h9]UcolwidthKuh"hkh=]h/Ucolspecqsubho)Åqt}qu(h!U�h1}qv(h6]h5]h3]h4]h9]UcolwidthK=uh"hkh=]h/hsubcdocutils.nodes
thead
qw)Åqx}qy(h!U�h1}qz(h3]h4]h5]h6]h9]uh"hkh=]q{cdocutils.nodes
row
q|)Åq}}q~(h!U�h1}q(h3]h4]h5]h6]h9]uh"hxh=]qÄ(cdocutils.nodes
entry
qÅ)ÅqÇ}qÉ(h!U�h1}qÑ(h3]h4]h5]h6]h9]uh"h}h=]qÖcdocutils.nodes
paragraph
qÜ)Åqá}qà(h!X���Dateqâh"hÇh-h.h/U	paragraphqäh1}qã(h3]h4]h5]h6]h9]uh;Kh=]qåhFX���DateqçÖÅqé}qè(h!hâh"háubaubah/UentryqêubhÅ)Åqë}qí(h!U�h1}qì(h3]h4]h5]h6]h9]uh"h}h=]qîhÜ)Åqï}qñ(h!X���Commentqóh"hëh-h.h/häh1}qò(h3]h4]h5]h6]h9]uh;Kh=]qôhFX���CommentqöÖÅqõ}qú(h!hóh"hïubaubah/hêubeh/Urowqùubah/Utheadqûubcdocutils.nodes
tbody
qü)Åq†}q°(h!U�h1}q¢(h3]h4]h5]h6]h9]uh"hkh=]q£(h|)Åq§}q•(h!U�h1}q¶(h3]h4]h5]h6]h9]uh"h†h=]qß(hÅ)Åq®}q©(h!U�h1}q™(h3]h4]h5]h6]h9]uh"h§h=]q´hÜ)Åq¨}q≠(h!X���20100416qÆh"h®h-h.h/häh1}qØ(h3]h4]h5]h6]h9]uh;Kh=]q∞hFX���20100416q±ÖÅq≤}q≥(h!hÆh"h¨ubaubah/hêubhÅ)Åq¥}qµ(h!U�h1}q∂(h3]h4]h5]h6]h9]uh"h§h=]q∑hÜ)Åq∏}qπ(h!X=���(Sandusky) Additional text; discussions of PREMIS, BagIt, OREq∫h"h¥h-h.h/häh1}qª(h3]h4]h5]h6]h9]uh;Kh=]qºhFX=���(Sandusky) Additional text; discussions of PREMIS, BagIt, OREqΩÖÅqæ}qø(h!h∫h"h∏ubaubah/hêubeh/hùubh|)Åq¿}q¡(h!U�h1}q¬(h3]h4]h5]h6]h9]uh"h†h=]q√(hÅ)Åqƒ}q≈(h!U�h1}q∆(h3]h4]h5]h6]h9]uh"h¿h=]q«hÜ)Åq»}q…(h!X���20100402q h"hƒh-h.h/häh1}qÀ(h3]h4]h5]h6]h9]uh;K	h=]qÃhFX���20100402qÕÖÅqŒ}qœ(h!h h"h»ubaubah/hêubhÅ)Åq–}q—(h!U�h1}q“(h3]h4]h5]h6]h9]uh"h¿h=]q”hÜ)Åq‘}q’(h!X!���(Allen, Sandusky) Additional textq÷h"h–h-h.h/häh1}q◊(h3]h4]h5]h6]h9]uh;K	h=]qÿhFX!���(Allen, Sandusky) Additional textqŸÖÅq⁄}q€(h!h÷h"h‘ubaubah/hêubeh/hùubh|)Åq‹}q›(h!U�h1}qfi(h3]h4]h5]h6]h9]uh"h†h=]qfl(hÅ)Åq‡}q·(h!U�h1}q‚(h3]h4]h5]h6]h9]uh"h‹h=]q„hÜ)Åq‰}qÂ(h!X���20100326qÊh"h‡h-h.h/häh1}qÁ(h3]h4]h5]h6]h9]uh;K
h=]qËhFX���20100326qÈÖÅqÍ}qÎ(h!hÊh"h‰ubaubah/hêubhÅ)ÅqÏ}qÌ(h!U�h1}qÓ(h3]h4]h5]h6]h9]uh"h‹h=]qÔhÜ)Åq}qÒ(h!X%���(Allen) Added more text and structureqÚh"hÏh-h.h/häh1}qÛ(h3]h4]h5]h6]h9]uh;K
h=]qÙhFX%���(Allen) Added more text and structureqıÖÅqˆ}q˜(h!hÚh"hubaubah/hêubeh/hùubh|)Åq¯}q˘(h!U�h1}q˙(h3]h4]h5]h6]h9]uh"h†h=]q˚(hÅ)Åq¸}q˝(h!U�h1}q˛(h3]h4]h5]h6]h9]uh"h¯h=]qˇhÜ)År���}r��(h!X���20100312r��h"h¸h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;Kh=]r��hFX���20100312r��ÖÅr��}r��(h!j��h"j���ubaubah/hêubhÅ)År��}r	��(h!U�h1}r
��(h3]h4]h5]h6]h9]uh"h¯h=]r��hÜ)År��}r
��(h!X���(Allen) First draftr��h"j��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;Kh=]r��hFX���(Allen) First draftr��ÖÅr��}r��(h!j��h"j��ubaubah/hêubeh/hùubeh/Utbodyr��ubeh/Utgroupr��ubah/Utabler��ubah/U
field_bodyr��ubeubaubh#)År��}r��(h!U�h"h+h-h.h/h0h1}r��(h3]h4]h5]h6]r��Uintroductionr��ah9]r��h
auh;Kh<hh=]r��(h?)År��}r ��(h!X���Introductionr!��h"j��h-h.h/hCh1}r"��(h3]h4]h5]h6]h9]uh;Kh<hh=]r#��hFX���Introductionr$��ÖÅr%��}r&��(h!j!��h"j��ubaubhÜ)År'��}r(��(h!Xë��The DataONE systems metadata is critical to ensuring that science data, science
metadata, and other digital objects stored in DataONE are discoverable,
accessible, auditable, verifiable, and are associated with meaningful related
digital objects. Digital objects in DataONE must also be viable for the long
term - for many decades - and so the system metadata must also include
provenance information.r)��h"j��h-h.h/häh1}r*��(h3]h4]h5]h6]h9]uh;Kh<hh=]r+��hFXë��The DataONE systems metadata is critical to ensuring that science data, science
metadata, and other digital objects stored in DataONE are discoverable,
accessible, auditable, verifiable, and are associated with meaningful related
digital objects. Digital objects in DataONE must also be viable for the long
term - for many decades - and so the system metadata must also include
provenance information.r,��ÖÅr-��}r.��(h!j)��h"j'��ubaubhÜ)År/��}r0��(h!Xh��Due primarily to the project deliverable schedule, the current DataONE system
metadata definition (DataONE, 2010b) is focused on the essential metadata values
that must be available to support the earliest versions of DataONE. So far,
relatively little attention has been paid to ensuring that system metadata
contains appropriate attributes for the long haul.r1��h"j��h-h.h/häh1}r2��(h3]h4]h5]h6]h9]uh;Kh<hh=]r3��hFXh��Due primarily to the project deliverable schedule, the current DataONE system
metadata definition (DataONE, 2010b) is focused on the essential metadata values
that must be available to support the earliest versions of DataONE. So far,
relatively little attention has been paid to ensuring that system metadata
contains appropriate attributes for the long haul.r4��ÖÅr5��}r6��(h!j1��h"j/��ubaubhÜ)År7��}r8��(h!XK��This document describes some of the results of a practicum project carried out
by Elizabeth (Betsy) Allen in Spring 2010. The PREMIS Data Dictionary for
Preservation Metadata was used as a standard against which the explicit and
implicit requirements of DataONE would be measured: "The PREMIS Data Dictionary
defines 'preservation metadata' as the information a repository usees to support
the digital preservation process" (PREMIS Editorial Committee, 2008, p.3).
PREMIS is focused on the "viabilility, renderability, understandability,
authenticity, and identity" of digital objects "in a preservation context"
(i.e., DataONE), and pays particular attention to "digital provenance (the
history of an object and to the documentation of relationships, especially
relationships among different objects within the preservation repository" (p.3).r9��h"j��h-h.h/häh1}r:��(h3]h4]h5]h6]h9]uh;Kh<hh=]r;��hFXK��This document describes some of the results of a practicum project carried out
by Elizabeth (Betsy) Allen in Spring 2010. The PREMIS Data Dictionary for
Preservation Metadata was used as a standard against which the explicit and
implicit requirements of DataONE would be measured: "The PREMIS Data Dictionary
defines 'preservation metadata' as the information a repository usees to support
the digital preservation process" (PREMIS Editorial Committee, 2008, p.3).
PREMIS is focused on the "viabilility, renderability, understandability,
authenticity, and identity" of digital objects "in a preservation context"
(i.e., DataONE), and pays particular attention to "digital provenance (the
history of an object and to the documentation of relationships, especially
relationships among different objects within the preservation repository" (p.3).r<��ÖÅr=��}r>��(h!j9��h"j7��ubaubhÜ)År?��}r@��(h!X‰��The PREMIS Data Dictionary seeks to identify "core" elements with its set of
definitions, where core implies "things that most working preservation
repositories are likely to need to know in order to support digital
preservation" (p.3). PREMIS also considered "implementability": because of the
large amounts of data held within preservation systems, metadata values should
be suppied autmatically and be capable of automated processing: required human
intervention should be avoided.rA��h"j��h-h.h/häh1}rB��(h3]h4]h5]h6]h9]uh;K*h<hh=]rC��hFX‰��The PREMIS Data Dictionary seeks to identify "core" elements with its set of
definitions, where core implies "things that most working preservation
repositories are likely to need to know in order to support digital
preservation" (p.3). PREMIS also considered "implementability": because of the
large amounts of data held within preservation systems, metadata values should
be suppied autmatically and be capable of automated processing: required human
intervention should be avoided.rD��ÖÅrE��}rF��(h!jA��h"j?��ubaubhÜ)ÅrG��}rH��(h!X’��It should also be noted that PREMIS has been created according to the "1:1
principle" which "asserts that each description describes one and only one
resource.... It is not possible to change a file...; on can only create a new
file... that is related to the source object" (p.14). The practicality of this
principle in DataONE has been debated by the Core Cyberinfrastructure Team,
which recognizes its conceptual cleanliness as well as its operational
impracticality.rI��h"j��h-h.h/häh1}rJ��(h3]h4]h5]h6]h9]uh;K2h<hh=]rK��hFX’��It should also be noted that PREMIS has been created according to the "1:1
principle" which "asserts that each description describes one and only one
resource.... It is not possible to change a file...; on can only create a new
file... that is related to the source object" (p.14). The practicality of this
principle in DataONE has been debated by the Core Cyberinfrastructure Team,
which recognizes its conceptual cleanliness as well as its operational
impracticality.rL��ÖÅrM��}rN��(h!jI��h"jG��ubaubhÜ)ÅrO��}rP��(h!Xö���PREMIS does not specify formats or other requirements for how preservation is
implemented in a preservation repository: these are left as local decisions.rQ��h"j��h-h.h/häh1}rR��(h3]h4]h5]h6]h9]uh;K:h<hh=]rS��hFXö���PREMIS does not specify formats or other requirements for how preservation is
implemented in a preservation repository: these are left as local decisions.rT��ÖÅrU��}rV��(h!jQ��h"jO��ubaubhÜ)ÅrW��}rX��(h!X>��DataONE, as a preservation repository, could aim toward "PREMIS conformance" by
implementing metadata elements that share the names and semantics of PREMIS Data
Dictionary semantic units. PREMIS is also intended to be a foundation for
interoperable preservation repositories (pp.15-16); PREMIS recommends using its
semantic unit names to aid this interoperability. This document does not argue
for or against seeking PREMIS conformance for DataONE; rather, it seeks to
identify and summarize topics and outstanding issues for discussion within the
broader DataONE community.rY��h"j��h-h.h/häh1}rZ��(h3]h4]h5]h6]h9]uh;K=h<hh=]r[��hFX>��DataONE, as a preservation repository, could aim toward "PREMIS conformance" by
implementing metadata elements that share the names and semantics of PREMIS Data
Dictionary semantic units. PREMIS is also intended to be a foundation for
interoperable preservation repositories (pp.15-16); PREMIS recommends using its
semantic unit names to aid this interoperability. This document does not argue
for or against seeking PREMIS conformance for DataONE; rather, it seeks to
identify and summarize topics and outstanding issues for discussion within the
broader DataONE community.r\��ÖÅr]��}r^��(h!jY��h"jW��ubaubhÜ)År_��}r`��(h!X„��This practicum project also took the Open Archives Initiative's Object Reuse and
Exchange (OAI-ORE) (Lagoze et al, 2008) and the BagIt File Packaging Format
(Boyko et al, 2009) into account as possible standards for aggregations, or
packages, of Web resources and as possible methods for recording the
relationships between preserved objects in DataONE. BagIt is "is a hierarchical
file packaging format designed to support disk-based or network-based storage
and transfer of generalized digital content" (p.3). OAI-ORE "defines standards
for the description and exchange of aggregations of Web resources". This
document looks at the points where BagIt and OAI-ORE may play a role in
supporting the long-term preservation needs of DataONE.ra��h"j��h-h.h/häh1}rb��(h3]h4]h5]h6]h9]uh;KFh<hh=]rc��hFX„��This practicum project also took the Open Archives Initiative's Object Reuse and
Exchange (OAI-ORE) (Lagoze et al, 2008) and the BagIt File Packaging Format
(Boyko et al, 2009) into account as possible standards for aggregations, or
packages, of Web resources and as possible methods for recording the
relationships between preserved objects in DataONE. BagIt is "is a hierarchical
file packaging format designed to support disk-based or network-based storage
and transfer of generalized digital content" (p.3). OAI-ORE "defines standards
for the description and exchange of aggregations of Web resources". This
document looks at the points where BagIt and OAI-ORE may play a role in
supporting the long-term preservation needs of DataONE.rd��ÖÅre��}rf��(h!ja��h"j_��ubaubhÜ)Årg��}rh��(h!Xç��BagIt and OAI-ORE have different strengths, and both systems have potential for
use within DataONE. Their differences are significant, and so they cannot be
viewed as substitutes for each other. The strengths of BagIt include simplicity
(text and file/directory orientations; supports opaque payloads; supports
aggregation; self-describing); its limitations include its hierarchical
structure and what appears to be the "fixed-in-time" nature of a bag: the
specification doesn't discuss how the content of a bag might evolve over time,
which limits its utility for application to supporting provenance tracking for
objects in a preseravation repository.ri��h"j��h-h.h/häh1}rj��(h3]h4]h5]h6]h9]uh;KQh<hh=]rk��hFXç��BagIt and OAI-ORE have different strengths, and both systems have potential for
use within DataONE. Their differences are significant, and so they cannot be
viewed as substitutes for each other. The strengths of BagIt include simplicity
(text and file/directory orientations; supports opaque payloads; supports
aggregation; self-describing); its limitations include its hierarchical
structure and what appears to be the "fixed-in-time" nature of a bag: the
specification doesn't discuss how the content of a bag might evolve over time,
which limits its utility for application to supporting provenance tracking for
objects in a preseravation repository.rl��ÖÅrm��}rn��(h!ji��h"jg��ubaubhÜ)Åro��}rp��(h!XB��OAI-ORE's strengths include its flexibility and extensibility, its graph-based
architecture, specifications based upon stable and widely-used technologies
included the URI and RDF, and the ability for relationships to be added to
existing OAI-ORE resources as time passes. OAI-ORE is also related to other
efforts that may play a role in DataONE, such as the Open Annotation
Collaboration (http://www.openannotation.org/). OAI-ORE's flexibility has a cost
in terms of its complexity, so it will be more costly to develop and maintain a
reliable implementation (although its current popularity may mean that existing
code implementations may be available for use within DataONE). OAI-ORE is also
expressed in XML, which tends to increase storage consumption. Large XML data
stores are also time-consuming to parse without optimization.h"j��h-h.h/häh1}rq��(h3]h4]h5]h6]h9]uh;K[h<hh=]rr��(hFXÜ��OAI-ORE's strengths include its flexibility and extensibility, its graph-based
architecture, specifications based upon stable and widely-used technologies
included the URI and RDF, and the ability for relationships to be added to
existing OAI-ORE resources as time passes. OAI-ORE is also related to other
efforts that may play a role in DataONE, such as the Open Annotation
Collaboration (rs��ÖÅrt��}ru��(h!XÜ��OAI-ORE's strengths include its flexibility and extensibility, its graph-based
architecture, specifications based upon stable and widely-used technologies
included the URI and RDF, and the ability for relationships to be added to
existing OAI-ORE resources as time passes. OAI-ORE is also related to other
efforts that may play a role in DataONE, such as the Open Annotation
Collaboration (h"jo��ubcdocutils.nodes
reference
rv��)Årw��}rx��(h!X���http://www.openannotation.org/ry��h1}rz��(Urefurijy��h6]h5]h3]h4]h9]uh"jo��h=]r{��hFX���http://www.openannotation.org/r|��ÖÅr}��}r~��(h!U�h"jw��ubah/U	referencer��ubhFXû��). OAI-ORE's flexibility has a cost
in terms of its complexity, so it will be more costly to develop and maintain a
reliable implementation (although its current popularity may mean that existing
code implementations may be available for use within DataONE). OAI-ORE is also
expressed in XML, which tends to increase storage consumption. Large XML data
stores are also time-consuming to parse without optimization.rÄ��ÖÅrÅ��}rÇ��(h!Xû��). OAI-ORE's flexibility has a cost
in terms of its complexity, so it will be more costly to develop and maintain a
reliable implementation (although its current popularity may mean that existing
code implementations may be available for use within DataONE). OAI-ORE is also
expressed in XML, which tends to increase storage consumption. Large XML data
stores are also time-consuming to parse without optimization.h"jo��ubeubhÜ)ÅrÉ��}rÑ��(h!X¬��The document is organized as follows. A set of high-level requirements was
developed to represent the general needs of the DataONE system metadata. For
each of the high-level requirements identified, the relevant sections of the
PREMIS data dictionary were identified, and missing, additional, mismatched
aspects are identified in the text. The documentation for BagIt and OAI-ORE were
consulted and their relevance to the requirement is also discussed in the text.
Optionally, use cases relevant to the requirement are described, using science
data specified in EML, Dryad, ORNL DAAC, and/or NBII formats as examples. The
section on each requirement ends with a general discussion of the overall
analysis.rÖ��h"j��h-h.h/häh1}rÜ��(h3]h4]h5]h6]h9]uh;Kgh<hh=]rá��hFX¬��The document is organized as follows. A set of high-level requirements was
developed to represent the general needs of the DataONE system metadata. For
each of the high-level requirements identified, the relevant sections of the
PREMIS data dictionary were identified, and missing, additional, mismatched
aspects are identified in the text. The documentation for BagIt and OAI-ORE were
consulted and their relevance to the requirement is also discussed in the text.
Optionally, use cases relevant to the requirement are described, using science
data specified in EML, Dryad, ORNL DAAC, and/or NBII formats as examples. The
section on each requirement ends with a general discussion of the overall
analysis.rà��ÖÅrâ��}rä��(h!jÖ��h"jÉ��ubaubeubh)h#)Årã��}rå��(h!U�h&Kh"h+h-h.h/h0h1}rç��(h3]ré��X
���discussionrè��ah4]h5]h6]rê��Uid20rë��ah9]uh;MPh<hh=]rí��(h?)Årì��}rî��(h!X
���Discussionrï��h"jã��h-h.h/hCh1}rñ��(h3]h4]h5]h6]h9]uh;MPh<hh=]ró��hFX
���Discussionrò��ÖÅrô��}rö��(h!jï��h"jì��ubaubh#)Årõ��}rú��(h!U�h"jã��h-h.h/h0h1}rù��(h3]h4]h5]h6]rû��UUrequirement-6-record-software-and-hardware-specifications-for-future-object-renderingrü��ah9]r†��hauh;MSh<hh=]r°��(h?)År¢��}r£��(h!XV���Requirement 6: Record software and hardware specifications for future object renderingr§��h"jõ��h-h.h/hCh1}r•��(h3]h4]h5]h6]h9]uh;MSh<hh=]r¶��hFXV���Requirement 6: Record software and hardware specifications for future object renderingrß��ÖÅr®��}r©��(h!j§��h"j¢��ubaubh#)År™��}r´��(h!U�h&Kh"jõ��h-h.h/h0h1}r¨��(h3]r≠��X���descriptionrÆ��ah4]h5]h6]rØ��Uid21r∞��ah9]uh;MVh<hh=]r±��(h?)År≤��}r≥��(h!X���Descriptionr¥��h"j™��h-h.h/hCh1}rµ��(h3]h4]h5]h6]h9]uh;MVh<hh=]r∂��hFX���Descriptionr∑��ÖÅr∏��}rπ��(h!j¥��h"j≤��ubaubhÜ)År∫��}rª��(h!X>���Emulation is a core preservation strategy for digital objects.rº��h"j™��h-h.h/häh1}rΩ��(h3]h4]h5]h6]h9]uh;MXh<hh=]ræ��hFX>���Emulation is a core preservation strategy for digital objects.rø��ÖÅr¿��}r¡��(h!jº��h"j∫��ubaubeubh#)År¬��}r√��(h!U�h&Kh"jõ��h-h.h/h0h1}rƒ��(h3]r≈��X���what premis suggestsr∆��ah4]h5]h6]r«��Uid22r»��ah9]uh;M[h<hh=]r…��(h?)År ��}rÀ��(h!X���What PREMIS suggestsrÃ��h"j¬��h-h.h/hCh1}rÕ��(h3]h4]h5]h6]h9]uh;M[h<hh=]rŒ��hFX���What PREMIS suggestsrœ��ÖÅr–��}r—��(h!jÃ��h"j ��ubaubhÜ)År“��}r”��(h!Xm��PREMIS provides the notion of a representation to as "the set of files required"
to "maintain usable versions of intellectual entities over time" (p. 8).
Emulation is one preservation approach to ensure long-term usability of digital
objects. To emulate a digital object whose format is obsolete, the DataONE
system must record information that characterizes both the software (1.8.5) and
hardware (1.8.6) environent for each object. PREMIS requires software/hardware
name and type to be recorded, while software version (1.8.5.2), software
components needed by the software (1.8.5.5), and other information are optional.r‘��h"j¬��h-h.h/häh1}r’��(h3]h4]h5]h6]h9]uh;M]h<hh=]r÷��hFXm��PREMIS provides the notion of a representation to as "the set of files required"
to "maintain usable versions of intellectual entities over time" (p. 8).
Emulation is one preservation approach to ensure long-term usability of digital
objects. To emulate a digital object whose format is obsolete, the DataONE
system must record information that characterizes both the software (1.8.5) and
hardware (1.8.6) environent for each object. PREMIS requires software/hardware
name and type to be recorded, while software version (1.8.5.2), software
components needed by the software (1.8.5.5), and other information are optional.r◊��ÖÅrÿ��}rŸ��(h!j‘��h"j“��ubaubeubh#)År⁄��}r€��(h!U�h&Kh"jõ��h-h.h/h0h1}r‹��(h3]r›��X���what bagit and oai-ore providerfi��ah4]h5]h6]rfl��Uid23r‡��ah9]uh;Mgh<hh=]r·��h?)År‚��}r„��(h!X���What BagIt and OAI-ORE provider‰��h"j⁄��h-h.h/hCh1}rÂ��(h3]h4]h5]h6]h9]uh;Mgh<hh=]rÊ��hFX���What BagIt and OAI-ORE providerÁ��ÖÅrË��}rÈ��(h!j‰��h"j‚��ubaubaubh#)ÅrÍ��}rÎ��(h!U�h&Kh"jõ��h-h.h/h0h1}rÏ��(h3]rÌ��X"���dataone use cases and requirementsrÓ��ah4]h5]h6]rÔ��Uid24r��ah9]uh;Mjh<hh=]rÒ��(h?)ÅrÚ��}rÛ��(h!X"���DataONE use cases and requirementsrÙ��h"jÍ��h-h.h/hCh1}rı��(h3]h4]h5]h6]h9]uh;Mjh<hh=]rˆ��hFX"���DataONE use cases and requirementsr˜��ÖÅr¯��}r˘��(h!jÙ��h"jÚ��ubaubhÜ)År˙��}r˚��(h!Xp���(Requirement) The infrastructure must support long term preservation of data
https://trac.dataone.org/ticket/410h"jÍ��h-h.h/häh1}r¸��(h3]h4]h5]h6]h9]uh;Mlh<hh=]r˝��(hFXM���(Requirement) The infrastructure must support long term preservation of data
r˛��ÖÅrˇ��}r���(h!XM���(Requirement) The infrastructure must support long term preservation of data
h"j˙��ubjv��)År��}r��(h!X#���https://trac.dataone.org/ticket/410r��h1}r��(Urefurij��h6]h5]h3]h4]h9]uh"j˙��h=]r��hFX#���https://trac.dataone.org/ticket/410r��ÖÅr��}r��(h!U�h"j��ubah/j��ubeubhÜ)År	��}r
��(h!Xb���(Requirement) Maintain original copies of all science metadata
https://trac.dataone.org/ticket/439h"jÍ��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;Moh<hh=]r��(hFX?���(Requirement) Maintain original copies of all science metadata
r
��ÖÅr��}r��(h!X?���(Requirement) Maintain original copies of all science metadata
h"j	��ubjv��)År��}r��(h!X#���https://trac.dataone.org/ticket/439r��h1}r��(Urefurij��h6]h5]h3]h4]h9]uh"j	��h=]r��hFX#���https://trac.dataone.org/ticket/439r��ÖÅr��}r��(h!U�h"j��ubah/j��ubeubeubh#)År��}r��(h!U�h&Kh"jõ��h-h.h/h0h1}r��(h3]r��X
���discussionr��ah4]h5]h6]r��Uid25r��ah9]uh;Msh<hh=]r��h?)År ��}r!��(h!X
���Discussionr"��h"j��h-h.h/hCh1}r#��(h3]h4]h5]h6]h9]uh;Msh<hh=]r$��hFX
���Discussionr%��ÖÅr&��}r'��(h!j"��h"j ��ubaubaubeubh#)År(��}r)��(h!U�h"jã��h-h.h/h0h1}r*��(h3]h4]h5]h6]r+��UPrequirement-7-record-provenance-information-e-g-prinicpal-timestamp-event-rightsr,��ah9]r-��hauh;Mwh<hh=]r.��(h?)År/��}r0��(h!XX���Requirement 7: Record provenance information (e.g., prinicpal, timestamp, event, rights)r1��h"j(��h-h.h/hCh1}r2��(h3]h4]h5]h6]h9]uh;Mwh<hh=]r3��hFXX���Requirement 7: Record provenance information (e.g., prinicpal, timestamp, event, rights)r4��ÖÅr5��}r6��(h!j1��h"j/��ubaubh#)År7��}r8��(h!U�h&Kh"j(��h-h.h/h0h1}r9��(h3]r:��X���descriptionr;��ah4]h5]h6]r<��Uid26r=��ah9]uh;M{h<hh=]r>��(h?)År?��}r@��(h!X���DescriptionrA��h"j7��h-h.h/hCh1}rB��(h3]h4]h5]h6]h9]uh;M{h<hh=]rC��hFX���DescriptionrD��ÖÅrE��}rF��(h!jA��h"j?��ubaubhÜ)ÅrG��}rH��(h!XM��Recording provenance allows users of digital objects to follow who has created
and acted upon the object, what action was taken, and when the action occured.
PREMIS uses associations between events and objects to record provenance.
PREMIS, however, leaves decisions on which events are worthy of recording to the
preservation system.rI��h"j7��h-h.h/häh1}rJ��(h3]h4]h5]h6]h9]uh;M}h<hh=]rK��hFXM��Recording provenance allows users of digital objects to follow who has created
and acted upon the object, what action was taken, and when the action occured.
PREMIS uses associations between events and objects to record provenance.
PREMIS, however, leaves decisions on which events are worthy of recording to the
preservation system.rL��ÖÅrM��}rN��(h!jI��h"jG��ubaubeubh#)ÅrO��}rP��(h!U�h&Kh"j(��h-h.h/h0h1}rQ��(h3]rR��X���what premis suggestsrS��ah4]h5]h6]rT��Uid27rU��ah9]uh;MÖh<hh=]rV��(h?)ÅrW��}rX��(h!X���What PREMIS suggestsrY��h"jO��h-h.h/hCh1}rZ��(h3]h4]h5]h6]h9]uh;MÖh<hh=]r[��hFX���What PREMIS suggestsr\��ÖÅr]��}r^��(h!jY��h"jW��ubaubhÜ)År_��}r`��(h!XU��PREMIS states that provenance is one of the many attributes necessary for a
digital object to be authentic (pg. 200); however, because demonstrating
provenance involves many semantic units, it deserves to be its own requirement
rather than a sub-requirement for authenticity [bad justification?]. The DataONE
systems would capture provenance by recording who is doing what to the digital
object through time. This includes recording information on the unique object
identifier (1.1), the original name of the object if it was not created within
the repository (1.6), and any relationships this item has with other digital
objects such as "is a source of" (1.10). The majority of semantic units
necessary to record provenance come from the event entity. The system will need
to create a unique identifier for each event (2.1), describe the event type
taken from a controlled vocabulary, (e.g. migration and ingestion)(2.1), and
record when the event occurred (2.3). Optionally, ir could store details about
the event, which are non-machine readable (2.4), and any information on the
success of the event (2.5).ra��h"jO��h-h.h/häh1}rb��(h3]h4]h5]h6]h9]uh;Máh<hh=]rc��hFXU��PREMIS states that provenance is one of the many attributes necessary for a
digital object to be authentic (pg. 200); however, because demonstrating
provenance involves many semantic units, it deserves to be its own requirement
rather than a sub-requirement for authenticity [bad justification?]. The DataONE
systems would capture provenance by recording who is doing what to the digital
object through time. This includes recording information on the unique object
identifier (1.1), the original name of the object if it was not created within
the repository (1.6), and any relationships this item has with other digital
objects such as "is a source of" (1.10). The majority of semantic units
necessary to record provenance come from the event entity. The system will need
to create a unique identifier for each event (2.1), describe the event type
taken from a controlled vocabulary, (e.g. migration and ingestion)(2.1), and
record when the event occurred (2.3). Optionally, ir could store details about
the event, which are non-machine readable (2.4), and any information on the
success of the event (2.5).rd��ÖÅre��}rf��(h!ja��h"j_��ubaubeubh#)Årg��}rh��(h!U�h&Kh"j(��h-h.h/h0h1}ri��(h3]rj��X���what bagit and oai-ore providerk��ah4]h5]h6]rl��Uid28rm��ah9]uh;Mòh<hh=]rn��h?)Åro��}rp��(h!X���What BagIt and OAI-ORE providerq��h"jg��h-h.h/hCh1}rr��(h3]h4]h5]h6]h9]uh;Mòh<hh=]rs��hFX���What BagIt and OAI-ORE providert��ÖÅru��}rv��(h!jq��h"jo��ubaubaubh#)Årw��}rx��(h!U�h&Kh"j(��h-h.h/h0h1}ry��(h3]rz��X"���dataone use cases and requirementsr{��ah4]h5]h6]r|��Uid29r}��ah9]uh;Mõh<hh=]r~��(h?)År��}rÄ��(h!X"���DataONE use cases and requirementsrÅ��h"jw��h-h.h/hCh1}rÇ��(h3]h4]h5]h6]h9]uh;Mõh<hh=]rÉ��hFX"���DataONE use cases and requirementsrÑ��ÖÅrÖ��}rÜ��(h!jÅ��h"j��ubaubhÜ)Årá��}rà��(h!XM���(Requirement) Identifiers for all objects https://trac.dataone.org/ticket/317râ��h"jw��h-h.h/häh1}rä��(h3]h4]h5]h6]h9]uh;Mùh<hh=]rã��(hFX*���(Requirement) Identifiers for all objects rå��ÖÅrç��}ré��(h!X*���(Requirement) Identifiers for all objects h"já��ubjv��)Årè��}rê��(h!X#���https://trac.dataone.org/ticket/317rë��h1}rí��(Urefurijë��h6]h5]h3]h4]h9]uh"já��h=]rì��hFX#���https://trac.dataone.org/ticket/317rî��ÖÅrï��}rñ��(h!U�h"jè��ubah/j��ubeubhÜ)Åró��}rò��(h!XV���(Requirement) Support arbitrary unique identifiers
https://trac.dataone.org/ticket/385h"jw��h-h.h/häh1}rô��(h3]h4]h5]h6]h9]uh;Müh<hh=]rö��(hFX3���(Requirement) Support arbitrary unique identifiers
rõ��ÖÅrú��}rù��(h!X3���(Requirement) Support arbitrary unique identifiers
h"jó��ubjv��)Årû��}rü��(h!X#���https://trac.dataone.org/ticket/385r†��h1}r°��(Urefurij†��h6]h5]h3]h4]h9]uh"jó��h=]r¢��hFX#���https://trac.dataone.org/ticket/385r£��ÖÅr§��}r•��(h!U�h"jû��ubah/j��ubeubhÜ)År¶��}rß��(h!X\���(Requirement) Consistent mechanism for identifying users
https://trac.dataone.org/ticket/390h"jw��h-h.h/häh1}r®��(h3]h4]h5]h6]h9]uh;M¢h<hh=]r©��(hFX9���(Requirement) Consistent mechanism for identifying users
r™��ÖÅr´��}r¨��(h!X9���(Requirement) Consistent mechanism for identifying users
h"j¶��ubjv��)År≠��}rÆ��(h!X#���https://trac.dataone.org/ticket/390rØ��h1}r∞��(UrefurijØ��h6]h5]h3]h4]h9]uh"j¶��h=]r±��hFX#���https://trac.dataone.org/ticket/390r≤��ÖÅr≥��}r¥��(h!U�h"j≠��ubah/j��ubeubhÜ)Årµ��}r∂��(h!X]���(Requirement) Identifiers always refer to the same object
https://trac.dataone.org/ticket/412h"jw��h-h.h/häh1}r∑��(h3]h4]h5]h6]h9]uh;M•h<hh=]r∏��(hFX:���(Requirement) Identifiers always refer to the same object
rπ��ÖÅr∫��}rª��(h!X:���(Requirement) Identifiers always refer to the same object
h"jµ��ubjv��)Årº��}rΩ��(h!X#���https://trac.dataone.org/ticket/412ræ��h1}rø��(Urefurijæ��h6]h5]h3]h4]h9]uh"jµ��h=]r¿��hFX#���https://trac.dataone.org/ticket/412r¡��ÖÅr¬��}r√��(h!U�h"jº��ubah/j��ubeubeubh#)Årƒ��}r≈��(h!U�h&Kh"j(��h-h.h/h0h1}r∆��(h3]r«��X
���discussionr»��ah4]h5]h6]r…��Uid30r ��ah9]uh;M©h<hh=]rÀ��h?)ÅrÃ��}rÕ��(h!X
���DiscussionrŒ��h"jƒ��h-h.h/hCh1}rœ��(h3]h4]h5]h6]h9]uh;M©h<hh=]r–��hFX
���Discussionr—��ÖÅr“��}r”��(h!jŒ��h"jÃ��ubaubaubeubh#)År‘��}r’��(h!U�h"jã��h-h.h/h0h1}r÷��(h3]h4]h5]h6]r◊��UIrequirement-8-record-information-to-ensure-viability-of-preserved-objectsrÿ��ah9]rŸ��hauh;M¨h<hh=]r⁄��(h?)År€��}r‹��(h!XJ���Requirement 8: Record information to ensure viability of preserved objectsr›��h"j‘��h-h.h/hCh1}rfi��(h3]h4]h5]h6]h9]uh;M¨h<hh=]rfl��hFXJ���Requirement 8: Record information to ensure viability of preserved objectsr‡��ÖÅr·��}r‚��(h!j›��h"j€��ubaubh#)År„��}r‰��(h!U�h&Kh"j‘��h-h.h/h0h1}rÂ��(h3]rÊ��X���descriptionrÁ��ah4]h5]h6]rË��Uid31rÈ��ah9]uh;M∞h<hh=]rÍ��h?)ÅrÎ��}rÏ��(h!X���DescriptionrÌ��h"j„��h-h.h/hCh1}rÓ��(h3]h4]h5]h6]h9]uh;M∞h<hh=]rÔ��hFX���Descriptionr��ÖÅrÒ��}rÚ��(h!jÌ��h"jÎ��ubaubaubh#)ÅrÛ��}rÙ��(h!U�h&Kh"j‘��h-h.h/h0h1}rı��(h3]rˆ��X���what premis suggestsr˜��ah4]h5]h6]r¯��Uid32r˘��ah9]uh;M¥h<hh=]r˙��(h?)År˚��}r¸��(h!X���What PREMIS suggestsr˝��h"jÛ��h-h.h/hCh1}r˛��(h3]h4]h5]h6]h9]uh;M¥h<hh=]rˇ��hFX���What PREMIS suggestsr���ÖÅr��}r��(h!j˝��h"j˚��ubaubhÜ)År��}r��(h!XÖ��PREMIS defines viability as the "property of being readable from media". The
PREMIS working group intentionally avoided defining detailed semanitc units for
viability with the exception of 1.7.2, storage media, where the medium for
storing an object is defined. More detailed information on media would likely be
desirable so that repository managers would know when to refresh the medium.r��h"jÛ��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;M∂h<hh=]r��hFXÖ��PREMIS defines viability as the "property of being readable from media". The
PREMIS working group intentionally avoided defining detailed semanitc units for
viability with the exception of 1.7.2, storage media, where the medium for
storing an object is defined. More detailed information on media would likely be
desirable so that repository managers would know when to refresh the medium.r��ÖÅr	��}r
��(h!j��h"j��ubaubeubh#)År��}r��(h!U�h&Kh"j‘��h-h.h/h0h1}r
��(h3]r��X���what bagit and oai-ore provider��ah4]h5]h6]r��Uid33r��ah9]uh;MΩh<hh=]r��h?)År��}r��(h!X���What BagIt and OAI-ORE provider��h"j��h-h.h/hCh1}r��(h3]h4]h5]h6]h9]uh;MΩh<hh=]r��hFX���What BagIt and OAI-ORE provider��ÖÅr��}r��(h!j��h"j��ubaubaubh#)År��}r��(h!U�h&Kh"j‘��h-h.h/h0h1}r��(h3]r��X"���dataone use cases and requirementsr��ah4]h5]h6]r ��Uid34r!��ah9]uh;M¿h<hh=]r"��(h?)År#��}r$��(h!X"���DataONE use cases and requirementsr%��h"j��h-h.h/hCh1}r&��(h3]h4]h5]h6]h9]uh;M¿h<hh=]r'��hFX"���DataONE use cases and requirementsr(��ÖÅr)��}r*��(h!j%��h"j#��ubaubhÜ)År+��}r,��(h!Xp���(Requirement) The infrastructure must support long term preservation of data
https://trac.dataone.org/ticket/410h"j��h-h.h/häh1}r-��(h3]h4]h5]h6]h9]uh;M¬h<hh=]r.��(hFXM���(Requirement) The infrastructure must support long term preservation of data
r/��ÖÅr0��}r1��(h!XM���(Requirement) The infrastructure must support long term preservation of data
h"j+��ubjv��)År2��}r3��(h!X#���https://trac.dataone.org/ticket/410r4��h1}r5��(Urefurij4��h6]h5]h3]h4]h9]uh"j+��h=]r6��hFX#���https://trac.dataone.org/ticket/410r7��ÖÅr8��}r9��(h!U�h"j2��ubah/j��ubeubhÜ)År:��}r;��(h!Xb���(Requirement) Maintain original copies of all science metadata
https://trac.dataone.org/ticket/439h"j��h-h.h/häh1}r<��(h3]h4]h5]h6]h9]uh;M≈h<hh=]r=��(hFX?���(Requirement) Maintain original copies of all science metadata
r>��ÖÅr?��}r@��(h!X?���(Requirement) Maintain original copies of all science metadata
h"j:��ubjv��)ÅrA��}rB��(h!X#���https://trac.dataone.org/ticket/439rC��h1}rD��(UrefurijC��h6]h5]h3]h4]h9]uh"j:��h=]rE��hFX#���https://trac.dataone.org/ticket/439rF��ÖÅrG��}rH��(h!U�h"jA��ubah/j��ubeubeubh#)ÅrI��}rJ��(h!U�h&Kh"j‘��h-h.h/h0h1}rK��(h3]rL��X
���discussionrM��ah4]h5]h6]rN��Uid35rO��ah9]uh;M…h<hh=]rP��h?)ÅrQ��}rR��(h!X
���DiscussionrS��h"jI��h-h.h/hCh1}rT��(h3]h4]h5]h6]h9]uh;M…h<hh=]rU��hFX
���DiscussionrV��ÖÅrW��}rX��(h!jS��h"jQ��ubaubaubeubh#)ÅrY��}rZ��(h!U�h"jã��h-h.h/h0h1}r[��(h3]h4]h5]h6]r\��ULrequirement-9-record-information-to-ensure-authenticity-of-preserved-objectsr]��ah9]r^��hauh;MÕh<hh=]r_��(h?)År`��}ra��(h!XM���Requirement 9: Record information to ensure authenticity of preserved objectsrb��h"jY��h-h.h/hCh1}rc��(h3]h4]h5]h6]h9]uh;MÕh<hh=]rd��hFXM���Requirement 9: Record information to ensure authenticity of preserved objectsre��ÖÅrf��}rg��(h!jb��h"j`��ubaubh#)Årh��}ri��(h!U�h&Kh"jY��h-h.h/h0h1}rj��(h3]rk��X���descriptionrl��ah4]h5]h6]rm��Uid36rn��ah9]uh;M–h<hh=]ro��(h?)Årp��}rq��(h!X���Descriptionrr��h"jh��h-h.h/hCh1}rs��(h3]h4]h5]h6]h9]uh;M–h<hh=]rt��hFX���Descriptionru��ÖÅrv��}rw��(h!jr��h"jp��ubaubhÜ)Årx��}ry��(h!Xë���Authenticity is the "quality of being what it purports to be". This includes the
conepts of fixity, integrity, and the use of digital signatures.rz��h"jh��h-h.h/häh1}r{��(h3]h4]h5]h6]h9]uh;M“h<hh=]r|��hFXë���Authenticity is the "quality of being what it purports to be". This includes the
conepts of fixity, integrity, and the use of digital signatures.r}��ÖÅr~��}r��(h!jz��h"jx��ubaubeubh#)ÅrÄ��}rÅ��(h!U�h&Kh"jY��h-h.h/h0h1}rÇ��(h3]rÉ��X���what premis suggestsrÑ��ah4]h5]h6]rÖ��Uid37rÜ��ah9]uh;M◊h<hh=]rá��(h?)Årà��}râ��(h!X���What PREMIS suggestsrä��h"jÄ��h-h.h/hCh1}rã��(h3]h4]h5]h6]h9]uh;M◊h<hh=]rå��hFX���What PREMIS suggestsrç��ÖÅré��}rè��(h!jä��h"jà��ubaubhÜ)Årê��}rë��(h!X��PREMIS has many semantic units that can be used as evidence of an object's
authenticity (1.5 and its sub-units). It is mandatory to record either format
designation of the object from a controlled vocabulary (e.g. base64 or Adobe
PDF)(1.5.4) or identify the format type through reference to a format registry
(1.5.4.2). It is recommended, though optional, that the DataONE system record
the message digest (1.5.2.2), the specific algorithm used to create the message
digest (1.5.2.1), and who created the original digest (1.5.2.3).rí��h"jÄ��h-h.h/häh1}rì��(h3]h4]h5]h6]h9]uh;MŸh<hh=]rî��hFX��PREMIS has many semantic units that can be used as evidence of an object's
authenticity (1.5 and its sub-units). It is mandatory to record either format
designation of the object from a controlled vocabulary (e.g. base64 or Adobe
PDF)(1.5.4) or identify the format type through reference to a format registry
(1.5.4.2). It is recommended, though optional, that the DataONE system record
the message digest (1.5.2.2), the specific algorithm used to create the message
digest (1.5.2.1), and who created the original digest (1.5.2.3).rï��ÖÅrñ��}ró��(h!jí��h"jê��ubaubhÜ)Årò��}rô��(h!X&��Digital signature information is an optional unit in PREMIS (1.9). ["A
repository may have a policy of generating digital signatures for files on
ingest, or may have a need to store and later validate incoming digital
signatures". Which is it for DataONE or is it both?] To use digital signatures
the system need to record the signature value (1.9.1.4), the "designation for
the encryption and hash algorithms used for signature generation" (1.9.1.3), the
rules for validating the signature (1.9.1.5), the encoding used for the
singature (1.9.1.1), the signer's public key (1.9.1.7) and who created the
signature (1.9.1.2 or 3.1). [Should recording the object's size be a requirement
for authenticity? It is a characteristic, but I think it is more important for
ensuring that a replication was successful]rö��h"jÄ��h-h.h/häh1}rõ��(h3]h4]h5]h6]h9]uh;M·h<hh=]rú��hFX&��Digital signature information is an optional unit in PREMIS (1.9). ["A
repository may have a policy of generating digital signatures for files on
ingest, or may have a need to store and later validate incoming digital
signatures". Which is it for DataONE or is it both?] To use digital signatures
the system need to record the signature value (1.9.1.4), the "designation for
the encryption and hash algorithms used for signature generation" (1.9.1.3), the
rules for validating the signature (1.9.1.5), the encoding used for the
singature (1.9.1.1), the signer's public key (1.9.1.7) and who created the
signature (1.9.1.2 or 3.1). [Should recording the object's size be a requirement
for authenticity? It is a characteristic, but I think it is more important for
ensuring that a replication was successful]rù��ÖÅrû��}rü��(h!jö��h"jò��ubaubhÜ)År†��}r°��(h!Xæ��The semantic unit 1.5 is used to record object characteristics, but
demonstrating that the object characteristics are in fact valid occurs through
events. For example, performing regular fixity checks is captured through the
units event identifier (2.1), event type such as "fixity check" (2.2), and event
date (2.3). Digital signature validation and format validation are also types of
events that need to be recorded to show authenticity (2.3).r¢��h"jÄ��h-h.h/häh1}r£��(h3]h4]h5]h6]h9]uh;MÌh<hh=]r§��hFXæ��The semantic unit 1.5 is used to record object characteristics, but
demonstrating that the object characteristics are in fact valid occurs through
events. For example, performing regular fixity checks is captured through the
units event identifier (2.1), event type such as "fixity check" (2.2), and event
date (2.3). Digital signature validation and format validation are also types of
events that need to be recorded to show authenticity (2.3).r•��ÖÅr¶��}rß��(h!j¢��h"j†��ubaubeubh#)År®��}r©��(h!U�h&Kh"jY��h-h.h/h0h1}r™��(h3]r´��X���what bagit and oai-ore provider¨��ah4]h5]h6]r≠��Uid38rÆ��ah9]uh;Mıh<hh=]rØ��h?)År∞��}r±��(h!X���What BagIt and OAI-ORE provider≤��h"j®��h-h.h/hCh1}r≥��(h3]h4]h5]h6]h9]uh;Mıh<hh=]r¥��hFX���What BagIt and OAI-ORE providerµ��ÖÅr∂��}r∑��(h!j≤��h"j∞��ubaubaubh#)År∏��}rπ��(h!U�h&Kh"jY��h-h.h/h0h1}r∫��(h3]rª��X"���dataone use cases and requirementsrº��ah4]h5]h6]rΩ��Uid39ræ��ah9]uh;M¯h<hh=]rø��(h?)År¿��}r¡��(h!X"���DataONE use cases and requirementsr¬��h"j∏��h-h.h/hCh1}r√��(h3]h4]h5]h6]h9]uh;M¯h<hh=]rƒ��hFX"���DataONE use cases and requirementsr≈��ÖÅr∆��}r«��(h!j¬��h"j¿��ubaubhÜ)År»��}r…��(h!Xp���(Requirement) The infrastructure must support long term preservation of data
https://trac.dataone.org/ticket/410h"j∏��h-h.h/häh1}r ��(h3]h4]h5]h6]h9]uh;M˙h<hh=]rÀ��(hFXM���(Requirement) The infrastructure must support long term preservation of data
rÃ��ÖÅrÕ��}rŒ��(h!XM���(Requirement) The infrastructure must support long term preservation of data
h"j»��ubjv��)Årœ��}r–��(h!X#���https://trac.dataone.org/ticket/410r—��h1}r“��(Urefurij—��h6]h5]h3]h4]h9]uh"j»��h=]r”��hFX#���https://trac.dataone.org/ticket/410r‘��ÖÅr’��}r÷��(h!U�h"jœ��ubah/j��ubeubhÜ)År◊��}rÿ��(h!Xb���(Requirement) Maintain original copies of all science metadata
https://trac.dataone.org/ticket/439h"j∏��h-h.h/häh1}rŸ��(h3]h4]h5]h6]h9]uh;M˝h<hh=]r⁄��(hFX?���(Requirement) Maintain original copies of all science metadata
r€��ÖÅr‹��}r›��(h!X?���(Requirement) Maintain original copies of all science metadata
h"j◊��ubjv��)Årfi��}rfl��(h!X#���https://trac.dataone.org/ticket/439r‡��h1}r·��(Urefurij‡��h6]h5]h3]h4]h9]uh"j◊��h=]r‚��hFX#���https://trac.dataone.org/ticket/439r„��ÖÅr‰��}rÂ��(h!U�h"jfi��ubah/j��ubeubeubh#)ÅrÊ��}rÁ��(h!U�h&Kh"jY��h-h.h/h0h1}rË��(h3]rÈ��X
���discussionrÍ��ah4]h5]h6]rÎ��Uid40rÏ��ah9]uh;Mh<hh=]rÌ��h?)ÅrÓ��}rÔ��(h!X
���Discussionr��h"jÊ��h-h.h/hCh1}rÒ��(h3]h4]h5]h6]h9]uh;Mh<hh=]rÚ��hFX
���DiscussionrÛ��ÖÅrÙ��}rı��(h!j��h"jÓ��ubaubaubeubh#)Årˆ��}r˜��(h!U�h"jã��h-h.h/h0h1}r¯��(h3]h4]h5]h6]r˘��U7requirement-10-ensure-that-principals-are-authenticatedr˙��ah9]r˚��hauh;Mh<hh=]r¸��(h?)År˝��}r˛��(h!X8���Requirement 10: Ensure that principals are authenticatedrˇ��h"jˆ��h-h.h/hCh1}r���(h3]h4]h5]h6]h9]uh;Mh<hh=]r��hFX8���Requirement 10: Ensure that principals are authenticatedr��ÖÅr��}r��(h!jˇ��h"j˝��ubaubh#)År��}r��(h!U�h&Kh"jˆ��h-h.h/h0h1}r��(h3]r��X���descriptionr	��ah4]h5]h6]r
��Uid41r��ah9]uh;Mh<hh=]r��(h?)År
��}r��(h!X���Descriptionr��h"j��h-h.h/hCh1}r��(h3]h4]h5]h6]h9]uh;Mh<hh=]r��hFX���Descriptionr��ÖÅr��}r��(h!j��h"j
��ubaubhÜ)År��}r��(h!X#���Software, organization. public key,r��h"j��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;M	h<hh=]r��hFX#���Software, organization. public key,r��ÖÅr��}r��(h!j��h"j��ubaubeubh#)År��}r��(h!U�h&Kh"jˆ��h-h.h/h0h1}r��(h3]r ��X���what premis suggestsr!��ah4]h5]h6]r"��Uid42r#��ah9]uh;Mh<hh=]r$��(h?)År%��}r&��(h!X���What PREMIS suggestsr'��h"j��h-h.h/hCh1}r(��(h3]h4]h5]h6]h9]uh;Mh<hh=]r)��hFX���What PREMIS suggestsr*��ÖÅr+��}r,��(h!j'��h"j%��ubaubhÜ)År-��}r.��(h!X¸��Principals are called agents in PREMIS. They are associated with either events
that occur to a digital object or the rights associated with an object, but they
are never directly linked to an object. PREMIS only has one required semantic
unit for principal, which is agentIdentifier (3.1). Other optional units used to
describe an agent include name (3.2) and type such as organization, software or
person (3.3). The PREMIS Data Dictionary suggests that systems use digital
signatures for authenticating submitters to and distributors from the system;
however, because validation takes place right after signing, there is no need
for the respository to preserve the signature itself through time. The system
can record the act of validation as an Event if desired.r/��h"j��h-h.h/häh1}r0��(h3]h4]h5]h6]h9]uh;Mh<hh=]r1��hFX¸��Principals are called agents in PREMIS. They are associated with either events
that occur to a digital object or the rights associated with an object, but they
are never directly linked to an object. PREMIS only has one required semantic
unit for principal, which is agentIdentifier (3.1). Other optional units used to
describe an agent include name (3.2) and type such as organization, software or
person (3.3). The PREMIS Data Dictionary suggests that systems use digital
signatures for authenticating submitters to and distributors from the system;
however, because validation takes place right after signing, there is no need
for the respository to preserve the signature itself through time. The system
can record the act of validation as an Event if desired.r2��ÖÅr3��}r4��(h!j/��h"j-��ubaubeubh#)År5��}r6��(h!U�h&Kh"jˆ��h-h.h/h0h1}r7��(h3]r8��X���what bagit and oai-ore provider9��ah4]h5]h6]r:��Uid43r;��ah9]uh;Mh<hh=]r<��h?)År=��}r>��(h!X���What BagIt and OAI-ORE provider?��h"j5��h-h.h/hCh1}r@��(h3]h4]h5]h6]h9]uh;Mh<hh=]rA��hFX���What BagIt and OAI-ORE providerB��ÖÅrC��}rD��(h!j?��h"j=��ubaubaubh#)ÅrE��}rF��(h!U�h&Kh"jˆ��h-h.h/h0h1}rG��(h3]rH��X"���dataone use cases and requirementsrI��ah4]h5]h6]rJ��Uid44rK��ah9]uh;Mh<hh=]rL��(h?)ÅrM��}rN��(h!X"���DataONE use cases and requirementsrO��h"jE��h-h.h/hCh1}rP��(h3]h4]h5]h6]h9]uh;Mh<hh=]rQ��hFX"���DataONE use cases and requirementsrR��ÖÅrS��}rT��(h!jO��h"jM��ubaubhÜ)ÅrU��}rV��(h!X\���(Requirement) Consistent mechanism for identifying users
https://trac.dataone.org/ticket/390h"jE��h-h.h/häh1}rW��(h3]h4]h5]h6]h9]uh;Mh<hh=]rX��(hFX9���(Requirement) Consistent mechanism for identifying users
rY��ÖÅrZ��}r[��(h!X9���(Requirement) Consistent mechanism for identifying users
h"jU��ubjv��)År\��}r]��(h!X#���https://trac.dataone.org/ticket/390r^��h1}r_��(Urefurij^��h6]h5]h3]h4]h9]uh"jU��h=]r`��hFX#���https://trac.dataone.org/ticket/390ra��ÖÅrb��}rc��(h!U�h"j\��ubah/j��ubeubhÜ)Ård��}re��(h!Xq���(Requirement) Enable different classes of users commensurate with their roles
https://trac.dataone.org/ticket/391h"jE��h-h.h/häh1}rf��(h3]h4]h5]h6]h9]uh;M"h<hh=]rg��(hFXN���(Requirement) Enable different classes of users commensurate with their roles
rh��ÖÅri��}rj��(h!XN���(Requirement) Enable different classes of users commensurate with their roles
h"jd��ubjv��)Årk��}rl��(h!X#���https://trac.dataone.org/ticket/391rm��h1}rn��(Urefurijm��h6]h5]h3]h4]h9]uh"jd��h=]ro��hFX#���https://trac.dataone.org/ticket/391rp��ÖÅrq��}rr��(h!U�h"jk��ubah/j��ubeubeubh#)Års��}rt��(h!U�h&Kh"jˆ��h-h.h/h0h1}ru��(h3]rv��X
���discussionrw��ah4]h5]h6]rx��Uid45ry��ah9]uh;M&h<hh=]rz��h?)År{��}r|��(h!X
���Discussionr}��h"js��h-h.h/hCh1}r~��(h3]h4]h5]h6]h9]uh;M&h<hh=]r��hFX
���DiscussionrÄ��ÖÅrÅ��}rÇ��(h!j}��h"j{��ubaubaubeubeubh#)ÅrÉ��}rÑ��(h!U�h"h+h-h.h/h0h1}rÖ��(h3]h4]h5]h6]rÜ��U
conclusionrá��ah9]rà��hauh;M*h<hh=]râ��h?)Årä��}rã��(h!X
���Conclusionr�h"j��h-h.h/hCh1}r�(h3]h4]h5]h6]h9]uh;M*h<hh=]r�hFX
���Conclusionrè��ÖÅrê��}rë��(h!jå��h"jä��ubaubaubh#)Årí��}rì��(h!U�h"h+h-h.h/h0h1}rî��(h3]h4]h5]h6]rï��U
referencesrñ��ah9]ró��hauh;M.h<hh=]rò��(h?)Årô��}rö��(h!X
���Referencesrõ��h"jí��h-h.h/hCh1}rú��(h3]h4]h5]h6]h9]uh;M.h<hh=]rù��hFX
���Referencesrû��ÖÅrü��}r†��(h!jõ��h"jô��ubaubhÜ)År°��}r¢��(h!X≈���Boyko, A., Kunze, J., Littman, J., Madden, L., Vargas, B. (2009). The BagIt File
Packaging Format (V0.96). Retrieved April 2, 2010, from
http://www.ietf.org/Internet-drafts/draft-kunze-bagit-04.txth"jí��h-h.h/häh1}r£��(h3]h4]h5]h6]h9]uh;M/h<hh=]r§��(hFXâ���Boyko, A., Kunze, J., Littman, J., Madden, L., Vargas, B. (2009). The BagIt File
Packaging Format (V0.96). Retrieved April 2, 2010, from
r•��ÖÅr¶��}rß��(h!Xâ���Boyko, A., Kunze, J., Littman, J., Madden, L., Vargas, B. (2009). The BagIt File
Packaging Format (V0.96). Retrieved April 2, 2010, from
h"j°��ubjv��)År®��}r©��(h!X<���http://www.ietf.org/Internet-drafts/draft-kunze-bagit-04.txtr™��h1}r´��(Urefurij™��h6]h5]h3]h4]h9]uh"j°��h=]r¨��hFX<���http://www.ietf.org/Internet-drafts/draft-kunze-bagit-04.txtr≠��ÖÅrÆ��}rØ��(h!U�h"j®��ubah/j��ubeubhÜ)År∞��}r±��(h!Xë���DataONE. (2010a). Metadata Attributes for Discovery. Retrieved April 2, 2010,
from http://mule1.dataone.org/ArchitectureDocs/SearchMetadata.html.h"jí��h-h.h/häh1}r≤��(h3]h4]h5]h6]h9]uh;M3h<hh=]r≥��(hFXS���DataONE. (2010a). Metadata Attributes for Discovery. Retrieved April 2, 2010,
from r¥��ÖÅrµ��}r∂��(h!XS���DataONE. (2010a). Metadata Attributes for Discovery. Retrieved April 2, 2010,
from h"j∞��ubjv��)År∑��}r∏��(h!X=���http://mule1.dataone.org/ArchitectureDocs/SearchMetadata.htmlrπ��h1}r∫��(Urefurijπ��h6]h5]h3]h4]h9]uh"j∞��h=]rª��hFX=���http://mule1.dataone.org/ArchitectureDocs/SearchMetadata.htmlrº��ÖÅrΩ��}ræ��(h!U�h"j∑��ubah/j��ubhFX���.ÖÅrø��}r¿��(h!X���.h"j∞��ubeubhÜ)År¡��}r¬��(h!X���DataONE. (2010b). System Metadata. Retrieved April 2, 2010, from
http://mule1.dataone.org/ArchitectureDocs/SystemMetadata.html.h"jí��h-h.h/häh1}r√��(h3]h4]h5]h6]h9]uh;M6h<hh=]rƒ��(hFXA���DataONE. (2010b). System Metadata. Retrieved April 2, 2010, from
r≈��ÖÅr∆��}r«��(h!XA���DataONE. (2010b). System Metadata. Retrieved April 2, 2010, from
h"j¡��ubjv��)År»��}r…��(h!X=���http://mule1.dataone.org/ArchitectureDocs/SystemMetadata.htmlr ��h1}rÀ��(Urefurij ��h6]h5]h3]h4]h9]uh"j¡��h=]rÃ��hFX=���http://mule1.dataone.org/ArchitectureDocs/SystemMetadata.htmlrÕ��ÖÅrŒ��}rœ��(h!U�h"j»��ubah/j��ubhFX���.ÖÅr–��}r—��(h!X���.h"j¡��ubeubhÜ)År“��}r”��(h!XÒ���Lagoze, C., Van de Sompel, H., Johnston, P., Nelson, M., Sanderson, R., Warner,
S. (2008). Open Archives Initiative Object Reuse and Exchange: ORE User Guide -
Primer. Retrieved April 2, 2010, from
http://www.openarchives.org/ore/1.0/primer.h"jí��h-h.h/häh1}r‘��(h3]h4]h5]h6]h9]uh;M9h<hh=]r’��(hFX∆���Lagoze, C., Van de Sompel, H., Johnston, P., Nelson, M., Sanderson, R., Warner,
S. (2008). Open Archives Initiative Object Reuse and Exchange: ORE User Guide -
Primer. Retrieved April 2, 2010, from
r÷��ÖÅr◊��}rÿ��(h!X∆���Lagoze, C., Van de Sompel, H., Johnston, P., Nelson, M., Sanderson, R., Warner,
S. (2008). Open Archives Initiative Object Reuse and Exchange: ORE User Guide -
Primer. Retrieved April 2, 2010, from
h"j“��ubjv��)ÅrŸ��}r⁄��(h!X*���http://www.openarchives.org/ore/1.0/primerr€��h1}r‹��(Urefurij€��h6]h5]h3]h4]h9]uh"j“��h=]r›��hFX*���http://www.openarchives.org/ore/1.0/primerrfi��ÖÅrfl��}r‡��(h!U�h"jŸ��ubah/j��ubhFX���.ÖÅr·��}r‚��(h!X���.h"j“��ubeubhÜ)År„��}r‰��(h!Xº���PREMIS Editorial Committee. (2008). Data Dictionary for Preservation
Metadata: PREMIS version 2.0. S.l. Retrieved April 2, 2010, from
http://www.loc.gov/standards/premis/v2/premis-2-0.pdf.h"jí��h-h.h/häh1}rÂ��(h3]h4]h5]h6]h9]uh;M>h<hh=]rÊ��(hFXÜ���PREMIS Editorial Committee. (2008). Data Dictionary for Preservation
Metadata: PREMIS version 2.0. S.l. Retrieved April 2, 2010, from
rÁ��ÖÅrË��}rÈ��(h!XÜ���PREMIS Editorial Committee. (2008). Data Dictionary for Preservation
Metadata: PREMIS version 2.0. S.l. Retrieved April 2, 2010, from
h"j„��ubjv��)ÅrÍ��}rÎ��(h!X5���http://www.loc.gov/standards/premis/v2/premis-2-0.pdfrÏ��h1}rÌ��(UrefurijÏ��h6]h5]h3]h4]h9]uh"j„��h=]rÓ��hFX5���http://www.loc.gov/standards/premis/v2/premis-2-0.pdfrÔ��ÖÅr��}rÒ��(h!U�h"jÍ��ubah/j��ubhFX���.ÖÅrÚ��}rÛ��(h!X���.h"j„��ubeubeubeubh-h.h/h0h1}rÙ��(h3]h4]h5]h6]rı��Usystem-metadata-requirementsrˆ��ah9]r˜��hauh;Ksh<hh=]r¯��(h?)År˘��}r˙��(h!X���System Metadata Requirementsr˚��h"h)h-h.h/hCh1}r¸��(h3]h4]h5]h6]h9]uh;Ksh<hh=]r˝��hFX���System Metadata Requirementsr˛��ÖÅrˇ��}r���(h!j˚��h"j˘��ubaubhÜ)År��}r��(h!X.��For each of the high-level requirements identified, the relevant sections of the
PREMIS data dictionary were identified, and missing, additional, mismatched
aspects are identified in the text. The documentation for BagIt and OAI-ORE were
consulted and their relevance to the requirement is also discussed in the text.
Optionally, use cases relevant to the requirement are described, using science
data specified in EML, Dryad, ORNL DAAC, and/or NBII formats as examples. The
section on each requirement ends with a general discussion of the overall
analysis.r��h"h)h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;Kuh<hh=]r��hFX.��For each of the high-level requirements identified, the relevant sections of the
PREMIS data dictionary were identified, and missing, additional, mismatched
aspects are identified in the text. The documentation for BagIt and OAI-ORE were
consulted and their relevance to the requirement is also discussed in the text.
Optionally, use cases relevant to the requirement are described, using science
data specified in EML, Dryad, ORNL DAAC, and/or NBII formats as examples. The
section on each requirement ends with a general discussion of the overall
analysis.r��ÖÅr��}r��(h!j��h"j��ubaubh#)År	��}r
��(h!U�h"h)h-h.h/h0h1}r��(h3]h4]h5]h6]r��U4requirement-1-perform-replication-on-digital-objectsr
��ah9]r��h	auh;Kh<hh=]r��(h?)År��}r��(h!X5���Requirement 1: Perform replication on digital objectsr��h"j	��h-h.h/hCh1}r��(h3]h4]h5]h6]h9]uh;Kh<hh=]r��hFX5���Requirement 1: Perform replication on digital objectsr��ÖÅr��}r��(h!j��h"j��ubaubh#)År��}r��(h!U�h&Kh"j	��h-h.h/h0h1}r��(h3]r��X���descriptionr��ah4]h5]h6]r��Udescriptionr��ah9]uh;KÇh<hh=]r��(h?)År ��}r!��(h!X���Descriptionr"��h"j��h-h.h/hCh1}r#��(h3]h4]h5]h6]h9]uh;KÇh<hh=]r$��hFX���Descriptionr%��ÖÅr&��}r'��(h!j"��h"j ��ubaubhÜ)År(��}r)��(h!XA��To increase accessibility and help ensure long-term preservation, the
Coordinating Nodes will perform replications on digital objects. Systems
metadata will be replicated at each of the three Coordinating Nodes, while
datasets and their associated descriptive metadata will be replicated at a
minimum of two Member Nodes.r*��h"j��h-h.h/häh1}r+��(h3]h4]h5]h6]h9]uh;KÑh<hh=]r,��hFXA��To increase accessibility and help ensure long-term preservation, the
Coordinating Nodes will perform replications on digital objects. Systems
metadata will be replicated at each of the three Coordinating Nodes, while
datasets and their associated descriptive metadata will be replicated at a
minimum of two Member Nodes.r-��ÖÅr.��}r/��(h!j*��h"j(��ubaubeubh#)År0��}r1��(h!U�h&Kh"j	��h-h.h/h0h1}r2��(h3]r3��X���what premis suggestsr4��ah4]h5]h6]r5��Uwhat-premis-suggestsr6��ah9]uh;Kãh<hh=]r7��(h?)År8��}r9��(h!X���What PREMIS suggestsr:��h"j0��h-h.h/hCh1}r;��(h3]h4]h5]h6]h9]uh;Kãh<hh=]r<��hFX���What PREMIS suggestsr=��ÖÅr>��}r?��(h!j:��h"j8��ubaubhÜ)År@��}rA��(h!XÄ��When a replication is performed, the DataONE system will need to record which
object was replicated (1.1), the unique identifier of the new copy (1.1), where
the replicate is stored in the system (1.7), information on the derivative
relationship between the original object and the new one (1.10) [in PREMIS,
replication of an object is defined as one type of a derivation relationship;
see p.13], and information on the event that created the replicate such as the
unique identifier of the event (2.1), type = replication (2.2), time (2.3), who
performed the replication (2.6), and a link between the replicated object and
the event (2.7).rB��h"j0��h-h.h/häh1}rC��(h3]h4]h5]h6]h9]uh;Kçh<hh=]rD��hFXÄ��When a replication is performed, the DataONE system will need to record which
object was replicated (1.1), the unique identifier of the new copy (1.1), where
the replicate is stored in the system (1.7), information on the derivative
relationship between the original object and the new one (1.10) [in PREMIS,
replication of an object is defined as one type of a derivation relationship;
see p.13], and information on the event that created the replicate such as the
unique identifier of the event (2.1), type = replication (2.2), time (2.3), who
performed the replication (2.6), and a link between the replicated object and
the event (2.7).rE��ÖÅrF��}rG��(h!jB��h"j@��ubaubeubh#)ÅrH��}rI��(h!U�h&Kh"j	��h-h.h/h0h1}rJ��(h3]rK��X���what bagit and oai-ore providerL��ah4]h5]h6]rM��Uwhat-bagit-and-oai-ore-providerN��ah9]uh;Kòh<hh=]rO��h?)ÅrP��}rQ��(h!X���What BagIt and OAI-ORE providerR��h"jH��h-h.h/hCh1}rS��(h3]h4]h5]h6]h9]uh;Kòh<hh=]rT��hFX���What BagIt and OAI-ORE providerU��ÖÅrV��}rW��(h!jR��h"jP��ubaubaubh#)ÅrX��}rY��(h!U�h&Kh"j	��h-h.h/h0h1}rZ��(h3]r[��X"���dataone use cases and requirementsr\��ah4]h5]h6]r]��U"dataone-use-cases-and-requirementsr^��ah9]uh;Kõh<hh=]r_��(h?)År`��}ra��(h!X"���DataONE use cases and requirementsrb��h"jX��h-h.h/hCh1}rc��(h3]h4]h5]h6]h9]uh;Kõh<hh=]rd��hFX"���DataONE use cases and requirementsre��ÖÅrf��}rg��(h!jb��h"j`��ubaubhÜ)Årh��}ri��(h!XN���(Requirement) System supports data storage https://trac.dataone.org/ticket/383rj��h"jX��h-h.h/häh1}rk��(h3]h4]h5]h6]h9]uh;Kùh<hh=]rl��(hFX+���(Requirement) System supports data storage rm��ÖÅrn��}ro��(h!X+���(Requirement) System supports data storage h"jh��ubjv��)Årp��}rq��(h!X#���https://trac.dataone.org/ticket/383rr��h1}rs��(Urefurijr��h6]h5]h3]h4]h9]uh"jh��h=]rt��hFX#���https://trac.dataone.org/ticket/383ru��ÖÅrv��}rw��(h!U�h"jp��ubah/j��ubeubhÜ)Årx��}ry��(h!X���(Requirement) The infrastructure must survive destruction of one or more data
storage nodes https://trac.dataone.org/ticket/411h"jX��h-h.h/häh1}rz��(h3]h4]h5]h6]h9]uh;Küh<hh=]r{��(hFX\���(Requirement) The infrastructure must survive destruction of one or more data
storage nodes r|��ÖÅr}��}r~��(h!X\���(Requirement) The infrastructure must survive destruction of one or more data
storage nodes h"jx��ubjv��)År��}rÄ��(h!X#���https://trac.dataone.org/ticket/411rÅ��h1}rÇ��(UrefurijÅ��h6]h5]h3]h4]h9]uh"jx��h=]rÉ��hFX#���https://trac.dataone.org/ticket/411rÑ��ÖÅrÖ��}rÜ��(h!U�h"j��ubah/j��ubeubhÜ)Årá��}rà��(h!Xs���(Requirement) Data and metadata is replicated to at least one other Member Node
https://trac.dataone.org/ticket/433h"jX��h-h.h/häh1}râ��(h3]h4]h5]h6]h9]uh;K¢h<hh=]rä��(hFXP���(Requirement) Data and metadata is replicated to at least one other Member Node
rã��ÖÅrå��}rç��(h!XP���(Requirement) Data and metadata is replicated to at least one other Member Node
h"já��ubjv��)Åré��}rè��(h!X#���https://trac.dataone.org/ticket/433rê��h1}rë��(Urefurijê��h6]h5]h3]h4]h9]uh"já��h=]rí��hFX#���https://trac.dataone.org/ticket/433rì��ÖÅrî��}rï��(h!U�h"jé��ubah/j��ubeubeubh#)Årñ��}ró��(h!U�h&Kh"j	��h-h.h/h0h1}rò��(h3]rô��X
���discussionrö��ah4]h5]h6]rõ��U
discussionrú��ah9]uh;K¶h<hh=]rù��h?)Årû��}rü��(h!X
���Discussionr†��h"jñ��h-h.h/hCh1}r°��(h3]h4]h5]h6]h9]uh;K¶h<hh=]r¢��hFX
���Discussionr£��ÖÅr§��}r•��(h!j†��h"jû��ubaubaubeubh'h#)År¶��}rß��(h!U�h"h)h-h.h/h0h1}r®��(h3]h4]h5]h6]r©��UDrequirement-3-record-specific-types-of-relationships-between-objectsr™��ah9]r´��hauh;K›h<hh=]r¨��(h?)År≠��}rÆ��(h!XE���Requirement 3: Record specific types of relationships between objectsrØ��h"j¶��h-h.h/hCh1}r∞��(h3]h4]h5]h6]h9]uh;K›h<hh=]r±��hFXE���Requirement 3: Record specific types of relationships between objectsr≤��ÖÅr≥��}r¥��(h!jØ��h"j≠��ubaubh#)Årµ��}r∂��(h!U�h&Kh"j¶��h-h.h/h0h1}r∑��(h3]r∏��X���descriptionrπ��ah4]h5]h6]r∫��Uid6rª��ah9]uh;K‡h<hh=]rº��h?)ÅrΩ��}ræ��(h!X���Descriptionrø��h"jµ��h-h.h/hCh1}r¿��(h3]h4]h5]h6]h9]uh;K‡h<hh=]r¡��hFX���Descriptionr¬��ÖÅr√��}rƒ��(h!jø��h"jΩ��ubaubaubh#)År≈��}r∆��(h!U�h&Kh"j¶��h-h.h/h0h1}r«��(h3]r»��X���what premis suggestsr…��ah4]h5]h6]r ��Uid7rÀ��ah9]uh;K‰h<hh=]rÃ��(h?)ÅrÕ��}rŒ��(h!X���What PREMIS suggestsrœ��h"j≈��h-h.h/hCh1}r–��(h3]h4]h5]h6]h9]uh;K‰h<hh=]r—��hFX���What PREMIS suggestsr“��ÖÅr”��}r‘��(h!jœ��h"jÕ��ubaubhÜ)År’��}r÷��(h!X¬��PREMIS suggest the system record as semantic units to define structural,
derivaton and dependency relationships. For structural relationships, which
"show relationships between parts of objects" (p.13), characterizations of these
relationship types are recorded with a description of the relationship type,
such as "structural" (1.10.1), relationship sub-type such as "is a part of"
(1.10.2), and the unique identifier of the related object (1.10.3).r◊��h"j≈��h-h.h/häh1}rÿ��(h3]h4]h5]h6]h9]uh;KÊh<hh=]rŸ��hFX¬��PREMIS suggest the system record as semantic units to define structural,
derivaton and dependency relationships. For structural relationships, which
"show relationships between parts of objects" (p.13), characterizations of these
relationship types are recorded with a description of the relationship type,
such as "structural" (1.10.1), relationship sub-type such as "is a part of"
(1.10.2), and the unique identifier of the related object (1.10.3).r⁄��ÖÅr€��}r‹��(h!j◊��h"j’��ubaubhÜ)År›��}rfi��(h!Xœ���Derivative relationships "result from the replication or transformation of an
object" (p.13). Because this type of relationship involves an event, the system
must record the unique event identifier (1.10.4).rfl��h"j≈��h-h.h/häh1}r‡��(h3]h4]h5]h6]h9]uh;KÌh<hh=]r·��hFXœ���Derivative relationships "result from the replication or transformation of an
object" (p.13). Because this type of relationship involves an event, the system
must record the unique event identifier (1.10.4).r‚��ÖÅr„��}r‰��(h!jfl��h"j›��ubaubhÜ)ÅrÂ��}rÊ��(h!Xw��Dependency relationships exist "when one object requires another to support its
functino,m delivery, or coherence of content". Examples include a data type
definition needed to render another file or modules needed by a software program
that is required to render an object. These relationships are characterized in
1.8.4 "dependency" and 1.8.5.5 "swDependency" respectively.rÁ��h"j≈��h-h.h/häh1}rË��(h3]h4]h5]h6]h9]uh;KÒh<hh=]rÈ��hFXw��Dependency relationships exist "when one object requires another to support its
functino,m delivery, or coherence of content". Examples include a data type
definition needed to render another file or modules needed by a software program
that is required to render an object. These relationships are characterized in
1.8.4 "dependency" and 1.8.5.5 "swDependency" respectively.rÍ��ÖÅrÎ��}rÏ��(h!jÁ��h"jÂ��ubaubeubh#)ÅrÌ��}rÓ��(h!U�h&Kh"j¶��h-h.h/h0h1}rÔ��(h3]r��X���what bagit and oai-ore providerÒ��ah4]h5]h6]rÚ��Uid8rÛ��ah9]uh;K¯h<hh=]rÙ��h?)Årı��}rˆ��(h!X���What BagIt and OAI-ORE provider˜��h"jÌ��h-h.h/hCh1}r¯��(h3]h4]h5]h6]h9]uh;K¯h<hh=]r˘��hFX���What BagIt and OAI-ORE provider˙��ÖÅr˚��}r¸��(h!j˜��h"jı��ubaubaubh#)År˝��}r˛��(h!U�h&Kh"j¶��h-h.h/h0h1}rˇ��(h3]r���X"���dataone use cases and requirementsr��ah4]h5]h6]r��Uid9r��ah9]uh;K˚h<hh=]r��(h?)År��}r��(h!X"���DataONE use cases and requirementsr��h"j˝��h-h.h/hCh1}r��(h3]h4]h5]h6]h9]uh;K˚h<hh=]r	��hFX"���DataONE use cases and requirementsr
��ÖÅr��}r��(h!j��h"j��ubaubhÜ)År
��}r��(h!XM���(Requirement) Identifiers for all objects https://trac.dataone.org/ticket/317r��h"j˝��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;K˝h<hh=]r��(hFX*���(Requirement) Identifiers for all objects r��ÖÅr��}r��(h!X*���(Requirement) Identifiers for all objects h"j
��ubjv��)År��}r��(h!X#���https://trac.dataone.org/ticket/317r��h1}r��(Urefurij��h6]h5]h3]h4]h9]uh"j
��h=]r��hFX#���https://trac.dataone.org/ticket/317r��ÖÅr��}r��(h!U�h"j��ubah/j��ubeubhÜ)År��}r��(h!XV���(Requirement) Support arbitrary unique identifiers
https://trac.dataone.org/ticket/385h"j˝��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;Kˇh<hh=]r ��(hFX3���(Requirement) Support arbitrary unique identifiers
r!��ÖÅr"��}r#��(h!X3���(Requirement) Support arbitrary unique identifiers
h"j��ubjv��)År$��}r%��(h!X#���https://trac.dataone.org/ticket/385r&��h1}r'��(Urefurij&��h6]h5]h3]h4]h9]uh"j��h=]r(��hFX#���https://trac.dataone.org/ticket/385r)��ÖÅr*��}r+��(h!U�h"j$��ubah/j��ubeubhÜ)År,��}r-��(h!X]���(Requirement) Identifiers always refer to the same object
https://trac.dataone.org/ticket/412h"j˝��h-h.h/häh1}r.��(h3]h4]h5]h6]h9]uh;Mh<hh=]r/��(hFX:���(Requirement) Identifiers always refer to the same object
r0��ÖÅr1��}r2��(h!X:���(Requirement) Identifiers always refer to the same object
h"j,��ubjv��)År3��}r4��(h!X#���https://trac.dataone.org/ticket/412r5��h1}r6��(Urefurij5��h6]h5]h3]h4]h9]uh"j,��h=]r7��hFX#���https://trac.dataone.org/ticket/412r8��ÖÅr9��}r:��(h!U�h"j3��ubah/j��ubeubeubh#)År;��}r<��(h!U�h&Kh"j¶��h-h.h/h0h1}r=��(h3]r>��X
���discussionr?��ah4]h5]h6]r@��Uid10rA��ah9]uh;Mh<hh=]rB��h?)ÅrC��}rD��(h!X
���DiscussionrE��h"j;��h-h.h/hCh1}rF��(h3]h4]h5]h6]h9]uh;Mh<hh=]rG��hFX
���DiscussionrH��ÖÅrI��}rJ��(h!jE��h"jC��ubaubaubeubh#)ÅrK��}rL��(h!U�h"h)h-h.h/h0h1}rM��(h3]h4]h5]h6]rN��U.requirement-4-support-digital-object-discoveryrO��ah9]rP��hauh;Mh<hh=]rQ��(h?)ÅrR��}rS��(h!X/���Requirement 4: Support digital object discoveryrT��h"jK��h-h.h/hCh1}rU��(h3]h4]h5]h6]h9]uh;Mh<hh=]rV��hFX/���Requirement 4: Support digital object discoveryrW��ÖÅrX��}rY��(h!jT��h"jR��ubaubh#)ÅrZ��}r[��(h!U�h&Kh"jK��h-h.h/h0h1}r\��(h3]r]��X���descriptionr^��ah4]h5]h6]r_��Uid11r`��ah9]uh;Mh<hh=]ra��(h?)Årb��}rc��(h!X���Descriptionrd��h"jZ��h-h.h/hCh1}re��(h3]h4]h5]h6]h9]uh;Mh<hh=]rf��hFX���Descriptionrg��ÖÅrh��}ri��(h!jd��h"jb��ubaubhÜ)Årj��}rk��(h!X„���Digital object discovery by DataONE users is supported primarily by the
descriptive metadata associated with data objects ingested into DataONE. The
DataONE design refers to this metadata as "science metadata" (DataONE, 2010a).rl��h"jZ��h-h.h/häh1}rm��(h3]h4]h5]h6]h9]uh;Mh<hh=]rn��hFX„���Digital object discovery by DataONE users is supported primarily by the
descriptive metadata associated with data objects ingested into DataONE. The
DataONE design refers to this metadata as "science metadata" (DataONE, 2010a).ro��ÖÅrp��}rq��(h!jl��h"jj��ubaubhÜ)Årr��}rs��(h!X��Other digital object scenarios should also be considered. For example, when
managing digital objects for long-term curation and stewardship, DataONE
personnel and processes may use the system metadata (DataONE, 2010b) as the
means for digital object discovery.rt��h"jZ��h-h.h/häh1}ru��(h3]h4]h5]h6]h9]uh;Mh<hh=]rv��hFX��Other digital object scenarios should also be considered. For example, when
managing digital objects for long-term curation and stewardship, DataONE
personnel and processes may use the system metadata (DataONE, 2010b) as the
means for digital object discovery.rw��ÖÅrx��}ry��(h!jt��h"jr��ubaubeubh#)Årz��}r{��(h!U�h&Kh"jK��h-h.h/h0h1}r|��(h3]r}��X���what premis suggestsr~��ah4]h5]h6]r��Uid12rÄ��ah9]uh;Mh<hh=]rÅ��(h?)ÅrÇ��}rÉ��(h!X���What PREMIS suggestsrÑ��h"jz��h-h.h/hCh1}rÖ��(h3]h4]h5]h6]h9]uh;Mh<hh=]rÜ��hFX���What PREMIS suggestsrá��ÖÅrà��}râ��(h!jÑ��h"jÇ��ubaubhÜ)Årä��}rã��(h!Xø���PREMIS defines descriptive metadata as "...metadata ... used to describe
Intellectual Entities" (p.23), and assumes that which in DataONE maps to the
science metadata submitted to the system.rå��h"jz��h-h.h/häh1}rç��(h3]h4]h5]h6]h9]uh;Mh<hh=]ré��hFXø���PREMIS defines descriptive metadata as "...metadata ... used to describe
Intellectual Entities" (p.23), and assumes that which in DataONE maps to the
science metadata submitted to the system.rè��ÖÅrê��}rë��(h!jå��h"jä��ubaubeubh#)Årí��}rì��(h!U�h&Kh"jK��h-h.h/h0h1}rî��(h3]rï��X���what bagit and oai-ore providerñ��ah4]h5]h6]ró��Uid13rò��ah9]uh;M"h<hh=]rô��h?)Årö��}rõ��(h!X���What BagIt and OAI-ORE providerú��h"jí��h-h.h/hCh1}rù��(h3]h4]h5]h6]h9]uh;M"h<hh=]rû��hFX���What BagIt and OAI-ORE providerü��ÖÅr†��}r°��(h!jú��h"jö��ubaubaubh#)År¢��}r£��(h!U�h&Kh"jK��h-h.h/h0h1}r§��(h3]r•��X"���dataone use cases and requirementsr¶��ah4]h5]h6]rß��Uid14r®��ah9]uh;M%h<hh=]r©��(h?)År™��}r´��(h!X"���DataONE use cases and requirementsr¨��h"j¢��h-h.h/hCh1}r≠��(h3]h4]h5]h6]h9]uh;M%h<hh=]rÆ��hFX"���DataONE use cases and requirementsrØ��ÖÅr∞��}r±��(h!j¨��h"j™��ubaubhÜ)År≤��}r≥��(h!Xe���DataONE Use Case 33 - Search for Data
(http://mule1.dataone.org/ArchitectureDocs/UseCases/33_uc.html)h"j¢��h-h.h/häh1}r¥��(h3]h4]h5]h6]h9]uh;M'h<hh=]rµ��(hFX'���DataONE Use Case 33 - Search for Data
(r∂��ÖÅr∑��}r∏��(h!X'���DataONE Use Case 33 - Search for Data
(h"j≤��ubjv��)Årπ��}r∫��(h!X=���http://mule1.dataone.org/ArchitectureDocs/UseCases/33_uc.htmlrª��h1}rº��(Urefurijª��h6]h5]h3]h4]h9]uh"j≤��h=]rΩ��hFX=���http://mule1.dataone.org/ArchitectureDocs/UseCases/33_uc.htmlræ��ÖÅrø��}r¿��(h!U�h"jπ��ubah/j��ubhFX���)ÖÅr¡��}r¬��(h!X���)h"j≤��ubeubhÜ)År√��}rƒ��(h!Xk���(Requirement) Enable efficient mechanisms for users to discover content
https://trac.dataone.org/ticket/384h"j¢��h-h.h/häh1}r≈��(h3]h4]h5]h6]h9]uh;M*h<hh=]r∆��(hFXH���(Requirement) Enable efficient mechanisms for users to discover content
r«��ÖÅr»��}r…��(h!XH���(Requirement) Enable efficient mechanisms for users to discover content
h"j√��ubjv��)År ��}rÀ��(h!X#���https://trac.dataone.org/ticket/384rÃ��h1}rÕ��(UrefurijÃ��h6]h5]h3]h4]h9]uh"j√��h=]rŒ��hFX#���https://trac.dataone.org/ticket/384rœ��ÖÅr–��}r—��(h!U�h"j ��ubah/j��ubeubeubh#)År“��}r”��(h!U�h&Kh"jK��h-h.h/h0h1}r‘��(h3]r’��X
���discussionr÷��ah4]h5]h6]r◊��Uid15rÿ��ah9]uh;M.h<hh=]rŸ��h?)År⁄��}r€��(h!X
���Discussionr‹��h"j“��h-h.h/hCh1}r›��(h3]h4]h5]h6]h9]uh;M.h<hh=]rfi��hFX
���Discussionrfl��ÖÅr‡��}r·��(h!j‹��h"j⁄��ubaubaubeubh#)År‚��}r„��(h!U�h"h)h-h.h/h0h1}r‰��(h3]h4]h5]h6]rÂ��U+requirement-5-support-digital-object-re-userÊ��ah9]rÁ��hauh;M2h<hh=]rË��(h?)ÅrÈ��}rÍ��(h!X,���Requirement 5: Support digital object re-userÎ��h"j‚��h-h.h/hCh1}rÏ��(h3]h4]h5]h6]h9]uh;M2h<hh=]rÌ��hFX,���Requirement 5: Support digital object re-userÓ��ÖÅrÔ��}r��(h!jÎ��h"jÈ��ubaubh#)ÅrÒ��}rÚ��(h!U�h&Kh"j‚��h-h.h/h0h1}rÛ��(h3]rÙ��X���descriptionrı��ah4]h5]h6]rˆ��Uid16r˜��ah9]uh;M5h<hh=]r¯��(h?)År˘��}r˙��(h!X���Descriptionr˚��h"jÒ��h-h.h/hCh1}r¸��(h3]h4]h5]h6]h9]uh;M5h<hh=]r˝��hFX���Descriptionr˛��ÖÅrˇ��}r���(h!j˚��h"j˘��ubaubhÜ)År��}r��(h!Xw���Relationships , entities , citation, life science identifiers [exchange of
digital objects between repositories? METS?]r��h"jÒ��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;M7h<hh=]r��hFXw���Relationships , entities , citation, life science identifiers [exchange of
digital objects between repositories? METS?]r��ÖÅr��}r��(h!j��h"j��ubaubeubh#)År	��}r
��(h!U�h&Kh"j‚��h-h.h/h0h1}r��(h3]r��X���what premis suggestsr
��ah4]h5]h6]r��Uid17r��ah9]uh;M<h<hh=]r��(h?)År��}r��(h!X���What PREMIS suggestsr��h"j	��h-h.h/hCh1}r��(h3]h4]h5]h6]h9]uh;M<h<hh=]r��hFX���What PREMIS suggestsr��ÖÅr��}r��(h!j��h"j��ubaubhÜ)År��}r��(h!XÔ��Potential users of digital objects need to know of any structural, derivative,
and dependency relationships properties in order to re-use an object. For
example, databases are often stored in repsotiories as two files: one for
content and oen for the schema. The user needs to access both files to re-use
the databse. The suggested PREMIS semantic units for relationships are described
under general requirement 3. Citation and persistent identifiers, such as LSIDs,
are not addressed in PREMIS.r��h"j	��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;M>h<hh=]r��hFXÔ��Potential users of digital objects need to know of any structural, derivative,
and dependency relationships properties in order to re-use an object. For
example, databases are often stored in repsotiories as two files: one for
content and oen for the schema. The user needs to access both files to re-use
the databse. The suggested PREMIS semantic units for relationships are described
under general requirement 3. Citation and persistent identifiers, such as LSIDs,
are not addressed in PREMIS.r��ÖÅr��}r ��(h!j��h"j��ubaubeubh#)År!��}r"��(h!U�h&Kh"j‚��h-h.h/h0h1}r#��(h3]r$��X���what bagit and oai-ore provider%��ah4]h5]h6]r&��Uid18r'��ah9]uh;MGh<hh=]r(��h?)År)��}r*��(h!X���What BagIt and OAI-ORE provider+��h"j!��h-h.h/hCh1}r,��(h3]h4]h5]h6]h9]uh;MGh<hh=]r-��hFX���What BagIt and OAI-ORE provider.��ÖÅr/��}r0��(h!j+��h"j)��ubaubaubh#)År1��}r2��(h!U�h&Kh"j‚��h-h.h/h0h1}r3��(h3]r4��X"���dataone use cases and requirementsr5��ah4]h5]h6]r6��Uid19r7��ah9]uh;MJh<hh=]r8��(h?)År9��}r:��(h!X"���DataONE use cases and requirementsr;��h"j1��h-h.h/hCh1}r<��(h3]h4]h5]h6]h9]uh;MJh<hh=]r=��hFX"���DataONE use cases and requirementsr>��ÖÅr?��}r@��(h!j;��h"j9��ubaubhÜ)ÅrA��}rB��(h!Xk���(Requirement) Enable efficient mechanisms for users to discover content
https://trac.dataone.org/ticket/384h"j1��h-h.h/häh1}rC��(h3]h4]h5]h6]h9]uh;MLh<hh=]rD��(hFXH���(Requirement) Enable efficient mechanisms for users to discover content
rE��ÖÅrF��}rG��(h!XH���(Requirement) Enable efficient mechanisms for users to discover content
h"jA��ubjv��)ÅrH��}rI��(h!X#���https://trac.dataone.org/ticket/384rJ��h1}rK��(UrefurijJ��h6]h5]h3]h4]h9]uh"jA��h=]rL��hFX#���https://trac.dataone.org/ticket/384rM��ÖÅrN��}rO��(h!U�h"jH��ubah/j��ubeubeubeubeubh-h.h/h0h1}rP��(h3]h4]h5]h6]rQ��U,requirement-2-perform-preservation-migrationrR��ah9]rS��hauh;K™h<hh=]rT��(h?)ÅrU��}rV��(h!X-���Requirement 2: Perform preservation migrationrW��h"h'h-h.h/hCh1}rX��(h3]h4]h5]h6]h9]uh;K™h<hh=]rY��hFX-���Requirement 2: Perform preservation migrationrZ��ÖÅr[��}r\��(h!jW��h"jU��ubaubh$h#)År]��}r^��(h!U�h&Kh"h'h-h.h/h0h1}r_��(h3]r`��j4��ah4]h5]h6]ra��Uid2rb��ah9]uh;K∂h<hh=]rc��(h?)Ård��}re��(h!X���What PREMIS suggestsrf��h"j]��h-h.h/hCh1}rg��(h3]h4]h5]h6]h9]uh;K∂h<hh=]rh��hFX���What PREMIS suggestsri��ÖÅrj��}rk��(h!jf��h"jd��ubaubhÜ)Årl��}rm��(h!X˙��Prior to migrating an object to a different format the system must first know
the following information: current format name and version (1.5.4.1.1 and
1.5.4.1.2, respectively), assurance that the file to be migrated is not
corrupted (1.5.2 fixity), which alternative format is the best possible format
to migrate the file to given the hardware and software requirements (refer to a
digital format registry?), and name and version of application that created the
object (1.5.5.1 and 1.5.5.2, respectively).rn��h"j]��h-h.h/häh1}ro��(h3]h4]h5]h6]h9]uh;K∏h<hh=]rp��hFX˙��Prior to migrating an object to a different format the system must first know
the following information: current format name and version (1.5.4.1.1 and
1.5.4.1.2, respectively), assurance that the file to be migrated is not
corrupted (1.5.2 fixity), which alternative format is the best possible format
to migrate the file to given the hardware and software requirements (refer to a
digital format registry?), and name and version of application that created the
object (1.5.5.1 and 1.5.5.2, respectively).rq��ÖÅrr��}rs��(h!jn��h"jl��ubaubhÜ)Årt��}ru��(h!Xb��When performing a migration due to format obsolescence, the DataONE system will
need to record the following metadata: which object is being replicated (1.1),
what is the unique identifier of the new object (1.1), where in the system is
the new object stored (1.7), information on the derivative relationship between
the original object and the new one (1.10). Also, it needs to record metadata on
the event that created the newly migrated object such as unique identifier
(2.1), type = migration (2.2), time (2.3), who performed the migration (2.6),
and a link between the migrated object and the event (2.7).rv��h"j]��h-h.h/häh1}rw��(h3]h4]h5]h6]h9]uh;K¿h<hh=]rx��hFXb��When performing a migration due to format obsolescence, the DataONE system will
need to record the following metadata: which object is being replicated (1.1),
what is the unique identifier of the new object (1.1), where in the system is
the new object stored (1.7), information on the derivative relationship between
the original object and the new one (1.10). Also, it needs to record metadata on
the event that created the newly migrated object such as unique identifier
(2.1), type = migration (2.2), time (2.3), who performed the migration (2.6),
and a link between the migrated object and the event (2.7).ry��ÖÅrz��}r{��(h!jv��h"jt��ubaubhÜ)År|��}r}��(h!Xà���When migration for physical media obsolescence occurs, the system should record
where the object is now located (1.7.1 contentLocation).r~��h"j]��h-h.h/häh1}r��(h3]h4]h5]h6]h9]uh;K…h<hh=]rÄ��hFXà���When migration for physical media obsolescence occurs, the system should record
where the object is now located (1.7.1 contentLocation).rÅ��ÖÅrÇ��}rÉ��(h!j~��h"j|��ubaubeubh#)ÅrÑ��}rÖ��(h!U�h&Kh"h'h-h.h/h0h1}rÜ��(h3]rá��jL��ah4]h5]h6]rà��Uid3râ��ah9]uh;KÕh<hh=]rä��h?)Årã��}rå��(h!X���What BagIt and OAI-ORE providerç��h"jÑ��h-h.h/hCh1}ré��(h3]h4]h5]h6]h9]uh;KÕh<hh=]rè��hFX���What BagIt and OAI-ORE providerê��ÖÅrë��}rí��(h!jç��h"jã��ubaubaubh#)Årì��}rî��(h!U�h&Kh"h'h-h.h/h0h1}rï��(h3]rñ��j\��ah4]h5]h6]ró��Uid4rò��ah9]uh;K–h<hh=]rô��(h?)Årö��}rõ��(h!X"���DataONE use cases and requirementsrú��h"jì��h-h.h/hCh1}rù��(h3]h4]h5]h6]h9]uh;K–h<hh=]rû��hFX"���DataONE use cases and requirementsrü��ÖÅr†��}r°��(h!jú��h"jö��ubaubhÜ)År¢��}r£��(h!Xp���(Requirement) The infrastructure must support long term preservation of data
https://trac.dataone.org/ticket/410h"jì��h-h.h/häh1}r§��(h3]h4]h5]h6]h9]uh;K“h<hh=]r•��(hFXM���(Requirement) The infrastructure must support long term preservation of data
r¶��ÖÅrß��}r®��(h!XM���(Requirement) The infrastructure must support long term preservation of data
h"j¢��ubjv��)År©��}r™��(h!X#���https://trac.dataone.org/ticket/410r´��h1}r¨��(Urefurij´��h6]h5]h3]h4]h9]uh"j¢��h=]r≠��hFX#���https://trac.dataone.org/ticket/410rÆ��ÖÅrØ��}r∞��(h!U�h"j©��ubah/j��ubeubhÜ)År±��}r≤��(h!Xb���(Requirement) Maintain original copies of all science metadata
https://trac.dataone.org/ticket/439h"jì��h-h.h/häh1}r≥��(h3]h4]h5]h6]h9]uh;K’h<hh=]r¥��(hFX?���(Requirement) Maintain original copies of all science metadata
rµ��ÖÅr∂��}r∑��(h!X?���(Requirement) Maintain original copies of all science metadata
h"j±��ubjv��)År∏��}rπ��(h!X#���https://trac.dataone.org/ticket/439r∫��h1}rª��(Urefurij∫��h6]h5]h3]h4]h9]uh"j±��h=]rº��hFX#���https://trac.dataone.org/ticket/439rΩ��ÖÅræ��}rø��(h!U�h"j∏��ubah/j��ubeubeubh#)År¿��}r¡��(h!U�h&Kh"h'h-h.h/h0h1}r¬��(h3]r√��jö��ah4]h5]h6]rƒ��Uid5r≈��ah9]uh;KŸh<hh=]r∆��h?)År«��}r»��(h!X
���Discussionr…��h"j¿��h-h.h/hCh1}r ��(h3]h4]h5]h6]h9]uh;KŸh<hh=]rÀ��hFX
���DiscussionrÃ��ÖÅrÕ��}rŒ��(h!j…��h"j«��ubaubaubeubh-h.h/h0h1}rœ��(h3]r–��j��ah4]h5]h6]r—��Uid1r“��ah9]uh;KÆh<hh=]r”��(h?)År‘��}r’��(h!X���Descriptionr÷��h"h$h-h.h/hCh1}r◊��(h3]h4]h5]h6]h9]uh;KÆh<hh=]rÿ��hFX���DescriptionrŸ��ÖÅr⁄��}r€��(h!j÷��h"j‘��ubaubhÜ)År‹��}r›��(h!X)��Migration is one kind of preservation strategy that Coordinating Nodes may
choose to use when a particular format of an object is in danger of
obsolescence. Also, through time, the physical media the digital objects are
stored on will degrade and an object will need to be migrated to a new media.rfi��h"h$h-h.h/häh1}rfl��(h3]h4]h5]h6]h9]uh;K∞h<hh=]r‡��hFX)��Migration is one kind of preservation strategy that Coordinating Nodes may
choose to use when a particular format of an object is in danger of
obsolescence. Also, through time, the physical media the digital objects are
stored on will degrade and an object will need to be migrated to a new media.r·��ÖÅr‚��}r„��(h!jfi��h"j‹��ubaubeubh-h.h/Usystem_messager‰��h1}rÂ��(h3]UlevelKh6]h5]rÊ��j“��aUsourceh.h4]h9]UlineKÆUtypeUINFOrÁ��uh;KÆh<hh=]rË��hÜ)ÅrÈ��}rÍ��(h!X.���Duplicate implicit target name: "description".h1}rÎ��(h3]h4]h5]h6]h9]uh"hh=]rÏ��hFX.���Duplicate implicit target name: "description".rÌ��ÖÅrÓ��}rÔ��(h!U�h"jÈ��ubah/häubaubh)År��}rÒ��(h!U�h"j]��h-h.h/j‰��h1}rÚ��(h3]UlevelKh6]h5]rÛ��jb��aUsourceh.h4]h9]UlineK∂UtypejÁ��uh;K∂h<hh=]rÙ��hÜ)Årı��}rˆ��(h!X7���Duplicate implicit target name: "what premis suggests".h1}r˜��(h3]h4]h5]h6]h9]uh"j��h=]r¯��hFX7���Duplicate implicit target name: "what premis suggests".r˘��ÖÅr˙��}r˚��(h!U�h"jı��ubah/häubaubh)År¸��}r˝��(h!U�h"jÑ��h-h.h/j‰��h1}r˛��(h3]UlevelKh6]h5]rˇ��jâ��aUsourceh.h4]h9]UlineKÕUtypejÁ��uh;KÕh<hh=]r���hÜ)År��}r��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}r��(h3]h4]h5]h6]h9]uh"j¸��h=]r��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".r��ÖÅr��}r��(h!U�h"j��ubah/häubaubh)År��}r	��(h!U�h"jì��h-h.h/j‰��h1}r
��(h3]UlevelKh6]h5]r��jò��aUsourceh.h4]h9]UlineK–UtypejÁ��uh;K–h<hh=]r��hÜ)År
��}r��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}r��(h3]h4]h5]h6]h9]uh"j��h=]r��hFXE���Duplicate implicit target name: "dataone use cases and requirements".r��ÖÅr��}r��(h!U�h"j
��ubah/häubaubh)År��}r��(h!U�h"j¿��h-h.h/j‰��h1}r��(h3]UlevelKh6]h5]r��j≈��aUsourceh.h4]h9]UlineKŸUtypejÁ��uh;KŸh<hh=]r��hÜ)År��}r��(h!X-���Duplicate implicit target name: "discussion".h1}r��(h3]h4]h5]h6]h9]uh"j��h=]r��hFX-���Duplicate implicit target name: "discussion".r��ÖÅr��}r��(h!U�h"j��ubah/häubaubh)År ��}r!��(h!U�h"jµ��h-h.h/j‰��h1}r"��(h3]UlevelKh6]h5]r#��jª��aUsourceh.h4]h9]UlineK‡UtypejÁ��uh;K‡h<hh=]r$��hÜ)År%��}r&��(h!X.���Duplicate implicit target name: "description".h1}r'��(h3]h4]h5]h6]h9]uh"j ��h=]r(��hFX.���Duplicate implicit target name: "description".r)��ÖÅr*��}r+��(h!U�h"j%��ubah/häubaubh)År,��}r-��(h!U�h"j≈��h-h.h/j‰��h1}r.��(h3]UlevelKh6]h5]r/��jÀ��aUsourceh.h4]h9]UlineK‰UtypejÁ��uh;K‰h<hh=]r0��hÜ)År1��}r2��(h!X7���Duplicate implicit target name: "what premis suggests".h1}r3��(h3]h4]h5]h6]h9]uh"j,��h=]r4��hFX7���Duplicate implicit target name: "what premis suggests".r5��ÖÅr6��}r7��(h!U�h"j1��ubah/häubaubh)År8��}r9��(h!U�h"jÌ��h-h.h/j‰��h1}r:��(h3]UlevelKh6]h5]r;��jÛ��aUsourceh.h4]h9]UlineK¯UtypejÁ��uh;K¯h<hh=]r<��hÜ)År=��}r>��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}r?��(h3]h4]h5]h6]h9]uh"j8��h=]r@��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".rA��ÖÅrB��}rC��(h!U�h"j=��ubah/häubaubh)ÅrD��}rE��(h!U�h"j˝��h-h.h/j‰��h1}rF��(h3]UlevelKh6]h5]rG��j��aUsourceh.h4]h9]UlineK˚UtypejÁ��uh;K˚h<hh=]rH��hÜ)ÅrI��}rJ��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}rK��(h3]h4]h5]h6]h9]uh"jD��h=]rL��hFXE���Duplicate implicit target name: "dataone use cases and requirements".rM��ÖÅrN��}rO��(h!U�h"jI��ubah/häubaubh)ÅrP��}rQ��(h!U�h"j;��h-h.h/j‰��h1}rR��(h3]UlevelKh6]h5]rS��jA��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]rT��hÜ)ÅrU��}rV��(h!X-���Duplicate implicit target name: "discussion".h1}rW��(h3]h4]h5]h6]h9]uh"jP��h=]rX��hFX-���Duplicate implicit target name: "discussion".rY��ÖÅrZ��}r[��(h!U�h"jU��ubah/häubaubh)År\��}r]��(h!U�h"jZ��h-h.h/j‰��h1}r^��(h3]UlevelKh6]h5]r_��j`��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]r`��hÜ)Åra��}rb��(h!X.���Duplicate implicit target name: "description".h1}rc��(h3]h4]h5]h6]h9]uh"j\��h=]rd��hFX.���Duplicate implicit target name: "description".re��ÖÅrf��}rg��(h!U�h"ja��ubah/häubaubh)Årh��}ri��(h!U�h"jz��h-h.h/j‰��h1}rj��(h3]UlevelKh6]h5]rk��jÄ��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]rl��hÜ)Årm��}rn��(h!X7���Duplicate implicit target name: "what premis suggests".h1}ro��(h3]h4]h5]h6]h9]uh"jh��h=]rp��hFX7���Duplicate implicit target name: "what premis suggests".rq��ÖÅrr��}rs��(h!U�h"jm��ubah/häubaubh)Årt��}ru��(h!U�h"jí��h-h.h/j‰��h1}rv��(h3]UlevelKh6]h5]rw��jò��aUsourceh.h4]h9]UlineM"UtypejÁ��uh;M"h<hh=]rx��hÜ)Åry��}rz��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}r{��(h3]h4]h5]h6]h9]uh"jt��h=]r|��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".r}��ÖÅr~��}r��(h!U�h"jy��ubah/häubaubh)ÅrÄ��}rÅ��(h!U�h"j¢��h-h.h/j‰��h1}rÇ��(h3]UlevelKh6]h5]rÉ��j®��aUsourceh.h4]h9]UlineM%UtypejÁ��uh;M%h<hh=]rÑ��hÜ)ÅrÖ��}rÜ��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}rá��(h3]h4]h5]h6]h9]uh"jÄ��h=]rà��hFXE���Duplicate implicit target name: "dataone use cases and requirements".râ��ÖÅrä��}rã��(h!U�h"jÖ��ubah/häubaubh)Årå��}rç��(h!U�h"j“��h-h.h/j‰��h1}ré��(h3]UlevelKh6]h5]rè��jÿ��aUsourceh.h4]h9]UlineM.UtypejÁ��uh;M.h<hh=]rê��hÜ)Årë��}rí��(h!X-���Duplicate implicit target name: "discussion".h1}rì��(h3]h4]h5]h6]h9]uh"jå��h=]rî��hFX-���Duplicate implicit target name: "discussion".rï��ÖÅrñ��}ró��(h!U�h"jë��ubah/häubaubh)Årò��}rô��(h!U�h"jÒ��h-h.h/j‰��h1}rö��(h3]UlevelKh6]h5]rõ��j˜��aUsourceh.h4]h9]UlineM5UtypejÁ��uh;M5h<hh=]rú��hÜ)Årù��}rû��(h!X.���Duplicate implicit target name: "description".h1}rü��(h3]h4]h5]h6]h9]uh"jò��h=]r†��hFX.���Duplicate implicit target name: "description".r°��ÖÅr¢��}r£��(h!U�h"jù��ubah/häubaubh)År§��}r•��(h!U�h"j	��h-h.h/j‰��h1}r¶��(h3]UlevelKh6]h5]rß��j��aUsourceh.h4]h9]UlineM<UtypejÁ��uh;M<h<hh=]r®��hÜ)År©��}r™��(h!X7���Duplicate implicit target name: "what premis suggests".h1}r´��(h3]h4]h5]h6]h9]uh"j§��h=]r¨��hFX7���Duplicate implicit target name: "what premis suggests".r≠��ÖÅrÆ��}rØ��(h!U�h"j©��ubah/häubaubh)År∞��}r±��(h!U�h"j!��h-h.h/j‰��h1}r≤��(h3]UlevelKh6]h5]r≥��j'��aUsourceh.h4]h9]UlineMGUtypejÁ��uh;MGh<hh=]r¥��hÜ)Årµ��}r∂��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}r∑��(h3]h4]h5]h6]h9]uh"j∞��h=]r∏��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".rπ��ÖÅr∫��}rª��(h!U�h"jµ��ubah/häubaubh)Årº��}rΩ��(h!U�h"j1��h-h.h/j‰��h1}ræ��(h3]UlevelKh6]h5]rø��j7��aUsourceh.h4]h9]UlineMJUtypejÁ��uh;MJh<hh=]r¿��hÜ)År¡��}r¬��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}r√��(h3]h4]h5]h6]h9]uh"jº��h=]rƒ��hFXE���Duplicate implicit target name: "dataone use cases and requirements".r≈��ÖÅr∆��}r«��(h!U�h"j¡��ubah/häubaubh)År»��}r…��(h!U�h"jã��h-h.h/j‰��h1}r ��(h3]UlevelKh6]h5]rÀ��jë��aUsourceh.h4]h9]UlineMPUtypejÁ��uh;MPh<hh=]rÃ��hÜ)ÅrÕ��}rŒ��(h!X-���Duplicate implicit target name: "discussion".h1}rœ��(h3]h4]h5]h6]h9]uh"j»��h=]r–��hFX-���Duplicate implicit target name: "discussion".r—��ÖÅr“��}r”��(h!U�h"jÕ��ubah/häubaubh)År‘��}r’��(h!U�h"j™��h-h.h/j‰��h1}r÷��(h3]UlevelKh6]h5]r◊��j∞��aUsourceh.h4]h9]UlineMVUtypejÁ��uh;MVh<hh=]rÿ��hÜ)ÅrŸ��}r⁄��(h!X.���Duplicate implicit target name: "description".h1}r€��(h3]h4]h5]h6]h9]uh"j‘��h=]r‹��hFX.���Duplicate implicit target name: "description".r›��ÖÅrfi��}rfl��(h!U�h"jŸ��ubah/häubaubh)År‡��}r·��(h!U�h"j¬��h-h.h/j‰��h1}r‚��(h3]UlevelKh6]h5]r„��j»��aUsourceh.h4]h9]UlineM[UtypejÁ��uh;M[h<hh=]r‰��hÜ)ÅrÂ��}rÊ��(h!X7���Duplicate implicit target name: "what premis suggests".h1}rÁ��(h3]h4]h5]h6]h9]uh"j‡��h=]rË��hFX7���Duplicate implicit target name: "what premis suggests".rÈ��ÖÅrÍ��}rÎ��(h!U�h"jÂ��ubah/häubaubh)ÅrÏ��}rÌ��(h!U�h"j⁄��h-h.h/j‰��h1}rÓ��(h3]UlevelKh6]h5]rÔ��j‡��aUsourceh.h4]h9]UlineMgUtypejÁ��uh;Mgh<hh=]r��hÜ)ÅrÒ��}rÚ��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}rÛ��(h3]h4]h5]h6]h9]uh"jÏ��h=]rÙ��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".rı��ÖÅrˆ��}r˜��(h!U�h"jÒ��ubah/häubaubh)År¯��}r˘��(h!U�h"jÍ��h-h.h/j‰��h1}r˙��(h3]UlevelKh6]h5]r˚��j��aUsourceh.h4]h9]UlineMjUtypejÁ��uh;Mjh<hh=]r¸��hÜ)År˝��}r˛��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}rˇ��(h3]h4]h5]h6]h9]uh"j¯��h=]r�	��hFXE���Duplicate implicit target name: "dataone use cases and requirements".r	��ÖÅr	��}r	��(h!U�h"j˝��ubah/häubaubh)År	��}r	��(h!U�h"j��h-h.h/j‰��h1}r	��(h3]UlevelKh6]h5]r	��j��aUsourceh.h4]h9]UlineMsUtypejÁ��uh;Msh<hh=]r	��hÜ)År		��}r
	��(h!X-���Duplicate implicit target name: "discussion".h1}r	��(h3]h4]h5]h6]h9]uh"j	��h=]r	��hFX-���Duplicate implicit target name: "discussion".r
	��ÖÅr	��}r	��(h!U�h"j		��ubah/häubaubh)År	��}r	��(h!U�h"j7��h-h.h/j‰��h1}r	��(h3]UlevelKh6]h5]r	��j=��aUsourceh.h4]h9]UlineM{UtypejÁ��uh;M{h<hh=]r	��hÜ)År	��}r	��(h!X.���Duplicate implicit target name: "description".h1}r	��(h3]h4]h5]h6]h9]uh"j	��h=]r	��hFX.���Duplicate implicit target name: "description".r	��ÖÅr	��}r	��(h!U�h"j	��ubah/häubaubh)År	��}r	��(h!U�h"jO��h-h.h/j‰��h1}r	��(h3]UlevelKh6]h5]r	��jU��aUsourceh.h4]h9]UlineMÖUtypejÁ��uh;MÖh<hh=]r 	��hÜ)År!	��}r"	��(h!X7���Duplicate implicit target name: "what premis suggests".h1}r#	��(h3]h4]h5]h6]h9]uh"j	��h=]r$	��hFX7���Duplicate implicit target name: "what premis suggests".r%	��ÖÅr&	��}r'	��(h!U�h"j!	��ubah/häubaubh)År(	��}r)	��(h!U�h"jg��h-h.h/j‰��h1}r*	��(h3]UlevelKh6]h5]r+	��jm��aUsourceh.h4]h9]UlineMòUtypejÁ��uh;Mòh<hh=]r,	��hÜ)År-	��}r.	��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}r/	��(h3]h4]h5]h6]h9]uh"j(	��h=]r0	��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".r1	��ÖÅr2	��}r3	��(h!U�h"j-	��ubah/häubaubh)År4	��}r5	��(h!U�h"jw��h-h.h/j‰��h1}r6	��(h3]UlevelKh6]h5]r7	��j}��aUsourceh.h4]h9]UlineMõUtypejÁ��uh;Mõh<hh=]r8	��hÜ)År9	��}r:	��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}r;	��(h3]h4]h5]h6]h9]uh"j4	��h=]r<	��hFXE���Duplicate implicit target name: "dataone use cases and requirements".r=	��ÖÅr>	��}r?	��(h!U�h"j9	��ubah/häubaubh)År@	��}rA	��(h!U�h"jƒ��h-h.h/j‰��h1}rB	��(h3]UlevelKh6]h5]rC	��j ��aUsourceh.h4]h9]UlineM©UtypejÁ��uh;M©h<hh=]rD	��hÜ)ÅrE	��}rF	��(h!X-���Duplicate implicit target name: "discussion".h1}rG	��(h3]h4]h5]h6]h9]uh"j@	��h=]rH	��hFX-���Duplicate implicit target name: "discussion".rI	��ÖÅrJ	��}rK	��(h!U�h"jE	��ubah/häubaubh)ÅrL	��}rM	��(h!U�h"j„��h-h.h/j‰��h1}rN	��(h3]UlevelKh6]h5]rO	��jÈ��aUsourceh.h4]h9]UlineM∞UtypejÁ��uh;M∞h<hh=]rP	��hÜ)ÅrQ	��}rR	��(h!X.���Duplicate implicit target name: "description".h1}rS	��(h3]h4]h5]h6]h9]uh"jL	��h=]rT	��hFX.���Duplicate implicit target name: "description".rU	��ÖÅrV	��}rW	��(h!U�h"jQ	��ubah/häubaubh)ÅrX	��}rY	��(h!U�h"jÛ��h-h.h/j‰��h1}rZ	��(h3]UlevelKh6]h5]r[	��j˘��aUsourceh.h4]h9]UlineM¥UtypejÁ��uh;M¥h<hh=]r\	��hÜ)År]	��}r^	��(h!X7���Duplicate implicit target name: "what premis suggests".h1}r_	��(h3]h4]h5]h6]h9]uh"jX	��h=]r`	��hFX7���Duplicate implicit target name: "what premis suggests".ra	��ÖÅrb	��}rc	��(h!U�h"j]	��ubah/häubaubh)Ård	��}re	��(h!U�h"j��h-h.h/j‰��h1}rf	��(h3]UlevelKh6]h5]rg	��j��aUsourceh.h4]h9]UlineMΩUtypejÁ��uh;MΩh<hh=]rh	��hÜ)Åri	��}rj	��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}rk	��(h3]h4]h5]h6]h9]uh"jd	��h=]rl	��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".rm	��ÖÅrn	��}ro	��(h!U�h"ji	��ubah/häubaubh)Årp	��}rq	��(h!U�h"j��h-h.h/j‰��h1}rr	��(h3]UlevelKh6]h5]rs	��j!��aUsourceh.h4]h9]UlineM¿UtypejÁ��uh;M¿h<hh=]rt	��hÜ)Åru	��}rv	��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}rw	��(h3]h4]h5]h6]h9]uh"jp	��h=]rx	��hFXE���Duplicate implicit target name: "dataone use cases and requirements".ry	��ÖÅrz	��}r{	��(h!U�h"ju	��ubah/häubaubh)År|	��}r}	��(h!U�h"jI��h-h.h/j‰��h1}r~	��(h3]UlevelKh6]h5]r	��jO��aUsourceh.h4]h9]UlineM…UtypejÁ��uh;M…h<hh=]rÄ	��hÜ)ÅrÅ	��}rÇ	��(h!X-���Duplicate implicit target name: "discussion".h1}rÉ	��(h3]h4]h5]h6]h9]uh"j|	��h=]rÑ	��hFX-���Duplicate implicit target name: "discussion".rÖ	��ÖÅrÜ	��}rá	��(h!U�h"jÅ	��ubah/häubaubh)Årà	��}râ	��(h!U�h"jh��h-h.h/j‰��h1}rä	��(h3]UlevelKh6]h5]rã	��jn��aUsourceh.h4]h9]UlineM–UtypejÁ��uh;M–h<hh=]rå	��hÜ)Årç	��}ré	��(h!X.���Duplicate implicit target name: "description".h1}rè	��(h3]h4]h5]h6]h9]uh"jà	��h=]rê	��hFX.���Duplicate implicit target name: "description".rë	��ÖÅrí	��}rì	��(h!U�h"jç	��ubah/häubaubh)Årî	��}rï	��(h!U�h"jÄ��h-h.h/j‰��h1}rñ	��(h3]UlevelKh6]h5]ró	��jÜ��aUsourceh.h4]h9]UlineM◊UtypejÁ��uh;M◊h<hh=]rò	��hÜ)Årô	��}rö	��(h!X7���Duplicate implicit target name: "what premis suggests".h1}rõ	��(h3]h4]h5]h6]h9]uh"jî	��h=]rú	��hFX7���Duplicate implicit target name: "what premis suggests".rù	��ÖÅrû	��}rü	��(h!U�h"jô	��ubah/häubaubh)År†	��}r°	��(h!U�h"j®��h-h.h/j‰��h1}r¢	��(h3]UlevelKh6]h5]r£	��jÆ��aUsourceh.h4]h9]UlineMıUtypejÁ��uh;Mıh<hh=]r§	��hÜ)År•	��}r¶	��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}rß	��(h3]h4]h5]h6]h9]uh"j†	��h=]r®	��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".r©	��ÖÅr™	��}r´	��(h!U�h"j•	��ubah/häubaubh)År¨	��}r≠	��(h!U�h"j∏��h-h.h/j‰��h1}rÆ	��(h3]UlevelKh6]h5]rØ	��jæ��aUsourceh.h4]h9]UlineM¯UtypejÁ��uh;M¯h<hh=]r∞	��hÜ)År±	��}r≤	��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}r≥	��(h3]h4]h5]h6]h9]uh"j¨	��h=]r¥	��hFXE���Duplicate implicit target name: "dataone use cases and requirements".rµ	��ÖÅr∂	��}r∑	��(h!U�h"j±	��ubah/häubaubh)År∏	��}rπ	��(h!U�h"jÊ��h-h.h/j‰��h1}r∫	��(h3]UlevelKh6]h5]rª	��jÏ��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]rº	��hÜ)ÅrΩ	��}ræ	��(h!X-���Duplicate implicit target name: "discussion".h1}rø	��(h3]h4]h5]h6]h9]uh"j∏	��h=]r¿	��hFX-���Duplicate implicit target name: "discussion".r¡	��ÖÅr¬	��}r√	��(h!U�h"jΩ	��ubah/häubaubh)Årƒ	��}r≈	��(h!U�h"j��h-h.h/j‰��h1}r∆	��(h3]UlevelKh6]h5]r«	��j��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]r»	��hÜ)År…	��}r 	��(h!X.���Duplicate implicit target name: "description".h1}rÀ	��(h3]h4]h5]h6]h9]uh"jƒ	��h=]rÃ	��hFX.���Duplicate implicit target name: "description".rÕ	��ÖÅrŒ	��}rœ	��(h!U�h"j…	��ubah/häubaubh)År–	��}r—	��(h!U�h"j��h-h.h/j‰��h1}r“	��(h3]UlevelKh6]h5]r”	��j#��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]r‘	��hÜ)År’	��}r÷	��(h!X7���Duplicate implicit target name: "what premis suggests".h1}r◊	��(h3]h4]h5]h6]h9]uh"j–	��h=]rÿ	��hFX7���Duplicate implicit target name: "what premis suggests".rŸ	��ÖÅr⁄	��}r€	��(h!U�h"j’	��ubah/häubaubh)År‹	��}r›	��(h!U�h"j5��h-h.h/j‰��h1}rfi	��(h3]UlevelKh6]h5]rfl	��j;��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]r‡	��hÜ)År·	��}r‚	��(h!XA���Duplicate implicit target name: "what bagit and oai-ore provide".h1}r„	��(h3]h4]h5]h6]h9]uh"j‹	��h=]r‰	��hFXA���Duplicate implicit target name: "what bagit and oai-ore provide".rÂ	��ÖÅrÊ	��}rÁ	��(h!U�h"j·	��ubah/häubaubh)ÅrË	��}rÈ	��(h!U�h"jE��h-h.h/j‰��h1}rÍ	��(h3]UlevelKh6]h5]rÎ	��jK��aUsourceh.h4]h9]UlineMUtypejÁ��uh;Mh<hh=]rÏ	��hÜ)ÅrÌ	��}rÓ	��(h!XE���Duplicate implicit target name: "dataone use cases and requirements".h1}rÔ	��(h3]h4]h5]h6]h9]uh"jË	��h=]r	��hFXE���Duplicate implicit target name: "dataone use cases and requirements".rÒ	��ÖÅrÚ	��}rÛ	��(h!U�h"jÌ	��ubah/häubaubh)ÅrÙ	��}rı	��(h!U�h"js��h-h.h/j‰��h1}rˆ	��(h3]UlevelKh6]h5]r˜	��jy��aUsourceh.h4]h9]UlineM&UtypejÁ��uh;M&h<hh=]r¯	��hÜ)År˘	��}r˙	��(h!X-���Duplicate implicit target name: "discussion".h1}r˚	��(h3]h4]h5]h6]h9]uh"jÙ	��h=]r¸	��hFX-���Duplicate implicit target name: "discussion".r˝	��ÖÅr˛	��}rˇ	��(h!U�h"j˘	��ubah/häubaubeUcurrent_sourcer�
��NU
decorationr
��NUautofootnote_startr
��KUnameidsr
��}r
��(hNhj,��hNh	j
��h
j��hjü��hNh
h8hjá��hjÊ��hjO��hjˆ��hjÿ��hNhjñ��hjR��hj™��hj˙��hj]��hNuh=]r
��h+ah!U�Utransformerr
��NU
footnote_refsr
��}r
��Urefnamesr	
��}r

��Usymbol_footnotesr
��]r
��Uautofootnote_refsr
��]r
��Usymbol_footnote_refsr
��]r
��U	citationsr
��]r
��h<hUcurrent_liner
��NUtransform_messagesr
��]r
��Ureporterr
��NUid_startr
��K.U
autofootnotesr
��]r
��U
citation_refsr
��}r
��Uindirect_targetsr
��]r
��Usettingsr
��(cdocutils.frontend
Values
r
��or 
��}r!
��(Ufootnote_backlinksr"
��KUrecord_dependenciesr#
��NUrfc_base_urlr$
��Uhttps://tools.ietf.org/html/r%
��U	tracebackr&
��àUpep_referencesr'
��NUstrip_commentsr(
��NU
toc_backlinksr)
��hêU
language_coder*
��Uenr+
��U	datestampr,
��NUreport_levelr-
��KU_destinationr.
��NU
halt_levelr/
��KU
strip_classesr0
��NhCNUerror_encoding_error_handlerr1
��Ubackslashreplacer2
��Udebugr3
��NUembed_stylesheetr4
��âUoutput_encoding_error_handlerr5
��Ustrictr6
��U
sectnum_xformr7
��KUdump_transformsr8
��NU
docinfo_xformr9
��KUwarning_streamr:
��NUpep_file_url_templater;
��Upep-%04dr<
��Uexit_status_levelr=
��KUconfigr>
��NUstrict_visitorr?
��NUcloak_email_addressesr@
��àUtrim_footnote_reference_spacerA
��âUenvrB
��NUdump_pseudo_xmlrC
��NUexpose_internalsrD
��NUsectsubtitle_xformrE
��âUsource_linkrF
��NUrfc_referencesrG
��NUoutput_encodingrH
��Uutf-8rI
��U
source_urlrJ
��NUinput_encodingrK
��U	utf-8-sigrL
��U_disable_configrM
��NU	id_prefixrN
��U�U	tab_widthrO
��KUerror_encodingrP
��UUTF-8rQ
��U_sourcerR
��h.Ugettext_compactrS
��àU	generatorrT
��NUdump_internalsrU
��NUsmart_quotesrV
��âUpep_base_urlrW
��U https://www.python.org/dev/peps/rX
��Usyntax_highlightrY
��UlongrZ
��Uinput_encoding_error_handlerr[
��j6
��Uauto_id_prefixr\
��Uidr]
��Udoctitle_xformr^
��âUstrip_elements_with_classesr_
��NU
_config_filesr`
��]Ufile_insertion_enabledra
��àUraw_enabledrb
��KU
dump_settingsrc
��NubUsymbol_footnote_startrd
��K�Uidsre
��}rf
��(jˆ��h)j˙��jˆ��j∞��j™��jO��jK��jy��js��jK��jE��j;��j5��j#��j��j��j��jÏ��jÊ��jñ��jí��jÊ��j‚��jR��h'j^��jX��jÛ��jÌ��j��j˝��j��j��jÀ��j≈��jò��jì��j≈��j¿��jb��j]��jâ��jÑ��j“��h$jA��j;��j`��jZ��jÄ��jz��jò��jí��j®��j¢��jÿ��j“��j˜��jÒ��j��j	��j'��j!��j7��j1��j!��j��jm��jg��j˘��jÛ��j��j��j ��jƒ��jú��jñ��j,��j(��jÈ��j„��j��j��jæ��j∏��jü��jõ��jO��jI��j6��j0��j]��jY��jÆ��j®��jÜ��jÄ��jÿ��j‘��j»��j¬��já��jÉ��j��jÍ��j}��jw��jª��jµ��jn��jh��jU��jO��j
��j	��jë��jã��j‡��j⁄��jN��jH��j��j��h8h+j™��j¶��j=��j7��uUsubstitution_namesrg
��}rh
��h/h<h1}ri
��(h3]h6]h5]Usourceh.h4]h9]uU	footnotesrj
��]rk
��Urefidsrl
��}rm
��ub.