...
A. Soroka, University of Virginia
- Aaron Birkland, Johns Hopkins University
Unknown User (acoburn), Amherst College
Aaron Elkiss, University of Michigan
- Andrew Woods, DuraSpace
- Benjamin Armintor, Columbia University
- Bethany Seeger, Amherst College
- Bill Branan, DuraSpace
- Esme Cowles, Princeton University
- Jared Whiklo, University of Manitoba
- Michael Durbin, University of Virginia
- Michael J. Giarlo, Stanford University
- Mirek Simek, University of Chemistry and Technology, Prague
- Mohamed Mohideen Abdul Rasheed, University of Maryland
- Nick Ruest, York University
- Peter Eichman, University of Maryland
- Yinlin Chen, Virginia Tech
Issue Reporters
...
- Tighten the definition of the RESTful application programming interface (API)
- Refining the messaging service
- Use performance test fixtures to examine the effects of different backends
- Improve durability by encouraging the use of MySQL and PostgreSQL backends
- Deprecation of legacy Transform service
- Fix bugs
This release will be the last release built against a version of Modeshape that uses Infinispan for data storage.
Excerpt |
---|
Note |
---|
This release is a major release (i.e. 4.6.0 instead of 4.5.2) because there are several REST API updates that are not backwards compatible with 4.5.x. The following, deprecated, REST endpoints have been removed: - /fcr:nodetypes
- /fcr:export
- /fcr:import
Additionally, the user-provided repository.json configuration file must be set as a system property. Unlike in previous releases, there is no default value. See Application Configuration for more details. The other non-backwards compatible change is the update to the messaging format, detailed in the section below. |
|
Changes
Messaging 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.
An important particular change to note here is the move to use only weakly-validated ETags for RDF resources, in line with a correct interpretation of the HTTP specifications. This means that such ETags are no longer suitable for use with the If-Match
request header. Additionally, the extensions fcr:transform
has been marked as "deprecated" in favor of more robust tooling found in fcrepo-ldpath
.
Expand |
---|
title | Related JIRA tickets... |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | filter=13712 |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
|
|
...
Expand |
---|
title | Related JIRA tickets... |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 50 |
---|
jqlQuery | filter=13711 |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
|
|
Complete Listing of Resolved Tickets
Expand |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 70 |
---|
jqlQuery | filter=13800 |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
|
|