...
| Note |
|---|
This release is a major release (i.e. 4.4.0 instead of 4.3.1) because there are a two updates that are not strictly speaking backwards compatible with 4.3.0:
Although not a backwards incompatible update in the 4.4.0 release, it should be noted that the Import and Export services [6] have been deprecated due to their reliance on a JCR serialization versus an RDF-centric approach. These services will be supplanted by externalized machinery that transacts in RDF. |
| Expand | ||
|---|---|---|
| ||
... |
Updates
Application Programming Interface
...
In support of Fedora's role in the preservation stack, this release includes two advances.:
- 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 now available in the Fedora Vagrant box.
- Backup strategies: By default, the database that Fedora currently is configured to use is LevelDB []. This release includes documentation and recommendations for performing backup and restore of internal data Fedora uses in maintaining state.
...
Additional documentation of Fedora's implementation of Web Access Controls is available on the wiki [].
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Modularity
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.
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...