That's a little difficult to make out, but I feel you are comparing apples
to oranges by comparing Blacklight to Omeka or CollectiveAccess.  From what
I've seen, I think CollectiveAccess is a great system.  Omeka is not, nor
designed to be, digital repository software.  I'm not sure it's a good fit
for Adam's requirements.  CollectiveAccess is worth looking into.  It's a
shame more museums don't take open source solutions and CollectiveAccess
more seriously.

Ethan

On Mon, Mar 29, 2010 at 4:48 PM, Carol Bean <[log in to unmask]>wrote:

> Adam,
>
> Oddly enough, I'm evaluating tools and DAM's this week.  I charted the
> Open Source ones that looked possible,  I don't know how this is going to
> come through on email, but this is what I've got:
>
>
>
>
>
>
>
> Software
> Source location
> Platform
> Web
> Based
> MODS/
> METS/
> DC
> Language
> Database
> Includes
> Rep?
> Multiple
> Schemas
> Primary
> Audience
> /Users
> Support
> Omeka
> http://omeka.org/
> Linux
> Y
> DC
> PHP
> MySQL
> Y
> ?
> Staff/
> Public
> Forums/
> List
> Blacklight
> http://projectblacklight.org/
> Any
> Y
> Any
> Ruby
> N
> N
> Y
> Public
> List
> Greenstone
> http://www.greenstone.org
> Any
> Y
> DC
> Java,
> Perl
> ?
> Y
> Configu-
> rable
> Staff/
> Public
> List
> DSpace
> http://www.dspace.org
> Any
> Y
> Any
> Java,
> Perl
> PostGres,
> Oracle
> Y
> Y
> Staff/
> Public
> Forum/
> Lists
> CollectiveAccess
> http://www.collectiveaccess.org
> Any
> Y
> Any
> PHP
> MySQL
> N
> Y
> Staff/
> Public
> Forum/
> Consult.
>
>
>
>
> These are just the preliminary things I was looking at, but in the process
> of getting the chart filled in.  I'm leaning towards Omeka (there's a good
> article on it in D-Lib,
> http://www.dlib.org/dlib/march10/kucsma/03kucsma.html this month), or
> CollectiveAccess.  They look like they will require the least amount of
> work getting it set up, and I'm already familiar with PHP/MySQL. :-)
> (Includes Rep == includes repository)
>
> Hope this helps a little. :-)
>
>
> Carol Bean
> Electronic Resources Librarian
> Federal Courts Library
> 936 Federal Justice Building
> 99 NE 4th Street
> Miami, FL  33132
> 305-523-5958
> 305-523-5962 (FAX)
> [log in to unmask]
>
>
>
> From:
> Adam Wead <[log in to unmask]>
> To:
> [log in to unmask]
> Date:
> 03/29/2010 03:38 PM
> Subject:
> Re: [CODE4LIB] need a plan for what to code
> Sent by:
> Code for Libraries <[log in to unmask]>
>
>
>
> Ethan,
>
> Thanks, yes, I did take a look at this.  I have to pick my battles here. A
> discovery interface is one of the things that we could buy "off the shelf"
> and get a lot of good mileage out of.  I'm devoted to open source and I
> would love nothing more than to roll our own with Blacklight, but that's
> more work on top of the DAM issue.  I chose not to delve into the
> Blacklight option to save myself more time to focus on the asset manager
> issue, which is where I *think* I'll be having to work the most.
>
> Of course, I'm open to suggestions.  Does anyone think it's easier to do
> your own discovery layer than a DAM? Potentially, the money we save not
> buying a discovery layer could go towards buying a DAM.  However, the
> products we're looking have some really great interfaces.  I think I'd be
> looking at an equally difficult challenge trying to emulate some of those
> features on my own.
>
> thoughts?
>
> -----Original Message-----
> From: Code for Libraries on behalf of Ethan Gruber
> Sent: Mon 3/29/2010 3:00 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] need a plan for what to code
>
> Instead of purchasing a discovery system, I recommend using
> blacklight<http://projectblacklight.org/>
>
> Ethan
>
>
>
>
> 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.
>