LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


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

CODE4LIB Home

CODE4LIB Home

CODE4LIB  March 2010

CODE4LIB March 2010

Subject:

need a plan for what to code

From:

Adam Wead <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 29 Mar 2010 14:49:57 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (51 lines)

Hello All,

This is my first post to the list so I thought I'd share my current dilemma and put it to you all to see what you might do if you were in my place.  I've really tried to keep this message as short as possible, but it's still too long.  I apologize in advance for that.  I can fill in more detail as the discussion progresses.

I'm the new systems and digital collections librarian for the Rock and Roll Hall of Fame Library and Archives.  I've been in the job for about two months now and have been gathering lots of information on requirements. The Rockhall library will open to the public for the first time at the end of this year and one of the things we're going to need is a digital asset manger. I'll briefly give you a list of some of the requirements that we're looking for, then a list of what possible solutions I've come up with, and close with problems I currently face.

-- DAM requirements --

Currently, we have no digital content, but will be building the infrastructure and workflows necessary to deal with the following:

Video: manage archival JPEG2000 and MPEG4 files created from a variety of analog sources, stream derivatives, handle descriptive metadata as well as text annotations and transcriptions of video segments, and manage new archival and access video objects created from edits of MPEG4 sources.

Audio: manage archival 24/96 broadcast wav files and stream mp3 or equivalent derivatives, handle catalog metadata

Images and Documents: same as audio, but with hi-res tiff images and jpeg/pdf, or similar derivatives

-- Possible solutions (and their drawbacks) --

DSpace: great for images and documents, not so good with video or audio? Also, complexity of video datastreams suggests another solution...

Fedora: flexible enough to handle both JPEG2000 and MPEG4 formats for a single archival video, as well as the text objects and future creation of edited videos from multiple archival sources, similar to WGBH's OpenVault. Downside: Extremely complex and code-intensive to develop and manage.

Proprietary options, ex. ContentDM, DigiTool, and others: I am unaware of their video capabilities at the moment. Image and document data seems to work best. Downside: will likely be cost-prohibitive.

-- Problems --

I need to come up with a realistic goal.  I'm a one-person show here...  While we probably won't be able to afford a nice vendor solution--assuming one exists that fits all of our needs--it would be just as costly in terms of time for me to learn, code and deploy a complete solution using the open source alternatives I've listed above, and I know I've missed some.

I have a lot of catching-up to do. I'm great with unix systems, databases, PHP and Perl; Java and XSLT, not so much. I'm taking a look at Python and Ruby because I can build and deploy things faster with them than PHP or Perl, they already have some Fedora libraries for them, and they are easier for me to wrap my head around than Java, but it will take a while to get fluent in either of them.

So, what would you do?

The idea I have in mind at the moment goes something like this:
First, we're going to purchase a discovery system that will harvest records from our soon-to-be-created MARC library catalog, and soon-to-be-populated archival manager, Archon.  Using that discovery service, we could harvest from one or more DAMs such as DSpace for images and documents, and maybe even audio; and Fedora or some such other system for video.  Fedora would be ideal for our video collection, and everything else for that matter, but very, very time consuming to construct.  Assuming I could build the back-end of fedora enough to allow some rudimentary ingestion of objects, the discovery interface could at least serve those objects out in some way by letting users know that they exist.  Actually streaming the video or audio is another story... but, if the discovery layer is there, I could build a nicer interface for deployment at a later date.

Since we don't open for another 9 months, and have no data to manage yet, that's time to start working on a Fedora backend, or research and create another solution.  I've looked at Fedora front-ends like Fez, Islandora, and Active-fedora, but they are limited to which version of Fedora they can use, and I can't get a feel yet for how they would deal with our requirements.

If we can coast by on a discovery-only type solution, that could give me a year (?) to build a nice interface or retool an existing one for our use.  So, 9 months for a repository, one year for a full interface.  Given my above limitations and desire not to work 80 hours a week, is something like that feasible, slightly ludicrous or completely insane?

If it's not really feasible, then I might be looking at a collaboration with one or more of you fine people, or finding some money from my organization or a grant to help pay one or more of you fine people for help.

So, I close this already way too long email with a final: what would you do?

Many thanks,

Adam Wead


Rock & Roll: (noun) African American slang dating back to the early 20th Century. In the early 1950s, the term came to be used to describe a new form of music, steeped in the blues, rhythm & blues, country and gospel. Today, it refers to a wide variety of popular music -- frequently music with an edge and attitude, music with a good beat and --- often --- loud guitars. 2005 Rock and Roll Hall of Fame and Museum.

This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication.

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

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

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager