Proposed list of metadata fields to drive the discovery and delivery of document level objects
The following is a list of descriptive, technical and administrative metadata that may accompany a document in Hypatia. Documents can be either a single file or a grouping of files that are that exist together in either a folder, a zipped archive or a disk image. Not all documents will necessarily have metadata for all of these metadata fields.
Field Name |
ISAD(G) Element |
Description |
Searchable? |
Facet? |
Display? |
Sortable? |
Allow edit? |
Metadata Source |
---|---|---|---|---|---|---|---|---|
|
|
Fields required for Standards-Compliant Archival Description |
|
|
|
|
|
|
Repository |
Name of archival unit responsible for the collection. |
Yes |
Yes |
Yes |
Yes |
|
collection object |
|
collection call number |
|
Maybe |
Yes |
Yes |
Yes |
|
collection object |
|
collection title |
|
Yes |
No |
Yes |
Yes |
|
collection object |
|
accession number |
|
|
No |
No |
Maybe? |
No |
|
|
Document identifier |
|
Yes |
No |
Yes |
Maybe |
No |
autogenerated |
|
archival context |
|
Location of the document in an intellectual arrangement (series, subseries, etc.) |
No |
Yes (with collection title) |
Yes |
No |
Yes (archivist) |
FTK / Parent object(s) / EAD |
Level of description |
Identifies the level of arrangement of the unit of description |
No |
Maybe |
Yes |
No |
Yes (archivist) |
|
|
Conditions governing access |
To provide information on the legal status or other regulations that restrict or affect access to the unit of description. |
Yes (need controlled vocabulary) |
Yes |
Yes |
Maybe |
Yes (archivist) |
EAD |
|
Conditions governing use/reproduction |
|
Yes (need controlled vocabulary) |
Yes |
Yes |
Maybe |
Yes (archivist) |
FTK / EAD |
|
Scope and contents |
|
Yes |
No |
Yes |
No |
Yes |
|
|
Creator |
|
Yes |
Yes |
Yes |
No |
Yes (archivist) |
FTK / parent object |
|
subject headings |
|
|
Yes |
Yes |
Yes |
No |
Yes (archivist) |
FTK / |
Citation |
|
|
No |
No |
Yes |
No |
Yes (archivist) |
|
document title |
Title supplied by archivist describing the document |
Yes |
No |
Yes |
Yes |
Yes (archivist) |
EAD? |
|
document date |
Is this the creation date or last modified date. Do we need both? |
Yes |
Yes (need both) |
Yes |
Yes |
|
FTK / |
|
document size |
Indicates the file or document's size on a filesystem |
No |
No |
Yes |
No |
|
FTK / |
|
|
|
Additional fields required for assets |
|
|
|
|
|
|
source media |
|
Description of the physical carrier for a record (floppy disk, hard disk, etc.) |
No |
Yes (need controlled vocabulary) |
Yes |
No |
|
FTK / |
operating system and version (if known) |
|
|
|
|
|
|
|
|
document type |
|
Controlled value list. Is this a text document, image, audio, video, forensic image etc. Where is this list coming from? |
No |
Yes |
Yes |
No |
Yes (archivist) |
FTK / |
file or document name |
|
Document or file name assigned to an object by an operating system |
Yes |
No |
Yes |
No |
Maybe |
FTK / |
document location |
|
Location of the document on a filesystem. This is different from the archival location of a document in a series / subseries. |
No |
No |
Yes |
No |
|
FTK / |
mime type |
The mime type indicates the type of document and may indicate the application that was used to create the document |
Maybe |
No |
Maybe |
No |
|
|
|
application software and version (if known) |
|
No |
No |
Yes |
No |
Yes (archivist) |
FTK / |
|
thumbnail image |
|
image that represents the document type (eg. PDF, text, image etc.) Peter: If the file is an image, it should be the relative thumbnail. |
No |
No |
Yes |
No |
|
FTK for image thumbnail / |
"Download" this |
|
button that allows the archivist or end user to download the document (if permitted) |
No |
No |
Yes |
No |
No |
|
checksum |
|
|
No |
No |
Yes |
No |
No |
FTK / |
Take-down request / policy |
|
|
No |
No |
Yes |
No |
Yes (public for request) |
Web UI |
Original file |
|
|
No |
No |
Yes |
No |
No |
|
Display version of the original file |
|
|
No |
No |
Yes |
No |
No |
|
|
|
User-generated content |
|
|
|
|
|
|
annotations ("stories") |
|
|
No |
No |
Yes |
No |
Yes (creator / invited public / public) |
Web UI |
archivist created tag |
|
tags that archivists/curators add - become facets (How are these different from access points) |
|
yes |
|
|
|
Web UI |
creator tag |
|
tags by creator - become facets by creator (How are these different from access points) |
|
yes |
|
|
|
Web UI |
(pre-)approved user tag |
|
tags that are added by approved users outside of the repository/library - should show up in facet as similar to an approved editor in Wikipedia (?) |
|
yes |
|
|
|
Web UI |
user created tag |
|
tags created by non-approved users; might go through vetting process by repository/library or be listed as unverfied/unvetted editor (like Wikipedia?) |
|
? |
|
|
|
Web UI |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|