Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

width60%

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.

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.

people who are working on anything external to the Core Repository.

We've created a map of the 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

Section
Column
width40%

End User Apps: Simple Interfaces to Complete Solutions

Column
width5%
Column
width35%
Navigate space
Page Tree Search
Page Tree
Section

Project Types

For the sake of sanity, we break these out into Complete Solutions, Services & Utilities, Libraries & Frameworks, Content Models, Workflow-ish Components, Plugins, Serializations & APIs.

Currently the most complete listing of available software is in our community software registry.

Column
width40%

Complete Solutions

Examples of 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.

Islandora

Examples:

  • MuradoraeSciDoc
  • VITAL
  • Hydra ETDs
  • NSDL EduPak
  • RODA
  • FascinatorIslandora

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

FedoraPedia

An encylopedia of instructional documentation, methods, glossaries, examples, pointers to resources that help in learning and using Fedora, integrated applications/service and data examples.

Click here.

Column
width40%

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

Small This forum is about both workflow (middleware) software and services, also called 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). Please use a very broad definition since any sort of software that 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 and can be made into a re-usable component is appropriate to this forum. Both fully automated processes and those which include people should be part of these discussions. Also, it's not just about software! The layout of the processes, often called business processes 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
  • Taverna
  • jBPM
  • Stanford's "Work-do" approach
  • JHOVE
  • PID/UUID generator
  • generic object updater
  • Bots (iee.g. work-do bots)
Plugins
  • )
  • Enterprise Service Buses (e.g. Apache ServiceMix, JBoss ESB, Websphere ESB)

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

& APIs

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

Section
Column
width60%
recently-updated