Versions Compared

Old Version 18

changes.mady.by.user Lynn McRae

Saved on

compared with

New Version 19

changes.mady.by.user Lynn McRae

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Site

Collection

EAD structure / location of born digital materials [type of hydra object]

notes

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fb9ad875f003ea84-2bed4f7a-4f6341c4-89599a3c-8d1ccdc097ca3b2181856a92"><ac:plain-text-body><![CDATA[

Hull

Gallagher

collection [set]
]]></ac:plain-text-body></ac:structured-macro>

 

Hull

Socialist Health Assoc.

 

 

Stanford

Xanadu

collection

Wiki Markup
*\[set\]*

- <c> file (10 of 10) -- unittitle "Born Digital"
Wiki Markup
*\[set\]*
- - <c> item -- unitid: CM01
Wiki Markup
*\[item\]*

- - <c> item -- unitid: CM02
Wiki Markup
*\[item\]*

- - <c> item -- unitid: CM03
Wiki Markup
*\[item\]*

1. Target "born digital" sub-level identified by <unittitle>
2. Collection only described to the container level (hard drives).
3. EAD "item" level  corresponds to target Fedora "item".
4. Item <unitid> is used as a filename stem to bind content files to Hypatia objects.

Stanford

Gould

collection -- unittitle "Stephen Jay Gould papers" unitid: M1437

Wiki Markup
*\[set\]*

- <c> series -- unittitle "Series 6: Born Digital Materials"
Wiki Markup
*\[set\]*

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

Wiki Markup
*\[set\]*

- <c01> series (3 of 7) -- unittitle "Accession 2004-M-088"
Wiki Markup
*\[set\]*
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="596732bec7323fcb-04616271-4887451a-908ab5fc-9b9a83751d5d51b40dca1c75"><ac:plain-text-body><![CDATA[- - <c02> file (28 of 29) -- unittitle "Computer diskettes [3.5 inch]"
Wiki Markup
*\[set\]*
]]></ac:plain-text-body></ac:structured-macro>
- - - <c03 file -- unitid: 2004-M-088.0001
Wiki Markup
*\[item\]*
           :
- - - <c03 file -- unitid: 2004-M-088.0027"
Wiki Markup
*\[item\]*

1. Target sub-level identified by <unittitle>
2. Collection only described to the container level (diskettes).
3. EAD "item" level  corresponds to target Fedora "item".
4. Item <unitid> is used as a filename stem to bind content files to Hypatia objects.

Yale

Turner

 

 

Yale

Welch

 

 

...

Issue: Stanford <container> conventions and mapping into a MODS "Located inLocation" note a collection and location MODS relatedItem (revised 10/24/11 to split out Collection title in item record and nest this information in a relatedItem):

We will create a concise representation of the physical/logical location (as appropriate) of the materials in the context of the collection and its hierarchy. It will be a MODS <relatedItem><physicalLocation type="location">. It will be a relatedItem representing the collection and a single string concatenatingconcatenation of the following information:

  • Series and Series, subseries names etc if presentpresent  -- e.g., Series 6: Born Digital Materials
  • The container labeltype (box, map case, etc) and ID -- e.g., Box 11
  • A sub-The container type + value, down to the level of the item -- e.g., Folder 3

Assembles as "Series 6: Born Digital Materials - Box 11 - Folder 3"

Is this generalizable, across Stanford collections? across institutions?

...