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 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 facing solutions that cater to specific use case(s), ie. Institutional Repositories (IRs), Virtual Research Environments (VREs), Data Curation Systems, etc.
- Hydra ETDs
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.
- Workflow Engines
- Permissions Manager
- CModel-based Constructor
- Version Wiper
- Solr, Lucene
- Bulk Updater
Libraries for consuming Fedora's APIs and/or Frameworks for creating client applications on top of Fedora Repositories.
- Python client code (Oxford, MSKCC)
- Hydra Framework
An encylopedia of instructional documentation, methods, glossaries, examples, pointers to resources that help in learning and using Fedora, integrated applications/service and data examples.
CModels and associated Service Definitions & Service Implementations that can be used with the Fedora CMA
- Djatoka Content Models
This forum is about both workflow (middleware) software and services, also called components, (small chunks of code for performing specific tasks). 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.
- ActiveMQ and other JMS Providers
- Amazon Simple Queue Services
- Stanford's "Work-do" approach
- PID/UUID generator
- generic object updater
- Bots (e.g. work-do bots)
- Enterprise Service Buses (e.g. Apache ServiceMix, JBoss ESB, Websphere ESB)
OSGi plugins and alternatives for components within the core (ie. Triplestores)
- JMS Queues (RabbitMQ)
- Storage Plugins (Akubra)
Means for exposing Fedora Repositories and Fedora Content by structures other than FOXML and Fedora's existing APIs.
- OAI-ORE, OAI-PMH
- Fedora METS Profile
- Fedora ATOM