Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 [3] (LDP) and Web Access Control [4] (WebAC)
  • Enhance preservation capabilities and related documentation
  • Improve tooling for external services live in the ecosystem around the repository
  • Fix bugs
Note

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 [5] 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 [6] (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 and tease out the non-core aspects of the Fedora ontology [7].

Expand
titleRelated JIRA tickets...

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryfilter=13417
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

...

Fedora is a Linked Data Platform (LDP) server implementation. This release fixes resolves a few bugs bug that relate relates to the interactions that an LDP client should expect.

...

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 [87]" upgration utility, the most notable of which is enabling the utility to optionally be configured with authorization credentials.

...

  1. Human-readable serialization to disk: A new component has been added to the suite of Apache Camel recipes that can be employed to react to updates in the Fedora repository by writing the resource RDF (and optionally the binaries) to a specified location on disk. This feature is also now available in the Fedora Vagrant box [8].
  2. Backup strategies: By default, the database that Fedora currently is configured to use is LevelDB [9]. This release includes documentation and recommendations for performing backup and restore of the internal data Fedora uses in maintaining state.

...

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.

...

This release includes several minor, but 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 shown of any given resource shown in the HTML UI of any given resource to 100
Expand

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryfilter=13425
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

...

No Format
[1]  https://wiki.duraspace.org/display/FF/Downloads
[2]  http://docs.fcrepo.org/
[3]  http://www.w3.org/TR/ldp/
[4]  http://www.w3.org/wiki/WebAccessControl
[5]  https://wiki.duraspace.org/display/FF/2015+-+2016+Technical+Priorities
[6]  https://en.wikipedia.org/wiki/Technology_Compatibility_Kit
[7]  httphttps://fedoragithub.infocom/definitions/v4/2015/07/24/repositoryfcrepo4-exts/migration-utils
[8]  https://github.com/fcrepo4-exts/migrationfcrepo4-utilsvagrant
[9]  https://github.com/dain/leveldb
[10] http://camel.apache.org/
[11] http://www.w3.org/wiki/WebAccessControl
[12] https://wiki.duraspace.org/display/FEDORA45/Principal+Providers#PrincipalProviders-DelegateHeaderPrincipalProvider
[13] https://wiki.duraspace.org/display/FEDORA45/Default+Filesystem-based+Policy
[14] https://wiki.duraspace.org/display/FEDORA45/How+to+Use+WebAC+agentClass+Groups
[15] https://wiki.duraspace.org/display/FEDORA45/WebAC+Authorization+Delegate