Versions Compared

Key

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

...

Table of Contents
minLevel2
outlinetrue
stylenone

New features in DSpace 1.8 (very tentative)

Note

New Features are yet to be determinedfinalized. If you have ideas or code you'd like to see make it into DSpace 1.8.0, please submit it to our Issue Tracker

  • For a list of all features/improvement/bugs currently scheduled for 1.8.0, see the 1.8.0 Version in our Issue Tracker.
  • NOTE: This listing is not finalized, and is likely to change. Not all features/improvements/bugs currently scheduled for 1.8.0 are guaranteed to be in that release.

Developers: Add what you are working on to this list. Please try and link off to additional documentation (on Wiki) or related JIRA issues.

  • More Curation Tools/Plugins (MIT & Others). Obviously, some could potentially even be release asynchronously, and also formally "bundled" with 1.8.0
  • REST API formal release? It missed 1.7.0, but there seemed to be interest there. Volunteer(s) to stabilize/improve for 1.8.0?
  • DSpace "Easy" Installer (Tim Donohue)? See DS-802 and InstallerPrototype for more details
    • Perhaps, alongside this, an easier way to "install" plugins/addons (like Curation Tool plugins)??
  • SWORD Client for DSpace (Robin Taylor, and possibly Richard Jones & Stuart Lewis)
    • would allow DSpace to push/submit content to other SWORD enabled repositories
    • For closed & open access repositories – add a button to transfer content from a closed to an open repository.
  • Context Guided Ingest (Richard Rodgers/MIT) – define an interface, where any submission code can write "attributes" and can retrieve those again later on. Can add any new attributes/values that you want for your submission code. Could be serialized to XML (using input-forms.xml) OR have an implementation of that service that stores in DB (recommended). JPA2?
    • would allow for type-based submission processes (e.g. Theses/Dissertations could have different submission steps than articles/papers).
    • based on the Item type based submission patch picked up by Robin Taylor (initially a GSoC project)
    • seems similar to SimpleStorage Service (user centered storage of state info) – Mark Diggory.
  • Usability improvements / new Theme work (Peter Dietz)
  • Context Sensitive Help for XMLUI (@mire)
  • Discovery Enhancements (@mire)
  • Asynchronous Release Process / Release various modules/addons separate from base install (Mark Diggory/@mire & others)
  • Metadata on all DSpaceObjects (Mark Diggory/@mire & others?)
  • Rewrite of Creative Commons licensing (MIT)??
    • would improve upon the features of the current CC licensing submission step
    • Currently only against XMLUI from MIT
    • Legacy problem – do we update old license to new or not? Currently MIT runs 'split version' with old licenses looking like old, and new look like new.

Organizational Details

Release Coordination

...

Release Process needs to proceed according to the following Maven release process: Release Procedure

Potential Changes and New Features

Note

These changes/features are not finalized. These are just what committers/developers are working on in anticipation for a 1.8 release

Developers: Add what you are working on to this list. Please try and link off to additional documentation (on Wiki) or related JIRA issues.

...

  • Perhaps, alongside this, an easier way to "install" plugins/addons (like Curation Tool plugins)??

...

  • would allow DSpace to push/submit content to other SWORD enabled repositories
  • For closed & open access repositories – add a button to transfer content from a closed to an open repository.

...

  • would allow for type-based submission processes (e.g. Theses/Dissertations could have different submission steps than articles/papers).
  • based on the Item type based submission patch picked up by Robin Taylor (initially a GSoC project)
  • seems similar to SimpleStorage Service (user centered storage of state info) – Mark Diggory.

...