Versions Compared

Old Version 8

changes.mady.by.user Richard Jones

Saved on

compared with

New Version 9

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  • Metadata for All Objects: In the Developers Meeting on Jan 30, 2013, those in attendance discussed a need to release an updated version of this "Metadata for All" pull request (#12).  However, we may need the following:
    • An updated version of the pull request based on current "master"
    • We like the suggestion to rename "schemas" to "namespaces"
    • We'd like it to use "metadatavalue" (and similar) tables rather than creating a new set of Metadata tables specific to other objects.   We understand this may be more disruptive, but it seems odd to have different metadata namespaces
    • If possible we'd want this change to be "backwards compatible" with existing UIs. The goal would be to perform this change in stages – first update the APIs to allow for metadata on all objects, then update each UI one-by-one.  Hopefully we can get all of the UIs done before 4.0
    • We also obviously could use some basic documentation / overview of the thinking behind it, so that we can vote this through sooner rather than later.
  • REST API: We would like to have a stable, tested, read/write, documented, standards based REST API available. Already a working group has been formed to review the existing API's, and to evaluate the existing API's, and to research development of a new API. The API will either be included with the out-of-the-box DSpace, or it will be released a module to be enabled separately. The API working group will host a discussion panel at OR13 during the DSUG track. An API available will enable further re-use of repository data. Existing use-cases of the project range from building JS widgets to spit out a researcher's publications in repository to building a frontend web application.
  • DOI Support (Pascal-Nicolas Becker & Mark Wood)
    • Bram Luyten (Atmire): I think this work looks very promising and would be great to get finalized for 4.0. On the maillinglist, I also saw Pascal Nicholas's wish to get this into 4.0
  • SWORDv2 module update (see Git Repo: https://github.com/nye-duo/DSpace/tree/swordv2contrib), which provides the following improvements: 
    • some general bug fixes including: bitstream url construction, config options, context management and connection pool, ORIGINAL bundle problem (
      Jira
      serverDuraSpace JIRA
      keyDS-1149
      )
    • proper METSDSpaceSIP support in both deposit and update
    • proper authentication for accessing actionable bitstreams (i.e. those that can be replaced via sword), tightened security options around mediated actions, and add extra security to the access of descriptive documents (deposit receipts, statements)
    • more configuration options: bundles to expose in Statements, DepositMO extensions (for individual files), and many more
    • some general refactoring
    • addition of 404 responses where necessary
    • better support for add/replace of metadata, and how metadata updates are handled on archived items
    • update to latest version of Java Server library
    • new bitstream formats in the bitstream registry

...