You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 50 Next »

The Fedora Create Community exists to coordinate and integrate the community of developers working with the Fedora software. The Fedora Repository Service was intentionally designed to be the basis for a variety of information management schemes and, as such, it provides the foundation for a rich variety of software projects.  Take a look at the project types listed below to get a sense of the diverse software being created by this community to work with Fedora.

Each of the category areas are intended to be where the community maintains infomation about software that is available in that area, as well as a hub for ongoing discussion and collaboration. Note that these categories are intended to be useful, not absolute. We will tweak, change and add to them as necessary, but we will also be somewhat pragmatic about we use them.

We've created a map of the structure of Duraspace to give a sense of where this fits within the bigger picture.

How to Participate
Documenting Best Practices
Features & Ideas Tracker
Challenge Areas and Hot Topics

Navigate space

The Fedora Repository Service

 The repository service that is at the core of Fedora is managed by a community-based committers group that maintains the integrity of the core software, both with their own code and by working with other members of the community to integrate their contributions.

End User Apps: Simple Interfaces to Complete Solutions

End-user facing solutions that cater to specific use case(s), ie. Institutional Repositories (IRs), Virtual Research Environments (VREs), Data Curation Systems, etc.

Examples:

  • Islandora
  • Muradora
  • VITAL
  • Hydra ETDs
  • NSDL EduPak
  • RODA
  • Fascinator

Services & Utilities

Self-contained, purpose-specific software that is either used on-demand or acts as an integrated part of overall deployment. These are either run constantly, on an ongoing basis, alongside the repository or invoked by a person.

Examples:

  • GSearch
  • Workflow Engines
  • Permissions Manager
  • CModel-based Constructor
  • Version Wiper
  • Djatoka
  • Solr, Lucene
  • Bulk Updater

Libraries, Frameworks and APIs

Libraries for consuming Fedora's APIs and/or Frameworks for creating client applications on top of Fedora Repositories.

Examples

  • ActiveFedora
  • Python client code (Oxford, MSKCC)
  • Hydra Framework

Content Models

CModels and associated Service Definitions & Service Implementations that can be used with the Fedora CMA

Examples

  • Djatoka Content Models

Workflow Components

This category is both about workflow management software and small chunks of code for performing specific tasks that can be included in organized workflows. Workflow approaches and engines that have been found to be useful by the community are appropriate to this area. It should also be a place for modules of code that can be used & re-used as building blocks in larger processes. Often, these are wrappers for software & utililties that are not Fedora-specific. These are meant to be invoked by an external program or process.

Examples

  • Kepler
  • jBPM
  • Stanford's "Work-do" approach
  • JHOVE
  • PID/UUID generator
  • generic object updater
  • Bots (ie. work-do bots)

Plug-ins

OSGi plugins and alternatives for components within the core (ie. Triplestores)

Examples

  • JMS Queues (RabbitMQ)
  • Triplestores
  • FeSL/Security
  • Storage Plugins (Akubra)

Serializations

Examples

Means for exposing Fedora Repositories and Fedora Content by structures other than FOXML and Fedora's existing APIs.

  • OAI-ORE, OAI-PMH
  • SWORD
  • Fedora METS Profile
  • Fedora ATOM
  • JSON
  • RSS

Recently Updated

  • No labels