Release date: 21 January, 2016
We are proud to announce the release of Fedora 4.5.0.
- A. Soroka
- Aaron Coburn
- Andrew Woods
- Bethany Seeger
- Unknown User (daniel-dgi)
- David Wilcox
- Esmé Cowles
- Jared Whiklo
- Justin Coyne
- Longshou Situ
- Michael Durbin
- Mohamed Mohideen Abdul Rasheed
- Monika Mevenkamp
- Nick Ruest
- Osman Din
- Peter Eichman
- Ralf Claussnitzer
- Rob Sanderson
- Steven Anderson
The Fedora 4.5.0 release furthers several major objectives:
- Tighten the definition of the RESTful application programming interface (API)
- Further align this API to community standards, including the Linked Data Platform  (LDP) and Web Access Control  (WebAC)
- Enhance preservation capabilities and related documentation
- Improve tooling for external services in the ecosystem around the repository
- Fix bugs
This release is a major release (i.e. 4.5.0 instead of 4.4.1) because there are a several REST API updates that are not backwards compatible with 4.4.0. The theme of these updates is the removal of JCR-related properties that have heretofore been leaked from the Fedora API in the RDF returned to users. Fedora 4 is in no way dependent on JCR, and any mention of JCR found in RESTful responses will be removed. No client code should require updating for this release unless it contains dependencies on JCR-namespaced properties.
See tickets in "Application Programming Interface" below for more details.
Application Programming Interface
One of the technical priorities  of Fedora is to define a well-specified application programming interface (API) against which client applications can be written and future server-side implementations can be created. This Fedora API should be clear and detailed enough such that a corresponding technology compatibility kit  (TCK) would be able to indicate if any Fedora implementation fulfills or diverges from the specification. With this in mind, several issues were addressed in this release that clean up Fedora's RESTful interaction.
Linked Data Platform alignment
Fedora is a Linked Data Platform (LDP) server implementation. This release resolves a bug that relates to the interactions that an LDP client should expect.
Upgrading and Migrating
A primary focus of the ongoing Fedora effort is to facilitate the upgrade/migration of Fedora3 repositories to Fedora4. To this end, a couple of improvements have been incorporated into the "migration-utils " upgration utility, the most notable of which is enabling the utility to optionally be configured with authorization credentials.
In support of Fedora's role in the preservation stack, this release includes investigation and documentation around backup and restore strategies for Fedora's datastore. By default, the database that Fedora currently is configured to use is LevelDB . This release includes documentation and recommendations for performing backup and restore of the internal data Fedora uses in maintaining state.
Web Access Control
Following the initial implementation of the Web Access Control  authorization module, this release furthers that effort with several fixes and improvements. Enhancements include:
WebACLs can now apply to binary resources
An HTTP header, 'On-Behalf-Of', can optionally be configured to offer delegated authorization (documentation )
- A WebACL can be placed on the server acting as the final backstop for authorization decisions for resources that have no other effective WebACL (documentation )
- WebACLs can now include references to 'agentClass' Fedora resources as defined in the Web Access Control specification (documentation )
- An HTTP 'Link' header is included in responses to protected resources pointing to the effective WebACL
Additional documentation of Fedora's implementation of Web Access Controls is available on the wiki .
From the perspectives of code maintainability, intelligibility, replaceability, and clearly defined separation of responsibility, significant focus continues towards increasing the modularity of Fedora. In this release, this effort can be seen in the extraction of the 'transform' and 'id minting' modules into their own projects, and the decoupling of project dependencies.
HTML User Interface
This release includes several useful updates to the HTML user interface:
- Ability to create versions in the HTML UI
- Auto-populate binary resource's 'educore:filename' property with name of file uploaded in the HTML UI
- Limit the number of children of any given resource shown in the HTML UI to 100
Housekeeping and Bugfixes
Numerous refactorings, bugfixes, and clean-up tasks were addressed in this release: