Versions Compared

Old Version 31

changes.mady.by.user Ivan Masár

Saved on

compared with

New Version 32

changes.mady.by.user Hardy Pottinger

Saved on

Key

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

...

Table of Contents
maxLevel3
minLevel2
outlinetrue
stylenone

 

...

New features in DSpace 5.0

...

For all UIs

  • Batch import from Zip files uploaded via the admin interface of either UI
  • Easier Database upgrades, thanks to the inclusion of Flyway, an open-source database migration tool
  • A feature-complete REST API, supporting both read and write operations
  • Linked (Open) Data support
  • Metadata for all DSpace Objects
  • Improved thumbnail generation (via ImageMagick/Ghostscript)
  • Google Analytics integration now tracks "downloads" of bitstreams
  • (Optional) ability to generate citation cover pages on PDFs
  • A place to add third-party plugins

For JSPUI only

  • HTML5-based drag and drop upload interface for uploading bitstreams during submission
  • Per-item configurable visual indicators for browse and search results

For XMLUI only

  • Mirage2 theme, utilizing many modern web design tools and technologies, facilitating a "responsive" web design, adapting to any screen size
  • ORCID integration via an authority plugin, and a new authority cache
  • Serpa/Romeo lookup
  • Rendering MathML code in abstracts
  • Error pages (including page not found) are all styled with your own site styles
  • Collection drop down box performance improvements for repositories with a large number of collections
  • An aspect for adding Google Analytics web usage information to item pages
Note

The list of features below is entirely speculative.  Features are not deemed finalized until the code is in-hand and accepted.

If you are a developer and you'd like to contribute to DSpace 5.0, you can do so by doing the following:

  1. Submit a JIRA ticket describing your contribution, and mark it as being for "5.0"  (this will cause it to auto-appear in the listing below)
  2. As early as possible, share your code via a GitHub Pull Request (or link to it if it's available publicly elsewhere).  Add a link to it in your JIRA ticket.  See Development with Git for more info.
  3. If it's a larger contribution, please provide some documentation (you are welcome to create a new page in this DSpace Wiki), so that we can understand how to use it and configure it.

The earlier you make your contribution known, the more likely it is that it will be accepted into 5.0.  The later you share your code / ideas, the more likely it is that we'll need to reschedule it for a later release.  Usually we need to have the contribution in-hand (or at least be well aware of what it involves) before Summer to ensure it won't conflict with other contributions and can get a thorough review.

Please feel free to list features / contributions you plan to develop for 5.0.  You can also add a JIRA ticket and mark it for "5.0" which will put it on the automated list below (see "Possible JIRA tickets to resolve")

Conceptual Ideas / Proposals

  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-1582
    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 5.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 updates
  • Audio/Video Streaming (RTMP, HLS, DASH) Support
  • Replace Authentication and Authorization code in DSpace with a 3rd-party framework 
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-2049
    (University of Missouri - @mire)
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-2052
     (The World Bank - @mire)
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-2053
     (@mire)
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-2061
     (pbecker)
    • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-1641
     (Longsight)
    The admin can batch import items through a ZIP file through the UI (XMLUI), that contains SimpleArchiveFormat package, the same as is valid for dspace import command launcher.

Release TODO list

  • Solr index format upgrade from 1.6,1.7,1.8 to 5 currently requires manual, undocumented steps (see below). 2 options:
    1. We automate it
    2. We document it
  • Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-2249
    Seems like we have 2 options:
    1. put Tomcat-specific code to JSPUI's web.xml
    2. just document this Tomcat 7-specific warning
      On DevMtg 2014-11-05 we decided to document for RC1 and decide before RC2

...