Versions Compared

Old Version 48

changes.mady.by.user Thorny Staples

Saved on

compared with

New Version 49

changes.mady.by.user Thorny Staples

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section

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.

Column
width40%

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
Column
width40%

Content Models

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

Examples

  • Djatoka Content Models

Workflow Components

Small This category is both about workflow management software and small chunks of code for performing specific tasks . These 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

...