Versions Compared

Old Version 56

changes.mady.by.user Andrea Bollini (4Science)

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

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

Version 3.0

...

Note
titleDSpace has changed its release numbering scheme

Wiki Markup
With DSpace 3.0, the DSpace Developers will be changing our release numbering scheme. Release numbers will now only consist of two numbers: {{\[major\].\[minor\]}} (e.g. 3.0, 3.1, 4.0):

  • Major Releases: incrementing the first number ('major') will represent a new MAJOR release of DSpace. A major release may include any or all of the following: 
    • new features
    • system improvements
    • architectural changes
    • bug fixes 
    • (All major releases end in ".0", so "3.0", "4.0", and "5.0" would all represent major releases.)
  • Minor (Bug-Fix) Releases: incrementing the second number ('minor') will represent a new MINOR release of DSpace. A minor release will only include: 
    • bug fixes to an existing major release(For example, "3.1" and "3.2" would represent two minor releases which only include bug fixes to the "3.0" major release.)

There will be a migration path for users upgrading from v1.8.2 to the 3.0 release.

For more information see DSpace Release Numbering Scheme and the initial DSpace 3.0 Announcement

Warning
titleA More Recent 3.x Release Exists: DSpace 3.2

We recommend users upgrade to DSpace 3.2 directly, rather than upgrading to 3.0.  The process to do so is documented at: DSpace Release 3.2 Notes

Tipinfo
titleDSpace 3.0 is a scheduled, "time-based" release

In order to decrease delays in releasing new features and increase transparency, the DSpace Developers have scheduled 3.0 in advance and are basing its features on what we are able to complete within that timeframe.

Scheduling releases benefits us all as it should decrease the delays in releasing new features, and increase the transparency of the development process. The DSpace Developers feel that these benefits will far outweigh the cost of potentially having fewer major features in a given DSpace release. We hope the DSpace Community will also realize the immediate benefits, which should allow them to receive new features more quickly, rather than potentially waiting years for the next major release of the software. The DSpace Developers hope to continue this trend of "time based" releases with all future releases. 

Want to contribute to this release of DSpace? Please see the How to Contribute to DSpace page for ways that you can help out!

...

was officially released to the public on November 30, 2012.

DSpace 3.0 can be downloaded immediately at either of the following locations:

Table of Contents:

Table of Contents
maxLevel3
minLevel2
outlinetrue
stylenone

 

Why 3.0? What happened to 2.0?

In 2011, after much discussion, the DSpace Committers in conjunction with members of the DSpace Community Advistory Team (DCAT) decided to forgo releasing a "DSpace 2.0".

...

Many of the ideas/concepts of "DSpace 2.0" may still be coming to the DSpace platform. But, they will continue to be added incrementally over several releases. The ideas behind "2.0" still live on, even while the release numbering has changed.

...

Note
titleNew Features are yet to be finalized and may change at a moment's noticeDSpace has changed its release numbering scheme

With If you have ideas or code you'd like to see make it into DSpace 3.0, please submit it to our Issue Tracker.
Please see our How to Contribute to DSpace page for more ways (both technical and non-technical) that you and your institution can contribute to 3.0!

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

...

