Vous êtes sur la page 1sur 1

of models being used by others, or designing their own schema (either as a complete solution

or as a minimal interim one until a standard emerges).

Many national archives authorities have released metadata specifications for record keeping
systems that include preservation needs. In the library field, an international working group
convened by OCLC and the Research Libraries Group (RLG) released a recommended
preservation metadata framework in mid-2002 (available online at
<http://www.oclc.org/research/pmwg/pm_framework.pdf>). Their report is a good starting
point for exploring the metadata that may be needed.

An interesting implementation by the National Library of New Zealand attempts to adapt the
OLCLC/RLG work to a particular programme and its circumstances (available online at
<http://www.natlib.govt.nz/files/4initiatives_metaschema.pdf>). This schema proposes the
following elements (somewhat summarised here):

Describing a digital object When created


Name of the object MIME type/format (eg image/tif)
Local identifiers Version
Global persistent identifier Key file that provides access
File location in storage system Characteristics of specific file types
Date when created as preservation master (eg for image files: resolution, dimensions,
Overarching technical composition (no of tonal resolution, colour space, colour
files of each MIME type) management, colour lookup table,
Structural type (eg text, image) orientation, compression)
Hardware required for object to function (eg for text files: compression, character
Software required for object to function set, associated DTD for structured text,
Special installation instructions structural divisions)
Built-in access inhibitors and facilitators (eg for audio: resolution, duration, bit rate,
Quirks (in-built anomalies) compression, encapsulation, track
Authentication or validation keys number and type)
Who created metadata and when (eg for video: frame dimensions, duration,
frame rate, compression, encoding
Describing any process applied to an structure, sound)
object (including creation) (eg for datasets: common elements above
Name of process only)
Purpose (eg for executable files: common elements
Agent who carried out process above only)
Agent who approved process and when
Hardware used Describing update of metadata
Software used Agent modifying metadata
Steps involved in process When modified
Outcomes Field modified
Standards or specifications used
When completed
Describing technical characteristics of any
files within the object
Specific file identifiers
Relationship to other component files
File size

95

Vous aimerez peut-être aussi