0th D.C. Fedora User Group Meeting


Goddard Space Flight Center
Greenbelt, MD


10 June 2009
9:00 am until 1:00 pm


With the breadth of regional activity involving libraries, archives, academics, research, and scholarship coupled with the growing interest amongst federal agencies in opensource solutions, the demand is building for a D.C. area Fedora User Group.

This meeting was both an informal discussion of the Duraspace mission and how it is realized in the Fedora Repository software, as well as a dialogue over Fedora design principles, implementation challenges, and potential future directions.

One of the most promising outcomes of the meeting was the desire and commitment expressed by the community in establishing a local Fedora User Group.

Represented Projects

  1. ...
  2. ...
  3. ...


This is a peppering of notes gleaned from the pre-User Group Meeting:

  • 'DC' datastream: it needs to be made clear to community system designers that the use of the reserved DC datastream is not advised for use beyond its system-management intent
    • Suggestion: rename it from 'DC' to something that expresses the intent ('SYS-MD?').
  • A general, rule-of-thumb guide for deciding on choice of datastream 'Control Group' would be helpful ('X', 'M', 'E', 'R').
  • A general, content modeling guide would be helpful.
  • A deployed, reference implementation of a simple repository with a variety of Object Models, Service Definitions/Deployments, would be helpful.
  • Service Deployments would be more widely adopted/implemented if they were not confined to WSDL.
  • A central access-point/registry of Fedora-related software applications/services would be helpful.
Design Quandary
  • In the scenario of migrating a collection of content from one rendition to the next (be it format type, application version, content detail, or otherwise) is it a viable option to version the earlier sDef/sDep instead of the actual content datastreams?
Potential Topic of Investigation
  • Multi-installation, global PID Generator
  1. Is there a 'purge(d)' state on datastreams?
    • no, the states are ACTIVE, INACTIVE, DELETED
  2. What is the issue (if any) with the Djatoka/Fedora integration?
    • pending