LISTSERV mailing list manager LISTSERV 16.0

Help for ARSCLIST Archives


ARSCLIST Archives

ARSCLIST Archives


ARSCLIST@LISTSERV.LOC.GOV


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

ARSCLIST Home

ARSCLIST Home

ARSCLIST  March 2005

ARSCLIST March 2005

Subject:

Re: .wav file content information

From:

John Spencer <[log in to unmask]>

Reply-To:

Association for Recorded Sound Discussion List <[log in to unmask]>

Date:

Wed, 23 Mar 2005 14:57:32 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (122 lines)

Richard,

I agree that this is a useful (and hopefully not too boring!) dialogue.

Let me hurl a few softballs back, and please, do understand that I agree
fundamentally with what you are saying.  As they say, "the devil is in the
details".

I truly believe this is a "crisis" for small archives, as the lack of
funding means that structured metadata gets pushed to the back of the bus
(or worse, OFF the bus).

My further comments below.

--
John Spencer
http://www.bridgemediasolutions.com/

>
> Hello, John,
>
> I think we have a really great dialogue going on here. I will elaborate on
> the points, below.
>
> At 12:40 PM 3/23/2005, John Spencer wrote:
>> Also, we've built these tools for our internal use, it's
>> certainly not that hard.
>
> Right, but I think Scott addressed that and what we're trying to do here.
> Mounting heads and aligning tape machines isn't that hard for me, but lots
> of people don't do it themselves. Writing the software would be harder for me.

Understood and agreed.  We have a number of data projects underway where the
archive is doing the "real work" (the actual transfers) and we're helping
out with the IT issues.
>
>>> I think the initial programming project was to provide a manual interface
>>> to the BWF metadata chunk, so that presented with a BWF file, the operator
>>> could read and modify the metadata.
>>
>> How do you control the operator's authority to modify?  Should it be
>> controlled?  Will certain DAW applications overwrite the existing metadata
>> when the file is opened?
>
> I think these tools are intended for smaller archives and people like me.
> Larger operations will require you to use the rigorous tools that they
> develop internally or purchase with rights management.

Here I must disagree.  If I were to share my collection of files with
another institution (small or large), I would have a problem if all present
metadata were modifiable.  DRM or not, the core information should not be
easily changeable.
>
>>> It was my suggestion to add the import/export utility and to make it easily
>>> accessible by standard Microsoft/Open Office tools.
>>
>> Agreed.  I think that is why you see a large "dose" of XML baked into the
>> latest Office flavors.
>
> That is true--I haven't worked with that part of the latest Office all that
> much.
>
>
>>> I do think that there is a place for this. If entity A provides a bunch of
>>> BWF files to entity B, they could stand on their own w/o having the
>>> separate metadata files.
>>
>> If entity A has 500GB of files and entity B would like to research them,
>> wouldn't a 500K database be an easier start?
>
> That wasn't what I meant. Entity A (me) transfers files for Entity B (Sound
> Archive of Nowhere in Particular). I submit these files with
> author/title/whatever metadata in them. It's all tied together. The SA of
> NiP then ingests the files (essence and metadata) into their digital
> storage system.
>
> The Sound Archive of Nowhere in Particular can also send some of these
> files off to the Aboriginal Cultural Heritage Centre of Nowhere in
> Particular without having to extract pieces of a database, etc.

This is another area of concern for me.  How can we assume that SANiP has
their metadata fields laid out in the same manner as ACHCN (Aboriginal
Cultural Heritage Centre of Nowhere in Particular)?  Sounds like there might
be some re-keying (or re-mapping, or crosswalks) of data, which is not my
favorite scenario.  The more times we re-type the same information, the
greater chance for error.  Are we talking about MARC records, DC metadata,
etc.?  The use of XML should remove many of these obstacles, but the same
cannot be said for those using Excel 95 to collect metadata!

I do agree that some metadata should reside in the header, as you could
always open the file up in hexadecimal and read it.  At our office, we call
this "catastrophic metadata" (or "CYA" metadata).  However, I'm somewhat
unsure of your meaning of "tied together".  Are you referring to
1) a wrapper that can be opened automatically (like MXF), or
2) the metadata and audio files reside on the same physical carrier, or
3) all of the metadata would be in the BWF header?

Also, I was under the impression that many smaller archives don't have
"digital storage systems", hence the transitional migration to Gold CD-R (as
evidenced by various discussions on this list).
>
>>> Also, putting metadata into the BWF on the data tape or storage system is
>>> the perfect long-term backup to the main data store. I did not see this as
>>> a search tool, but as part of an archive strategy and an interchange
>> strategy.
>>
>> Agreed.  I was merely pointing out that if you have many data tapes, it is a
>> logistical nightmare to try and reload those tapes to update (1) common
>> field across all of the audio files.
>
> Totally agreed. I see the type of metadata in the BWF file as more
> static/historic. The dynamic data--which, presumably, would be more
> specialized to your collection would live in your database only and not be
> written to the metadata chunk of the BWF files.
>
>
> Richard L. Hess                           email: [log in to unmask]
> Vignettes
> Media                           web:   http://www.richardhess.com/tape/
> Aurora, Ontario, Canada             (905) 713 6733     1-877-TAPE-FIX
>

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

October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 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
November 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
September 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
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager