...
Release Managers
Developers
- ...
Issue Reporters
...
| Expand | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
|
Updates
...
| title | Related JIRA ticket... |
|---|
...
...
| server | DuraSpace JIRA |
|---|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
| key | FCREPO-1593 |
Application Programming Interface
One of the technical priorities [9] 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 cooresponding corresponding technology compatibility kit [10] (TCK) would be able to indicate if the any Fedora implementation fullfills fulfills or diverges from the specification. With this in mind, several issues where were addressed in this release that clean up Fedora's RESTful interaction and tease out the non-core aspects of the Fedora ontology [11].
...
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 [12]" upgration utility.
...
, the most notable of which is enabling the utility to optionally be configured with authorization credentials.
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...