Fedora "Create" Community: Working together to Get Stuff Done
(formerly Solutions Integration Community)
Regardless of how we are using Fedora, or what types of content we are putting into it, we all have a number of common technical challenges that we must all overcome. One of the greatest strengths of Fedora Commons is the fact that it has an active and innovative community of software architects, developers, archivists and librarians working to tackle those challenges in ways that range from pragmatic to visionary.
We've formed a Solutions Community around identifying, documenting, discussing, and solving these technical challenges that we must all face.
Read about the Solutions Integration Community if you would like to know more about the community, this section of the wiki, and how you can get involved.
...
- Indexing and Search
- User Management & Access Controls
- Filtering Search Results by Access Rights
- Scalability, Replication, Redundancy and Failover
- Backups and Disaster Recovery
- Content Modeling and the CMA
- Writing Client Applications for Fedora: Choosing Frameworks, Languages, etc.
- Managing Large Files
- Video
- ORE & Atom
- Workflow (people-based)
- Workflow (service orchestration)
...
- Choosing Frontend UI, and when to write one from scratch
- Understanding the technological differences between Fedora and other Repository or Content Management Systems.
- Understanding the Fedora Data Model
- SOA/WOA best practices
- RDF Best Practices
- Metadata Best Practices
Resources
Wiki: Fedora Developers Forum
Fedora Commons Developers Mailing List
...
Visit the recommended reading, which contains some recommended posts from many of these blogs (this is only updated periodically).
Presentations
- NLM Digital Repository Server Architecture - This presentation is from the Washington, DC Fedora User's Group meeting in January 2011, and describes NLM's server architecture and approach to redundancy, replication and failover in the initial implementation of NLM's repository.