...

  • Wiki Markup
    -HTML pages for OAI generated with client-side XSLT (--[doc|https://wiki.duraspace.org/display/DSDOC3x/OAI#OAI-EnablingOAIPMHInterface]--,- -[DS-1178|https://jira.duraspace.org/browse/DS-1178]--) \[COMMITED\]- Lyncode's OAI 2.0 does it better (see below)
  • Wiki Markup
    SFX button support (institutional branding) ([doc|https://wiki.duraspace.org/display/DSDOC3x/Configuration#Configuration-JSPUI%2FXMLUISFXServer], [DS-820|https://jira.duraspace.org/browse/DS-820]) \[COMMITED\]
  • Wiki Markup
    robots.txt: disallow indexing some dynamically generated pages ([DS-1138|https://jira.duraspace.org/browse/DS-1138]) \[COMMITED\], documentation on robots.txt desirable

...

  • DS-1127: Type based submissions (Pull Request #56)
  • DS-1234: Edit item using the workflow process
  • DS-1232: Select metadata language from submission forms
  • DS-1233: Inline metadata edition for repetible fields in submission forms (currently you have to delete the old value and submit a new one)

...

...

the DSpace Developers will be changing our release numbering scheme. Release numbers will now only consist of two numbers: [major].[minor] (e.g. 3.0, 3.1, 4.0):

  • Major Releases: incrementing the first number ('major') will represent a new MAJOR release of DSpace. A major release may include any or all of the following: 
    • new features
    • system improvements
    • architectural changes
    • bug fixes 
    • (All major releases end in ".0", so "3.0", "4.0", and "5.0" would all represent major releases.)
  • Minor (Bug-Fix) Releases: incrementing the second number ('minor') will represent a new MINOR release of DSpace. A minor release will only include: 
    • bug fixes to an existing major release (For example, "3.1" and "3.2" would represent two minor releases which only include bug fixes to the "3.0" major release.)

There will be a migration path for users upgrading from v1.8.2 to the 3.0 release.

For more information see DSpace Release Numbering Scheme and the initial DSpace 3.0 Announcement

New features in DSpace 3.0

Excerpt
DSpace 3.0 ships with a number of new features. Certain features are automatically enabled by default while others require deliberate activation. 
The following non-exhaustive list contains the major new features in 3.0 that are enabled by default:
Image Added

Completely rewritten OAI-PMH Interface

  • Driver and Open-AIRE compatible
  • Allows for multiple contexts (URL endpoints), each with a different configuration
  • 12 default metadata export formats and easy way to write new ones using XSLT
  • Runs on Solr for great performance, legacy mode over DSpace database supported
  • Even faster thanks to caching

Kindly contributed by Lyncode

Image Added

Improvements to Solr-based Statistics

  • Workflow statistics
  • Search Query statistics
  • Solr version upgrade and performance optimization

Kindly contributed by @mire

Image Added

Batch import for Bibliographic formats

  • Support for

...

  • Endnote, BibTex, RIS, TSV, CSV

...

  • Elastic Search Statistics (screenshots 1, 2)

...

...

...

  • Enhanced batch import routines

Kindly contributed by the Greek National Documentation Centre/EKT

Image Added

Controlled Vocabulary Support for XMLUI

  • Submission form vocabulary lookup
  • Includes The Norwegian Science Index and the Swedish Research Subject Categories

Kindly contributed by @mire's Kevin Van de Velde

Image Added

Google Analytics support for JSPUI

  • support for statistics collection by entering the GA key into dspace.cfg

Kindly contributed by Denys Slipetskyy

Image Added

Improvements to Authentication by Password

  • now stores salted hashes
  • old passwords will continue to work and will be automatically converted to salted hashes on next user login

Kindly contributed by Mark H. Wood with the support of IUPUI University Library

 
The following list contains all features that are included in the DSpace 3.0 release, but need to be enabled manually.
Review the documentation for these features carefully, especially if you are upgrading from an older version of DSpace.
Image Added

Discovery: Search & Browse

Kindly contributed by @mire with the support of the World Bank

Kindly contributed by CILEA

Image Added

Item Level Versioning

  • Create and preserve different item versions
  • Enhanced identifiers
  • XMLUI only

Kindly contributed by @mire with the support of MBLWHOI Library, WHOI, MBL CLI (HPS), ASU CBS and Dryad

Image Added

Advanced Embargo

Kindly contributed by @mire with the support of the University of Michigan Libraries

Image Added

Mobile Theme for XMLUI (beta)

Kindly contributed by Elias Tzoc and James Russell with the support of Miami University

 

Type-based submissions

  • Show or hide metadata fields in the submission forms, based on the type of content submitted

Kindly contributed by Nestor Oviedo and SeDiCI

Image Added

ElasticSearch-based Usage Statistics

  • scalable ElasticSearch backend, runs on embedded node by default 
  • uses Google Chart API for graphs and maps
  • export to CSV available
  • displaying can be either public or restricted

Kindly contributed by Peter Dietz with the support of Ohio State University Libraries

Image Added

Improvements to LDAP Authentication

Kindly contributed by Samuel Ottenhoff

Info
titleMore Information

Additional information about DSpace 3.0 may be found in the 3.0 Documentation.

A full list of all changes / bug fixes in 3.0 is available in the History section of the 3.0 Documentation.

(All non-commercial images in the above table are free-to-use images borrowed from elsewhere. In order: OAI-PMH image, chart image, import icon, dictionary icon, key icon, magnifier icon, documents icon, lock icon, phone icon)

Upgrade Instructions

Organizational

3.0 Decisions To Be Documented:

  • Where should translations of individual modules like Discovery go? Including them in the main messages.xml currently works. This should be answered before freeze time, it already poses another barrier for commiting of translations, see DS-1049, DS-1054. This is a subproblem of i18n Improvements Proposal, but let us not divert this discussion too much to broad topics. ~~helix84
    • Wiki Markup
      ANSWER: In mtg on July 25, we decided the best we likely can do for 3.0 is to suggest that translations of individual modules should just be added to the central messages.xml/messages.properties files. For the full discussion see: [http://irclogs.duraspace.org/index.php?date=2012-07-25] (starts: \[20:57\])
  • Does 3.0 Work with Java 7?
    • Wiki Markup
      ANSWER: Yes, it seems to work with *both* Oracle JDK 7 and OpenJDK 7. We should test & document it works for both. For full discussion see: [http://irclogs.duraspace.org/index.php?date=2012-07-25] (starts: \[20:13\])
    • Actually, I read the log again and nobody said they're running specifically OpenJDK version 7, but I agree we should support it (I will run it when I upgrade my systems). ~~helix84

Accepted Changes

Note

Please note the lists of accepted changes below are dynamically generated from our ticketing system (JIRA). This list may change at any time, and is not finalized until DSpace 3.0 is formally released.

Jira Issues
renderModestatic
columnskey;summary;assignee;reporter
anonymoustrue
titleNew Features in 3.0
urlhttps://jira.duraspace.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+DS+AND+issuetype+%3D+%22New+Feature%22+AND+resolution+%3D+Fixed+AND+fixVersion+%3D+%223.0%22+ORDER+BY+key+ASC&tempMax=1000
Jira Issues
renderModestatic
columnskey;summary;assignee;reporter
anonymoustrue
titleImprovements in 3.0
urlhttps://jira.duraspace.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+DS+AND+issuetype+in+%28Task%2C+Improvement%2C+%22Code+Task%22%2C+Documentation%2C+Sub-task%29+AND+resolution+%3D+Fixed+AND+fixVersion+%3D+%223.0%22+ORDER+BY+key+ASC&tempMax=1000
Jira Issues
renderModestatic
columnskey;summary;assignee;reporter
anonymoustrue
titleBugs Fixed in 3.0
urlhttps://jira.duraspace.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+DS+AND+issuetype+%3D+Bug+AND+resolution+%3D+Fixed+AND+fixVersion+%3D+%223.0%22+ORDER+BY+key+ASC&tempMax=1000

...

Details

Release Coordination

Instead of a single "Release Coordinator", the DSpace 3.0 release will be managed by a "Release Team".

Release Team Leader

...

Sands Fish (MIT)

Release Team Members

...

Sands Fish (MIT), Hardy Pottinger (U of Missouri), Robin Taylor (EDINA, U of Edinburgh), Ivan Masár

Timeline and Processing

Note

It has been decided that DSpace 3.0 will be released in Fall 2012. The exact date is still being worked out, but will likely be in October/November.

Release Timeline (PROVISIONAL):

  August 17, 2012 : Feature Freeze Date

  August 24, 2012 : Final Documentation "Due Date"?

  August 31, 2012 : Release Candidate 1 Release

  September 4-14, 2012 : Testathon

  September 28, 2012 : Release Candidate 2 Release

  October 1-10, 2012 : Final Testing / Bug Fixing

...

  • August 24, 2012 : Feature/Code Submission Deadline - New features must be submitted as a GitHub Pull Request by this date. Any new features submitted after this date will not be considered for 3.0.
  • August 31, 2012 : Final Documentation Due Date - Initial documentation for all new features is due.
  • September 14, 2012 : Feature Freeze - This is an internal deadline for the Committers. This is the date by which the Release Team and Committers will have reviewed via Pull Request, and accepted or rejected all contributions made for the 3.0 release. Rejected code has to wait for the next version of DSpace (or is suggested to be released separate from the current release as a "third party add-on", if applicable).
  • October 8, 2012 : Release Candidate 1 is released
  • October 10-19, 2012 : Test-a-thon
  • October 22-31, 2012 : Bug fixing period
  • October 24, 2012 : Release Candidate 2 is released
  • October 25, 2012 : Release Candidate 2 is on demo.dspace.org
  • October 24-November 1, 2012 : Testing / Bug Fixing
  • November 1, 2012 : Release Candidate 3 is released
  • November 5, 2012 : Release Candidate 3 is on demo.dspace.org
  • November 5-9, 2012 : Test-a-thon (2nd round)
  • November 9-25, 2012 : Testing / Bug Fixing
  • November 30

...

  • , 2012 : 3.0 Final Release

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

3.0 Decisions To Be Documented

  • Where should translations of individual modules like Discovery go? Including them in the main messages.xml currently works. This should be answered before freeze time, it already poses another barrier for commiting of translations, see DS-1049, DS-1054. This is a subproblem of i18n Improvements Proposal, but let us not divert this discussion too much to broad topics. ~~helix84