Versions Compared

Key

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

...

There has been significant community discussion about the fact that the metaphorical "4.1" release of Fedora being the release targeting the features and tooling needed for upgrading from Fedora 3 to 4. However, the upgrade tooling is not a part of this current 4.1.0 release. The current 4.1.0 release includes some backwards incompatible changes that has motivated numbering this version as 4.1.0. Specifically, there were minor naming changes to some of the optional configuration properties (see descriptions below) properties as well as naming changes to some of the Fedora ontology terms (see descriptions below). A detailed description of these changes is available on the wiki.

Updates

Ontology

  • Standardized naming of OWL classes...
  • Removed unused terms...
  • Published "indexing" vocabulary...

Performance

  • Transaction memory leaks...
  • Blank nodes now auto-created in a performant hierarchy...

Camel module

...

The Fedora ontology has been updated and improved in several ways. A number of class and property names have been updated based on naming conventions, and several unused terms have been removed. Additionally, the #indexing vocabulary has been published.

Related JIRA Issues

  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1309

  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1261
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1343
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1305
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1285

Performance

Performance continues to be a major priority for Fedora 4, and this release includes two important improvements in this regard. The first is the inclusion of the JBoss Transaction Manager, which (among other things) addressed a memory leak issue with transactions. The second is an improvement to the way blank, intermediate nodes are generated. Maintaining a deep, nested repository hierarchy is a key factor in good performance with Fedora 4, and this improvement ensures that there are never too many nodes beneath a single parent in the repository.

Releated JIRA Issues

  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1272

  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1293
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1258

Camel module

The fcrepo-camel module, a Camel component for interacting with Fedora 4 repositories, was recently promoted from fcrepo4-labs to the main fcrepo4 GitHub repository. This promotion represents the maturity of the module in terms of code coverage, documentation, and usage within the community. This module allows Fedora 4 to leverage the well-supported Camel project for a number of use cases

...

:

  • Deployment into OSGi...
  • Fedora resource streaming...
  • Dynamic Fedora transformations...
  • Integration tests...
  • Both Fuseki and Sesame triplestores...
  • "Prefer" headers...
  • HTTPS connections...
  • Named graphs...
  • Improved documentation and examples...

OAI Provider module

...

OAI Provider module

This release includes two improvements to the OAI Provider module. The first is a refactor of the repository querying logic; unnecessary code was removed to make the module more light-weight and easier to maintain. The second improvement allows administrators to configure

...

repository descriptions in OAI responses, such as repository name, administrator email address, and Fedora version number.

Related JIRA Issues

  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1237
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-1238
    ...

All Issues

Jira
serverDuraSpace JIRA
columnskey,summary,type,assignee,reporter,priority,status,resolution
maximumIssues1000
jqlQueryfilter=13027
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

 

References

No Format
[1]