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

Compare with Current View Page History

« Previous Version 42 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 porvides 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.

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
Types of Developers & Skills
Documenting Best Practices
Features & Ideas Tracker
Project Directory (Products)
Challenge Areas
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

Examples of end user apps:

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

  • 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 of Services & Services

  • 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 of Libraries & Frameworks

  • 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 of Content Models

  • Djatoka Content Models

Workflow Components

Small chunks of code for performing specific tasks. These 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 of Workflow Components

  • 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 of Plugins

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

Serializations

Examples of Serializations & APIs

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