...
Site | Collection | EAD structure / location of born digital materials [type of hydra object] | notes | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Hull | Gallagher |
|
| ||||||||||
Hull | Socialist Health Assoc. |
|
| ||||||||||
Stanford | Xanadu | collection | 1. Target "born digital" sub-level identified by <unittitle> | ||||||||||
Stanford | Gould | collection -- unittitle "Stephen Jay Gould papers" unitid: M1437 | EAD only goes down to the single "Born digital" series description, with no details expressed at lower levels. A rationalized directory structure and FTK output are intended to support a direct translation into Hypatia objects for both unprocessed and processed views without an intermediary EAD. | ||||||||||
Virginia | Cheuse |
|
| ||||||||||
Yale | Conn. Oral Histories |
|
| ||||||||||
Yale | Love Makes a Family |
|
| ||||||||||
Yale | Pelli |
|
| ||||||||||
Yale | Tobin | collection | 1. Target sub-level identified by <unittitle> | ||||||||||
Yale | Turner |
|
| ||||||||||
Yale | Welch |
|
|
...
In general, "item" level entries in an EAD will map to individual Hypatia objects. The "file" level" may also be considered an item node for a specific EAD. Unless otherwise indicated for a specific conversion, other levels will translate to set objects in Hypatia, even if they are empty sets because the EAD had no item-level description.
EAD item node mapping
Issue: A few Stanford-centric features may not be of interest to other Hypatia partners. What accommodation, if any, is needed for Stanford vs generic software?
...
EAD-to-MODS - general information
...