Date: Fri, 29 Mar 2024 02:49:43 -0400 (EDT) Message-ID: <1094897216.29924.1711694983417@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_29923_754728000.1711694983416" ------=_Part_29923_754728000.1711694983416 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Academy: The educational and research inst= itutions that employ the community of scholars and researchers worldwide.= p>
Administrative Node: The node which serves= as the primary contact with the depositor and holds responsibility for the= consistency of registry entries. The administrative node holds a contractu= al relationship with the Depositor. Only the Administrative node can make u= pdates to the DPN registry entry for content.
Administrative Restoration: In the a= dvent of a failure or withdrawal of an Administrative Node, another DPN nod= e will work with the owners of particular DPN content to ensure they can ga= in access to the preservation package. Stewardship of co= ntent owned by the exiting node is assigned elsewhere to make content avail= able back to the depositor.
Auditing: Planned and documented activity to objectivel= y determine by investigation of evidence the adequacy and compliance with e= stablished procedures and the effectiveness of implementation of the the pr= eservation services DPN has contracted to provide for DPN Members. Aud= iting will be done at several different levels, including object management= , preservation actions and infrastructure.
Bag: An individual preservation item= stored in BagIt format (see below).
BagIt: A "hierarchical file packaging form= at designed to support disk-based storage and network transfer of arbitrary= digital content." DPN uses this format for the storage of digital ob= jects, ensuring the integrity of each preserved object for durability. more info...
Checksum: Also called a hash, a checksum i= s a randomly generated piece of data that is used to verify the fixity of a= digital object (see below). It is most commonly used to detect whether a d= igital object has changed over time.
Content Bag: The basic unit of storage in = the DPN preservation environment. A content bag has member content objects = and metadata stored in BagIt format.
Darkive: A term used in some DPN materials= as a short form of =E2=80=98dark archive=E2=80=99.
Deaccession: The process by which DPN permanently= removes deposited objects from the DPN federation. Deaccessioned objects a= re no longer accessible or recoverable from the DPN nodes.
DPN Charter Member: An institution o= r organization contributing financially to establish and support DPN prior = to June 30, 2013 (current members). Initial DPN Depositors = must all be Charter Members.
DPN Digital Object: AKA First Class Digita= l Object.
DPN Node: Content is held in DPN at nodes.= These are individual organizations and institutions that provide storage a= nd preservation actions for DPN Depositors. DPN will replicate the content = from the Ingest Node (see below) to other DPN Nodes, also known as Replicat= ing Nodes.
Federation: The DPN administrative organiz= ation and all of the Ingest, Administrative, and Replicating nodes
First Class Digital Object: A DPN Digital = Object that is audited and its integrity is maintained. A First Class= Object may contain Second Class object(s). Second Class objects are not in= dividually audited. A first class object is one that has an identity indepe= ndent of any other item. The identity allows the item to persist, and allow= s other items to claim relationships with the item. A DPN content bag is co= nsidered a First Class Digital Object and is tracked via a registry entry.<= /p>
First Node: (obsoleted) See Ingest Nod= e and Administrative Node
Fixity: The process of verifying that= the bit streams that make up a Digital Object have not been changed or cor= rupted from their accepted state.
In-Scope Services: A range of services pro= vided under contract to DPN in support of member data preservation. This in= cludes: preservation of ingested content (ingest, bit level assurance of fi= xity, event monitoring, inventory reporting), replication services, registr= y services - including consistency and synchronization, and general system = and service availability and customer response. Further definition is provi= ded in section 5.1 of the SLA.
Ingest Node: DPN Depositors will work dire= ctly with one or more DPN Nodes to negotiate contracts, determine service l= evels, and deposit materials. This node is known as the "Ingest Node" at de= posit and =E2=80=9CAdministrative Node=E2=80=9D afterwards.
Interpretive Bag: Contains information, pr= ovided by the depositor, intended to provide context and instructions to in= terpret the content bag.
Ingestion: The process of bringing DPN Dep= ositor content into the network. Ingestion happens via a DPN Ingest Node.= p>
Node: Individual organizations and institutions that pr= ovide storage and preservation services for DPN Depositors. DPN automatical= ly replicates the content from Ingest Nodes to other DPN Nodes, known as Re= plicating Nodes.
Package: Organizing and grouping con= tent into discrete units, particularly for storage and data transfer. DPN w= ill be using Bags as an organizational unit. (See "Bag" above.)
Recovery: (See =E2=80=98Restoration=E2=80=99 and =E2=80= =98Administrative Restoration.=E2=80=99)
In the DPN context, recovery applies to t= wo contexts:
Registry: DPN will maintain a registry of = replicated content to allow management of Digital Objects in the DPN networ= k. It will track the identity, source, location of copies, previous version= , legal agreements, and fixity of content in DPN.
Release candidate: A release candidate is a beta v=
ersion with potential to be a final product, which is ready to release unle=
ss significant bugs emerge.
In this stage of product stabilization, all product features have been des=
igned, coded and tested through one or more beta cycles with no known shows=
topper-class bug. There could still be source code changes to fix defects, =
changes to documentation and data files, and peripheral code for test cases=
or utilities.
Replicating Node: DPN will replicate the c= ontent from the Ingest Node (see above) to other DPN Nodes, known as Replic= ating Nodes. Content in Replicating Nodes will be held =E2=80=9Cdark=E2=80= =9D, and inaccessible except for preservation actions.
Restoration: The act of returning content = to the depositor.
Second Class Digital Object: An object con= tained within a First Class Digital object (content Bag). Second Class obje= cts are not individually audited or cataloged within the DPN architecture. = They are retrievable only via the content bag in which they reside.
SLA: Service Level Agre= ement. A contract between a service provider (DPN or Node) and the s= ervice consumer (DPN or Member) that defines the level of service expected = from the service provider. SLAs are output-based in that their purpose is s= pecifically to define what the customer will receive. Th= ey commonly include a definition of: services, performance measurement, pro= blem management, customer duties, warranties, disaster recovery, and provis= ions for termination of agreement.
Soft Launch: The release of a service= to a limited audience. Soft-launching is a method for gathering data on a = product's usage and acceptance before making it generally available. DPN is= choosing a soft launch to test the operation and fine-tune functionality b= efore a full production release.
Succession: The planned and documente= d transfer of content from the original steward to another steward. As= a preservation network for the academy and by the academy, content preserv= ed in DPN will be covered by succession rights that will allow the content = to be used in the future by the academy after the dissolution of the source= of the content. The current model for succession is via =E2=80=9CQuit Clai= m=E2=80=9D.
TDR (Trustworthy Digital Repository): = ; A repository certified as meeting TRAC requirements.
TRAC (Trusted Digital Repositories and Aud= it Checklist): A checklist of best practices for Trusted Digital Repo= sitories built on the recommendations for TDR. more info...
Trusted: Node repositories are designated = as =E2=80=9CTrusted=E2=80=9D by meeting audit and fixity criteria detailed = in the SLA with DPN.