Draft list of metadata fields to drive the discovery and delivery of collection-level objects

MM: Recommendation: follow ISAD(G) for consistent reference.

Proposed list of metadata fields to drive the discovery and delivery of Hypatia collections. The following is a list of descriptive, technical and administrative metadata that may accompany a collection in Hypatia. Not all collections will necessarily have metadata for all of these metadata fields.

Field Name

ISAD(G) element

Description

Facet as refinement in UI?

Searchable?

Displayed?

Sortable?

Metadata Source for Tracer Bullet *

Repository

ISDIAH 5.1.2

Name of the archival unit responsible for the collection.

Yes

Yes

Yes

Yes

EAD <repository/>

Collection Call Number

3.1.1

 

Maybe

Yes

Yes

Yes

EAD <unitid/>

Collection Title

3.1.2

 

No

Yes

Yes

Yes

EAD <unittitle/>

Dates

3.1.3

 

Maybe (low priority)

Maybe

Yes

Maybe

EAD <unitdate/>

Creator name(s)

3.2.1

 

Yes

Yes

Yes

Yes

EAD <origination/>

Accession

 

List of accessions that are a part of this collection

No

No

Maybe

No

?

Abstract

 

 

No

Maybe

Yes

No

EAD <abstract/>

Extent

3.1.5

Size of the collection: corresponding storage media, number of files, disk size

No

No

Yes

No

EAD <extent/>

Physical characteristics/technical requirements

3.4.4

Size of the collection: corresponding storage media, number of files, disk size

No

Maybe

Yes

No

EAD <phystech/>

Languages/scripts of material

3.4.3

languages represented in the collection

Yes

Yes

Yes

No

EAD <langmaterial/>

Conditions governing access

3.4.1

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

EAD <accessrestrict/>

Conditions governing use/reproduction

3.4.2

 

Yes (need controlled vocabulary)

Yes

Yes

Maybe

EAD <userestrict/>

Indexing terms

 

names and subjects

Yes

Yes

Yes

No

EAD <controlaccess/>/*

Scope and Content

3.3.1

 

No

Yes

Yes

No

EAD <scopecontent/>

Administrative/Biographical History

3.2.2

Background on collection or creator

No

Yes

Yes

No

EAD <bioghist/>

Custodial History

3.2.3

Information on the history of the unit of description that is significant for its authenticity, integrity and interpretation.

No

Yes

Yes

No

EAD <custodhist/>

Immediate source of acquisition

3.2.4

Information on the history of the unit of description that is significant for its authenticity, integrity and interpretation.

No

Yes

Yes

No

EAD <acqinfo/>

Appraisal, destruction and scheduling

3.3.2

 

No

Maybe

Yes

No

EAD <appraisal/>

Accruals

3.3.3

 

No

Maybe

Yes

No

EAD <accruals/>

System of arrangement

3.3.4

To provide information on the internal structure, the order and/or the system of classification of the unit of description.

No

No

Yes

No

EAD <arrangement/>

Access Notes

 

Notes on how to get access to the collection (eg.series 8 is available on in the reading room)

No

Maybe

Yes

No

?

Existence and location of originals

3.5.1

To indicate the existence, location, availability and/or destruction of originals where the unit of description consists of copies.

No

No

Yes

No

EAD <originalsloc/>

Existence and location of copies

3.5.2

To indicate the existence, location, and availability of copies.

No

No

Yes

No

EAD <altformavail/>

Related units of description

3.5.3

 

No

No

Yes

No

EAD <relatedmaterial/>, <separatedmaterial/>

Publication note

3.5.4

To identify any publications that are about or are based on the use, study, or analysis of the unit of description.

No

No

Yes

No

EAD ?

Note: For collection-level metadata from EAD, this will come from either elements immediately below <archdesc/> or <archdesc/>/<did/>.

Extra Elements to display (informed by SALT)

Institution

Branding?

Other image?

Preliminary Mockup for Hypatia Home Page


LICENSE EXPIRED
buy Balsamiq Wireframes now to continue editing your mockups.

Preliminary Mockup for Hypatia Collection Home Page


LICENSE EXPIRED
buy Balsamiq Wireframes now to continue editing your mockups.
  • No labels

1 Comment

  1. Comments related to process from Apr 26 DA call:

    • Best way to provide collection-level metadata? Collection-level EAD?
    • Need mechanism to create new collection level record
    • Do we need to make mockup match list of fields?
    • What does registration, etc. do at this point?