Oops formatting went a bit wrong, let me try again so that it's easier to
read..
Hi Pete,
Many thanks for your response. I think we are on the same wave length
with what is possible, but whether or not to go down the route of noting
bitstream formats is another matter. I've a few more comments below...
>I don't know a lot about the MP2T format.
Me either, must say I'm finding audiovisual file formats a bit of a
challenge.
>Is it the case that the video and audio aspects within the AV material
>would be bitstream information as defined by PREMIS?
Yes I think so.
>If so the case, you could have the file level information for the MP2T
>which would look like your TIFF example below, then you can have format
>information for each bitstream too.
>File
><premis:format>
> <premis:formatDesignation>
> <premis:formatName>MP2T</premis:formatName>
> <premis:formatVersion>1</premis:formatVersion>
> </premis:formatDesignation>
> <premis:formatRegistry>
> <premis:formatRegistryName>PRONOM</premis:formatRegistryName>
> <premis:formatRegistryKey>????</premis:formatRegistryKey>
> <premis:formatRegistryRole>specification</premis:formatRegistryRole>
> </premis:formatRegistry>
></premis:format>
>
>Bitstream 1
><premis:format>
> <premis:formatDesignation>
> <premis:formatName>MP3</premis:formatName>
> <premis:formatVersion>1</premis:formatVersion>
> </premis:formatDesignation>
> <premis:formatRegistry>
> <premis:formatRegistryName>PRONOM</premis:formatRegistryName>
> <premis:formatRegistryKey>fmt/134</premis:formatRegistryKey>
> <premis:formatRegistryRole>specification</premis:formatRegistryRole>
> </premis:formatRegistry>
></premis:format>
Yes that’s the kind of thing I was thinking of but also having the
relationship noted in the technical metadata section for the archive file
e.g.
<premis:relationship>
<premis:relationshipType>structural</premis:relationshipType>
<premis:relationshipSubType>includes</premis:relationshipSubType>
<premis:relatedObjectIdentification>
<premis:relatedObjectIdentifierType>WlAbNL_METS_AOAAA000006576</premis:rela
tedObjectIdentifierType>
<premis:relatedObjectIdentifierValue>TrackID
570</premis:relatedObjectIdentifierValue>
</premis:relatedObjectIdentification>
<premis:relatedObjectIdentification>
<premis:relatedObjectIdentifierType>WlAbNL_METS_AOAAA000006576</premis:rela
tedObjectIdentifierType>
<premis:relatedObjectIdentifierValue>TrackID
571</premis:relatedObjectIdentifierValue>
</premis:relatedObjectIdentification>
<premis:relatedObjectIdentification>
<premis:relatedObjectIdentifierType>WlAbNL_METS_AOAAA000006576</premis:rela
tedObjectIdentifierType>
<premis:relatedObjectIdentifierValue>TrackID
572</premis:relatedObjectIdentifierValue>
</premis:relatedObjectIdentification>
</premis:relationship>
The TrackID values relate to bitstream information within PBCore output
e.g.
<pbcore:essenceTrackIdentifier
source="Mediainfo.ID">570</pbcore:essenceTrackIdentifier>
Then have as you suggested..
<METS:techMD ID="techMD_BITSTREAM-1">
<METS:mdWrap MDTYPE="PREMIS:OBJECT">
<METS:xmlData>
<premis:objectIdentifier>
<premis:objectIdentifierType>WlAbNL_METS_AOAAA000006576</premis:objectIdent
ifierType>
<premis:objectIdentifierValue>TrackID
570</premis:objectIdentifierValue>
</premis:objectIdentifier>
<premis:objectCategory>bitstream</premis:objectCategory>
<premis:objectCharacteristics>
<premis:compositionLevel>0</premis:compositionLevel>
<premis:format>
<premis:formatDesignation>
<premis:formatName>MPEG</premis:formatName>
<premis:formatVersion>2</premis:formatVersion>
</premis:formatDesignation>
<premis:formatRegistry>
<premis:formatRegistryName>PRONOM</premis:formatRegistryName>
<premis:formatRegistryKey>???
</premis:formatRegistryKey>
</premis:formatRegistry>
<premis:formatNote>IMX 50
4:2:2@main</premis:formatNote>
</premis:format>
</premis:objectCharacteristics>
</METS:xmlData>
</METS:mdWrap>
</METS:techMD>
>We don't currently write information to the bitstream level at National
>Library of New Zealand.
Yes I’m not sure if we should either but thought I’d try and get an idea
of what others are doing before deciding. Also I would be grateful on any
feedback to the above suggestion.
>In this specific case (video) we would extract the format information of
>the components as technical properties and store it that way (if a
>metadata extractor existed for the format).
We use MediaInfo to do the initial technical metadata extraction and then
we’re thinking of using the following MediaInfo to PBCore 2.0
Instantiation xslt developed by AVPreserve
https://github.com/avpreserve/random-pbcore-metadata-
translators/blob/master/mediainfo2pbcoreinstantiation2.xsl
> Always happy to discuss further -- we struggle (among other things!)
>with bitstream/filestream here.
Yes me too.
Many thanks,
Vicky
|