From David Wilcox, Fedora Product Manager, on behalf of the Fedora Team

The Fedora Team is proud to announce the release of Fedora 4.7.1. on January 24, 2017. Full release notes are available on the wiki. The Fedora 4.7.1 release is a backwards compatible refinement of the previous release, focused on improvements and bug fixes to the REST-API and the core code base.


Release Manager


Issue Reporters

Application Programming Interface

Much of the application programming interface updates in this release relate to correcting response headers.

Support for JSON-LD profiles have also been improved. It has always been possible to retrieve JSON-LD from Fedora using content negotiation. In previous releases, it was possible to retrieve expanded (the default) and compacted JSON-LD profiles. This release adds support for flattened profiles. Users familiar with the JSON-LD serialization will note a change from the "pretty printed" serialization to one that that produces a JSON response without extraneous spaces. Retrieving JSON-LD with an expanded/compacted/flattened profile can be done by adding the following header to the request (replace compacted with flattened or expanded for those other profiles):

Accept: application/ld+json; profile=""

Additionally, with the help of community input, iteration on the Fedora API Specification continues:


  • Support for the previously deprecated File System Federation capability has discontinued and the module has been removed from the fcrepo-webapp-plus project.
  • The /fcr:backup and /fcr:restore endpoints have been deprecated and will be moving to an extension module in a future release of Fedora. This capability will continue to be available until the Import/Export functionality fully supports backup/restore use cases.

Related JIRA tickets


There is no change to the default behavior of message publication by the fcrepo-webapp and fcrepo-webapp-plus: they continue to be produced by an embedded ActiveMQ broker on a topic called "fedora". However, for any applications that are consuming these messages, it is usually better to consume messages from a queue, since there are many circumstances under which messages published on topics can be missed by consumers. This release includes an example for configuring the message publishing machinery to use a queue instead of a topic. Making this change will require customizing the Spring configuration via the system property:


..and using a Spring file such as (noting the highlighted configuration):

It is worth noting that it is also now possible to set the name of the topic or queue as shown in the example above. The default value remains "fedora”.

Related JIRA tickets


For those who use the provided HTML view of Fedora for basic administrative operations, a feature has been added that now allows for including the RDF body of new "container" resources during the creation step. Previously, it was necessary to create an empty "container", followed by a second step of updating the properties of that "container" with a sparql-update request.

Related JIRA tickets

Housekeeping, Refactoring, Tests, Documentation and Bugs

Numerous refactorings, bugfixes, and clean-up tasks were addressed in this release, including:

  • Upgrading the backend ModeShape version to 5.2.0-FINAL
  • Resolving the issue where references to child resources of a deleted container were not being deleted
  • Prohibiting the use of whitespace in the names of version identifiers

Related JIRA tickets

Complete Listing of Resolved Tickets


Leave a Reply

Your email address will not be published. Required fields are marked *