LISTSERV mailing list manager LISTSERV 16.0

Help for PIG Archives


PIG Archives

PIG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

PIG Home

PIG Home

PIG  November 2011

PIG November 2011

Subject:

Re: Audio chunk as bitstream / boundaries of bitstream

From:

Peter McKinney <[log in to unmask]>

Reply-To:

PREMIS Implementors Group Forum <[log in to unmask]>

Date:

Wed, 23 Nov 2011 02:40:27 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Many thanks to Carol and Seth for replying to my questions. 

I would be really interested in the committee's view on whether there are compliance issues with this set of questions. If we are writing our audio chunk information to the file level, does it mean we are not compliant?

Many thanks once again.

Pete

-----Original Message-----
From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On Behalf Of carol chou
Sent: Friday, 18 November 2011 7:59 a.m.
To: [log in to unmask]
Subject: Re: [PIG] Audio chunk as bitstream / boundaries of bitstream

Hi Peter,

In our institution, we take the approach of implementing PREMIS based
on our analysis of the file format from practical point of view.   For
every file we archive, a file object is used to store the general file metadata such as format, checksum, size, etc.  Format specific metadata is placed inside  the objectCharacteristic of either file or bitstream object, depending on the file format.

For WAVE, the audio metadata is placed inside the objectCharacteristic of the file object.  Our understanding is although the WAVE format specification doesn't explicitly prohibit putting multiple audio tracks inside a WAVE file, in practice, we only see an audio stream inside a WAVE file so that's the most practical way of implementing PREMIS from our perspective.  An audio stream is defined as an audio data stream with all the audio metadata.  So even there are various metadata chucks for the audio data stream inside WAVE, it's all considered as one audio stream.  For broadcast wave, though it contains additional chucks, they are considered as metadata chunk thus is not considered as individual audio stream.

For multimedia formats like AVI and MOV, each audio and video streams will be considered as PREMIS bitstreams because we want to have the ability to characterize each video and audio separately.  Same principle goes to TIFF since a TIFF file can contain more than one image and each image can have different characteristic that we want to capture.  So for a TIFF with just one image, the image metadata will still be put into the object characteristic of a PREMIS bitstream.
JPEG image, on the other hand, is put into file object, because a JPEG file contain only one JPEG image.  For PDF, we put document specific metadata in the file level but the metadata for all the bitstreams like images inside the PDF are considered as bitstream objects.

Attached is am example of our PREMIS document for a WAVE file.  We also have a web service on our web site where you can submit a file and generate a PREMIS document for it.  You may access the web service at description.fcla.edu.

Thank you,
-Carol Chou
Florida Center for Library Automation


2011/11/16 Peter McKinney <[log in to unmask]>:
> Dear Listmembers,
>
>
>
> I wonder if any of you might be able to offer advice. I’m getting 
> confused with information I should be writing to the file level and 
> which to the bitstream level.
>
>
>
> We collect a lot of wave audio files. They are brought into our system 
> and run through format ID and metadata extraction (among other 
> things). My understanding of PREMIS is that the audio chunk of the 
> wave file should be treated as a bitstream. Does this mean that all 
> the technical metadata extracted for that wave file should actually be 
> written to the bitstream level, as it mostly relates to the audio chunk?
>
>
>
> Likewise, how do I deal with the other chunks? If I’m dealing with, 
> say, a Broadcast Wave, are all the chunks bitstream? Meaning, what do 
> I do if I want to extract the metadata from them? Do I write them to a 
> new bitstream object?
>
>
>
> I guess what I’m trying to get at here is what defines whether you 
> have a bitstream or not? Why are the images in a multi-page tiff 
> bitstreams, but the single image in a tiff is not (or is it?)? What if 
> it is a tiff with one image and exif metadata?
>
>
>
> There’s something in this also around tools and systems capabilities 
> as well. The tools we use don’t view files through a PREMIS lens. In 
> addition, the systems and tools that we use do not offer unlimited 
> flexibility and it is conceivable that we will wind up writing 
> conceptually different things to the same PREMIS level as a result. 
> The audio chunk of a Wave file would be described as a bitstream if 
> the file is ingested on its own but the entire file will be considered 
> a bitstream if it is encapsulated in a WARC or Baggit file.
>
>
>
> I’d be really grateful for any thoughts on this topic, especially if 
> those thoughts contain examples!
>
>
>
> Thanks,
>
> Pete
>
>
>
>
>
> Peter McKinney
>
> Digital Preservation Policy Analyst
>
> Preservation Research and Consultancy
>
> National Library of New Zealand Te Puna Mātauranga o Aotearoa The 
> Department of Internal Affairs Te Tari Taiwhenua PO Box 12-340, 
> Wellington 6144
> 77 Thorndon Quay, Thorndon, Wellington 6011
>
> Direct Dial: +64 (4) 462 3931
>
> www.dia.govt.nz
>
>
>
> ====
> CAUTION:  This email message and any attachments contain information 
> that may be confidential and may be LEGALLY PRIVILEGED. If you are not 
> the intended recipient, any use, disclosure or copying of this message 
> or attachments is strictly prohibited. If you have received this email 
> message in error please notify us immediately and erase all copies of 
> the message and attachments. Thank you.
> ====

====
CAUTION:  This email message and any attachments contain information that may be confidential and may be LEGALLY PRIVILEGED. If you are not the intended recipient, any use, disclosure or copying of this message or attachments is strictly prohibited. If you have received this email message in error please notify us immediately and erase all copies of the message and attachments. Thank you.
====

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2024
January 2024
December 2023
August 2023
July 2023
June 2023
March 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
May 2022
April 2022
January 2022
December 2021
October 2021
August 2021
July 2021
June 2021
April 2021
March 2021
January 2021
December 2020
September 2020
August 2020
July 2020
June 2020
April 2020
February 2020
December 2019
November 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager