...
| Note |
|---|
This release is 4.3.0 instead of 4.2.1 because there are two non-backwards compatible changes:
An update utility [3] has been included with the release - see the README [4] for how to run the utility to migrate the properties to their new namespaces and update the package names. |
...
Fedora is moving towards a tightly defined, standards-based, set of RESTful services that are supplemented with a pattern of integrating message-driven, asynchronous services for non-core capabilities. The 4.3.0 release includes several updates that move the software in that direction.
- Aligning with LDP [35] by
- Returning a 400 response when illegal triples are not persisted
- Advertising constraints in responses when an update request fails due to a repository constraint
- Showing inbound references for indirectly contained resources
- Tightening the core repository services by
- Forbidding the update of resources that are not the target of the request
- Removing the leakage of the underlying UUID to repository clients
- Allowing "mimeType" and "filename" properties to be mutable
- Moving towards full OSGi [46] deployability for runtime configuration and feature activation
- Ensuring modules are property packaged as OSGi bundles
- Ensuring modules are importing and exporting correct dependencies and services
- Creating a Fedora features.xml for dependable deployment into Apache Karaf [57]
- Enhancing external services with the Apache Camel [68] integration framework by
- Adding a "reindex" endpoint
- Adding a "fixity" invocation service
- Adding support to the REST API for the JSON-LD "Accept" header "profile" parameter
...
A primary focus of the ongoing Fedora effort is to facilitate the upgrade/migration of Fedora3 repositories to Fedora4. To those ends, a number of improvements have been incorporated into the "migration-utils [79]" upgration utility.
- Packaging the utility as a standalone executable application
- Using opaque identifiers for migrated resources
- Adding support for user-provided RDF namespace mappings
- Providing specific mappings of Fedora3 to Fedora4 properties
- Improving support for migrating resources with non-existent datastreams
...
After the completion of the Audit Service [810] sprints this spring, there remained two items to be completed:
...
- Cleaning the Fedora ontology [911] by removing the obsolete "fedora:Blanknode" class
- Creating a JSON-LD @context file for the Portland Common Data Model [1012] ontology
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
The Fedora Java Client library [1113] was updated for this release by
...
| No Format |
|---|
[1] https://wiki.duraspace.org/display/FF/Downloads [2] http://docs.fcrepo.org [3] https://github.com/fcrepo4-labs/fcrepo4-upgrade-utils/releases/tag/fcrepo4-upgrade-utils-4.3.0 [4] https://github.com/fcrepo4-labs/fcrepo4-upgrade-utils/blob/cc77a50b3fac62f791ce2d4fa17cc6b5cfc3ea33/README.md [5] http://www.w3.org/TR/ldp/ [46] http://www.osgi.org/Technology/WhatIsOSGi [57] http://karaf.apache.org [68] http://camel.apache.org [79] https://github.com/fcrepo4-labs/migration-utils [810] https://wiki.duraspace.org/display/FEDORA43/Setup+Audit+Service [911] https://github.com/fcrepo4/ontology [1012] https://github.com/duraspace/pcdm [1113] https://github.com/fcrepo4-labs/fcrepo4-client |