Page History

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 and Service Components

This category forum is about both about workflow management (middleware) software and services, also called components, (small chunks of code for performing specific tasks) that can be included in organized workflows. Workflow approaches and engines that have automated workflows. Please use a very broad definition since any sort of software which can be used to connect or compose services into larger processes fits in this forum. Equally, any software that has been found to be useful by the community are and can be made into a re-usable component is 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

forum. Both fully automated processes and those which include people should be part of these discussions. It's just about software. The layout of the processes, often called business processs and business integration patterns, are equally part of the discussion. None of these discussion need to be Fedora-specific since this is all about connecting any component from any source including your existing systems.

Examples

• ActiveMQ and other JMS Providers
• Spring
• Amazon Simple Queue Services
• Kepler
• TavernaKepler
• jBPM
• Stanford's "Work-do" approach
• JHOVE
• PID/UUID generator
• generic object updater
• Bots (ie. work-do bots)
• Mule
• Apache ServiceMix
• Enterprise Service Bus

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