Here's on more thing to take a look at... there's a project named Raven (http://github.com/mwmitchell/raven) that one of the Scholars' Lab staff was working on as a research project. Essentially it takes XML (tested with VRA, EAD, and TEI) and builds out a faceted interface from a Solr index along the lines of XTF (just not quite as painful) in a Rails interface. You can check out a sample at http://raven.scholarslab.org/. If you're finding that there's not a solution that's doing what you need, this would be a great place to start building out a custom interface with whatever language you choose.
On 2/8/10 1:39 PM, "Benjamin Young" <[log in to unmask]> wrote:
Have you seen the Exhibit library (part of the Simile project at MIT)?
It provides faceted browsing along with map integration:
It should be fairly easy to add to an existing project as it can consume
a pretty simple JSON format that your app could provide.
Since you're familiar with CakePHP, it would be very easy to turn
parseExtensions on in your routes.php file and provide specific views
for ".json" requests (they'd be stored in views/audio/json/index.ctp for
The Exhibit JSON format is based on some RDF concepts I believe, so if
you're into that at all, it will be doubly enjoyable. :)
Hope that helps,
On 2/8/10 1:31 PM, Ethan Gruber wrote:
> I just checked up on CollectiveAccess' features, and the newest version has
> faceting search/browse now, so you may want to try that. They support
> uploading videos as well. http://www.collectiveaccess.org/about/overview
> On Mon, Feb 8, 2010 at 1:25 PM, Ethan Gruber<[log in to unmask]> wrote:
>> I think Omeka may be a good fit for you, but there currently isn't faceted
>> searching, though a Solr plugin is currently in development. You have a
>> very specific set of requirements, so I'm not sure that any single CMS/DAM
>> will work in precisely the way you want right out of the box, but Omeka
>> could very well be the closest thing. It's written in the Zend framework
>> for PHP. I know that there is great demand for a Solr plugin for Omeka.
>> It's in the Omeka svn repo, but it's not really ready yet for primetime.
>> Ethan Gruber
>> University of Virginia Library
>> On Mon, Feb 8, 2010 at 11:58 AM, Earles, Jill Denae<[log in to unmask]>wrote:
>>> I would like recommendations for faceted browsing systems that include
>>> authentication, and easily support multimedia content and metadata. The
>>> ability to add comments and tags to content, and browse by tag cloud is
>>> also desirable.
>>> My skills include ColdFusion, PHP, CakePHP, and XML/XSL. The only
>>> system I've worked with that includes faceted browsing is XTF, and I
>>> don't think it's well suited to this. I am willing to learn a new
>>> language/technology if there is a system that includes most of what I'm
>>> looking for.
>>> Please let me know of any open-source systems you know of that might be
>>> suited to this. If you have time and interest, see the detailed
>>> description of the system below.
>>> Thank you,
>>> Jill Earles
>>> Detailed description:
>>> I am planning to build a system to manage a collection of multimedia
>>> artwork, to include audio, video, images, and text along with
>>> accompanying metadata. The system should allow for uploading the
>>> content and entering metadata, and discovery of content via searching
>>> and faceted browsing. Ideally it will also include a couple of ways of
>>> visually representing the relationships between items (for example, a
>>> video and the images and audio files that are included in the video, and
>>> notes about the creative process). The views we've conceived of at this
>>> point include a "flow" view that shows relationships with arrows between
>>> them (showing chronology or this begat that relationship), and a
>>> "constellation" view that shows all of the related items, with or
>>> without lines between them.
>>> It needs to have security built in so that only contributing members can
>>> search and browse the contributions by default. Ideally, there would be
>>> an approval process so that a contributor could propose making a work
>>> public, and if all contributors involved in the work (including any
>>> components of the work, i.e. the images and audio files included in the
>>> video) give their approval, the work would be made public. The public
>>> site would also have faceted browsing, searching by all metadata that we
>>> make public, and possibly tag clouds, and the ability to add tags and
>>> comments about the work.