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:

Damien Moody <[log in to unmask]>

Reply-To:

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

Date:

Thu, 24 Mar 2005 11:01:01 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

If you're really interested, you can get a project started and posted on SourceForge (www.sourceforge.net) for an open-source multi-media metadata/archival project. Interested developers can contribute as they have time and resources to do so. 

Damien J. Moody
Information Technology Services
Library of Congress

>>> [log in to unmask] 03/23/05 1:31 PM >>>

IMHO, in the end databases are absolutely the way to go. However, by
having both a file naming scheme to use with databases and perhaps
'pointer' information in the metadata, the both the files themselves and
the database information would be more useful. I'll pass any/all
comments on to the developers that have volunteering to look into this
for us. Needs to be K.I.S.S. for sure if we don't want to kill the goose
that lays the eggs though.

My thinking was just to suck a few good software developers in and make
a few simple tools available for general use at no / low cost. There
seems, if I read the posts here right, to be a real need for them. Yes,
they aren't hard to write, but fact is, no one is doing and releasing
them for folks outside their organizations to use. It would be a start.

Ultimately, I hope they (the developers) may see that there is an
unfilled need for commercial software to address the needs of the
archiving community, database driven but fully scaleable. The money
available and the size of the archives dictates that for such software
to see general use, it would need to work with several databases (Say,
Access, MySQL, Oracle) Access is cheap and available, but has issues,
particularly with 2+ Gb databases. Oracle is good for huge databases,
but expensive as heck. If a product could be written that allows for
common GUI and data formats in/out, but allowed different database
underpinnings, that would be great. 

-----Original Message-----
From: Association for Recorded Sound Discussion List
[mailto:[log in to unmask]] On Behalf Of John Spencer
Sent: Wednesday, March 23, 2005 11:41 AM
To: [log in to unmask]
Subject: Re: [ARSCLIST] .wav file content information

Hello Richard,

All good points, so let me clarify my earlier statements by commenting
to your reply.  Also, we've built these tools for our internal use, it's
certainly not that hard.

> 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?

> 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.

> 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?

> 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.

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


> From: "Richard L. Hess" <[log in to unmask]>
> Reply-To: Association for Recorded Sound Discussion List 
> <[log in to unmask]>
> Date: Wed, 23 Mar 2005 12:24:48 -0500
> To: [log in to unmask]
> Subject: Re: [ARSCLIST] .wav file content information
>
> Hello, John,
>
> 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.
>
> It was my suggestion to add the import/export utility and to make it 
> easily accessible by standard Microsoft/Open Office tools.
>
> 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.
>
> 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.

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

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