| Element |
Examples/Terms |
Required |
Repeatable |
Source |
|
1. Persistant Identifer
An identifier or 'permanent name' for an
object that identifies it uniquely and persistently,
and enables links to different editions of
it, to metadata about it, and to other objects
related to it.
|
www.tdh.state.tx.us/
otpc/sb55rpt/
2002/01/31/
2000legrpt.PDF
(agency's path + date of capture + filename)
|
Y
|
N
|
S
|
|
2. Date of Creation
Date expressed in a standardized form that
the edition came into being.
|
Example:1. 20021212 (yyyymmdd.)
|
Y
|
N
|
A
|
|
3. Date of Capture
|
20021212
|
Y
|
N
|
S
|
|
4. Mime Type
MIME types are used to automatically populate
the field. For a multi-file object this field
will be repeated for each file.
|
List of terms:
1. Image/jpeg
2. Text/html
|
Y
|
Y
|
S
|
|
5. Storage Information
Total file size for all components of the
object
|
Example:
1. 1.3 Mb
|
Y
|
N
|
S
|
|
6. Access Inhibitors Any method used to inhibit
access, which would impact on preservation
procedures, such as encryption or watermarking.
|
Example:
1. Watermark by Digimarc Professional
|
N
|
Y
|
A
|
|
7. Finding and Searching Aids, and Access
Facilitators?
Any system or method used to enhance access
to information within the digital object,
which need to be maintained in successive
generations.
|
Examples:
1. CD type ID points linked to file
2. Video and text time code linked
|
N
|
Y
|
A
|
|
8. Checksum
Value derived by a standard checksum system
to certify the authenticity of the document.
|
Examples:
1. 16423521
|
Y
|
Y
|
S
|
|
9. Relationships
Relationships between this edition and other
objects necessary for preservation management.
The field enables an object to be linked to
its metadata, to earlier or later editions
of it, other forms of it, and other objects,
including finding aids. It is essential to
maintaining a history of the change of an
object by linking to the metadata of earlier
editions, including that of the source object
|
Examples:
1. Linked to previous in a migration sequence,
e.g., was migrated from [Unique Identifier]
2. Linked to following in a migration sequence,
e.g., was migrated to [Unique Identifier]
3. Is part of a higher aggregation, e.g.,
part of [Unique Identifier]
4. Contains the lower component(s), e.g.,
contains [Unique Identifier]
5. Revised from [Unique Identifier]
6. Related to off-line material, e.g., accompanied
by book [call number]
7. etc
|
N
|
Y
|
A
|
|
10. Exceptions
Any characteristic that may appear as a
loss in functionality or change in the look
and feel of an object. May describe or provide
links to quirks. Includes only descriptions
of exceptions that are relevant to the use
of the current instance. Should include any
relevant dates. This element documents changes
that occur as a result of digitization, duplication,
or migration, as well as those that might
be inherent in the source document.
|
Example:
1. The Shockwave files could not be captured
from the source document.
|
N
|
Y
|
A+M
|
|
11. Process
All relevant details of any process applied
to a digital object or file, including software,
specific settings or actions that were required
to produce the current manifestation, details
of all equipment and responsible agencies
or persons. This element documents what has
happened to a particular manifestation of
an object. The series of linked records pertaining
to manifestations of an object builds up a
change history over time. This information
is essential to document what preservation
methods have been applied to the object and
how the various manifestations might differ
from each other.
|
|
N
|
Y
|
A
|
|
12. Other
(Any) Any other information relevant to the
preservation of the object.
|
[Use of this field is not encouraged!]
|
N
|
N
|
M
|
|
13. Archiving Decision The date and reason
for any decision whether this work should
be archived and the date of that decision.
This field may also include a retention period
or review date.
|
Example: 1. 20011212 - Conforms to TRAIL
selection guidelines. Date of review: 20051212
|
N
|
Y
|
M
|
