fedora4lib

Fedora at code4lib 2013

Hacking Fedora 4

We can rebuild it. We have the technology. Better…stronger…faster.

Where is Fedora 4 today?

  1. Rapid prototypes of RESTful services

    a. fcrepo 3.x “legacy” API

    b. CDL Storage Services API (i.e. Merritt)

    c. An “experimental” pluggable Dublin Core derivation service

    d. Content-negotiation

  2. A commitment to asynchronous infrastructure

    a. Message queues to index content into external services (e.g. 4store, Solr, etc)

    b. Asynchronous storage (e.g. Amazon Glacier)

    c. Consuming API requests via message queues

  3. Support for Ruby, Python & Scala

    a. JRuby and Scala examples for processing object events and manipulating content

  4. Modern approaches to scaling

    a. replicating and distributing digital objects across multiple nodes for throughput and high-availability

Where is Fedora 4 going?

We very much believe that “The coolest thing to do with your data will be thought of by someone else”, and we know you’ve got ideas you couldn’t realize on Fedora 3.

What do you want your repository backend to do? Can you hack it into the Fedora 4 prototype by Thursday?

The best code submission for indexers, web APIs, message listeners or improvements to the prototype will win a $500 cash prize, and the second place entry will win $250. Pull requests welcome!

For more information, visit us at Fedora House on Monday and Tuesday nights!