Dealing with multi-part instantiations

Written by Mary on Saturday, December 06, 2008

Dealing with multi-part instantiations in formatGenerations attribute?

Greetings, all! I am spending my weekend creating an SQL conservation database- it's a school project. Catherine Cormon said it took about 300 hours for them to develop InBlik. I'm trying to do mine in about 30.

Anyway, I was thinking formatGenerations might be a handly place to stow a note about instantiation parts. So instead of Archive Master you could have 'Archive Master part 1 of 2' and then the other instantiation would be 'Archive Master part 2 of 2'

You would still need structural metadata to tie the digital instantiations together if you wanted them to play in succession or something, but this might be a start.

TITLE SCOPE FORMAT_GENERATIONS

Conversations in Black and White. [1968, Unidentified Episode] 1 episode on 1 tape. Archive Master part 1 of 1

Conversations in Black and White. [1968, Unidentified Episode] 1 episode on 1 tape. Preservation Master part 1 of 1

Conversations in Black and White. [1968, Unidentified Episode] 1 episode on 1 tape. Access Copy part 1 of 1

Crossroads of the Future. [1948-01-10], Greece 6 episodes of different Lowell Institute series on 7 discs. This episode on 2 discs. Archive Master part 1 of 2

Crossroads of the Future. [1948-01-10], Greece 6 episodes of different Lowell Institute series on 7 discs. This episode on 2 discs. Archive Master part 2 of 2


Comments:

  • Dave Rice said on 12/09 at 10:14 AM

    Hi Mary,
    I’m dealing a lot with this issue as well. I prefer to stick with the pbcore authority list for formatGenerations when possible and usually have tested annotation for this type of data. However I think it bends the definition of instantiation to have two instantiations represent two parts of an instantiation.

    In the digital examples I’m working with I have two types of segmented instantiation issues: by multiplexing and by concatenation. Sometimes I have separately wrapped audio and video tracks that must be multiplexed in order to be a full instantiation and sometimes I have a series of files that must be concatenated to form the instantiation. I suppose a good example would be a cd, as a physical object it can be one instantiation by digitized it typically results in a series of files that must be considered together to form an instantiation.

    In an outside project that I’m working on this issue came up enough to abandon legally following PBCore and changing the asset-instantiation-essenceTrack relationship to asset-instantiation-component-essenceTrack. The component section would list files (or tapes) and how they must interact in order to form the instantiation.

    Any other ideas on how to do this?
    Dave

Write a comment:

Commenting is not available in this section entry.

Options:

Size

Colors