|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (13)
View Page History
...
{section} {column:width=80%}
|| || Preservation Procedure Policy: Metadata: Original metadata ||
|| || Preservation Procedure Policy: Metadata: Original metadata ||
|| Related Guidance Policy \\ | Metadata | ||
|| Definition/ Description | The term “original metadata” means metadata that is with the digital object at the time it is received by the repository and can consist of different kinds of metadata. This original metadata should be preserved along with the digital object to ensure provenance and authenticity. The organization should have a policy describing how they intend to collect (e.g. by agreement with the depositor or producer) and manage these original metadata. \\
It could be beneficial to develop a policy with regard to agreements with the depositor about which metadata would be preferable and expected, e.g. technical metadata about hardware and software used in the process of creating the digital objects. \\
It could be beneficial to develop a policy with regard to agreements with the depositor about which metadata would be preferable and expected, e.g. technical metadata about hardware and software used in the process of creating the digital objects. \\
The repository should safeguard all relevant metadata in the submission package, where “relevant” implies metadata that can only be created by the producer and cannot be derived from the digital object itself. \\ | ||
|| Why | Original metadata can add to the provenance and authenticity of the digital object. Often this kind of metadata contains information that cannot be retrieved authentically from other sources. \\ | ||
|| Risks | Not keeping the original metadata or unrecorded manipulation might lead to loss of authenticity and provenance. \\ | ||
|| Life cycle stage | Description and Representation Information, Preservation Planning, Create or receive, Ingest \\ | ||
|| Stakeholder | *Depositor*: delivers metadata \\
*Consumer*: needs to be able to access and trust the metadata in order to understand the digital material \\ | ||
|| Cross Reference | Authenticity \\
Provenance \\
Provenance \\
Object \\ | ||
|| Examples | State Library of Queensland: “_As some digital preservation activities may result in changes to the digital material all digital preservation processes will be documented in the provenance metadata to ensure the authenticity of the digital records._” Source:, \[http://www.slq.qld.gov.au/\__data/assets/pdf_file/0020/109550/SLQ{_}{_}{-}Digital_Preservation_Policy_v0.05{-}{_}{_}Oct_2008.pdf_ \\ \[http://www.slq.qld.gov.au/\__data/assets/pdf_file/0020/109550/SLQ{_}{_}{-}Digital_Preservation_Policy_v0.05{-}{_}{_}Oct_2008.pdf{_}_\]_\\
_\]State and University Library, Denmark: “_In connection with digitisation, documentation should include relevant metadata, including data generated during the digitisation process._” Source: [http://en.statsbiblioteket.dk/about-the-library/dpstrategi|http://en.statsbiblioteket.dk/about-the-library/dpstrategi]\\
_State and University Library, Denmark: “When an analogue collection is digitised, data generated in connection with the digitisation process is added to the metadata of the collection._” Source: [http://en.statsbiblioteket.dk/about-the-library/dpstrategy|http://en.statsbiblioteket.dk/about-the-library/resolveuid/cc1d1273338547efba30d65d63bea4f4]\\
_ _ | ||
|| Control Policy | * Information about object creation MUST be kept
* Ingest event information MUST be recorded
* Ingest event information MUST be recorded
* Information on ingest event MUST include date undertaken, \\ | ||
|| Questions to foster discussions | * How does your organisation manage metadata that is received along with the digital object?
* Has your organisation defined a policy to support the process of selecting “relevant original metadata “at ingest? | ||
{column}
{column:width=20%}
{column:width=20%}
...