...
The Fedora community is working to establish a clearly defined specification for the core Fedora services []. This specification will detail the exact services and interactions required for a server implementation to be verified as "doing Fedora".
The primary benefits of this specification include:
- Concrete and common understanding of Fedora's role in an institution's infrastructure ecosystem
- Stable, independently versioned Fedora RESTful API
- Opportunity for alternate Fedora implementations to support different use cases
An article on this effort was recently published in ProgrammableWeb magazine.
Check out the wiki for a full description [2] of the Fedora specification initiative. You are invited to comment on and contribute to the draft specifications [3].
Community-driven Features
API Extension Architecture
API-X stakeholders met on March 18 [4] to discuss a number of topics, including an updated API-X architecture diagram [5] and a document on API-X patterns [6]. A Vagrant/Docker image [7] to demonstrate API-X proof-of-concept implementations was also discussed.
The Sheridan Libraries at Johns Hopkins University was awarded an IMLS grant [] to support development on API-X through December, 2016. The deliverables include:
- Public release of the API-X architectures
- Associated documentation and dissemination
- Some common interest extensions
At the last meeting [] it was decided that a list of tasks would be circulated to the group before being added to an issue tracker for resolution. If you are interested in the API Extension Architecture, please join the discussion on the fedora-community mailing list [8] and attend the next meeting on Thursday, May 12 at 1pm EDT.
Performance and Scalability
A number of test plans [] have been developed by the Performance and Scalability stakeholders met on March 14group, and some initial results are available. At the last meeting [9] to discuss performance benchmarks [10] and testing the new MySQL and PostgreSQL database options. A few tests have been run but the group identified a need for more community participation to execute and document the breadth of test scenariosthe group made plans to document and run additional tests and work on profiling Fedora 4 using YourKit.
If you are interested in Performance and Scalability, please join the discussion on the fedora-community mailing list [11] and attend the next meeting [12] on April 18May 16 at 11am EDT.
Conferences and events
Upcoming Events
Previous Events
CNI
...
LPForum
...
TCDL
...
OR2016
...
Previous Events
Museums and the Web
Museums and the Web [17] will take took place April 6-9 in Los Angeles, CA. This year's conference features featured a presentation by Stefano Cossu (Art Institute of Chicago) and David Wilcox (DuraSpace) on Fedora as the heart of an open source digital asset management system for museums [18].
West Coast Fedora Camp
The West Coast Fedora Camp [19], hosted by the Caltech Library, will take took place April 11-13 in Pasadena, CA. It is based on the inaugural Fedora Camp [20] that was held at Duke University in November. Training will begin with the basics and build toward more advanced concepts–no prior Fedora 4 experience is required. Participants can expect to come away with a deep dive Fedora 4 learning experience coupled with multiple opportunities for applying hands-on techniques working with experienced trainers and Fedora gurus. Registration is now full but please contact Kristi Searle [21] to have your name added to the waiting list and to be informed about future camps!
DC Area Fedora User Group Meeting
The next Spring DC Area Fedora User Group Meeting [22] will take took place April 27-28 at the National Library of Medicine and will include included presentations, project updates, and discussions from local Fedora users. The second day of the event will be featured a Hydra/Fedora 4 workshop led by Esmé Cowles and David Wilcox. Attendance is free so please register in advance [23]!
References
| No Format |
|---|
[1] |