You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Release date: January 24th, 2017

We are proud to announce the release of Fedora 4.7.1.

Resources

Team

Release Manager

Issue Reporters

Summary

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.

Changes

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="http://www.w3.org/ns/json-ld#compacted"

Additionally, with the help of community input, iteration on the Fedora API Specification continues: http://fedora.info/spec/

Deprecations

  • 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.

 

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

 

Messaging

 

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

HTML View

 

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ontology

 

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Housekeeping/Refactoring/Tests/Documentation/Bugs

 

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Complete Listing of Resolved Tickets

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

 

  • No labels