Page History
...
| 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: | |
 | Completely rewritten OAI-PMH Interface
Kindly contributed by Lyncode |
 | Improvements to Solr-based Statistics
Kindly contributed by @mire |
 | Batch import for Bibliographic formats
Kindly contributed by the Greek National Documentation Centre/EKT |
 | Controlled Vocabulary Support for XMLUI
Kindly contributed by @mire's Kevin Van de Velde |
 | Google Analytics support for JSPUI
Kindly contributed by Denys Slipetskyy |
 | Improvements to Authentication by Password
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. | |
 |
Kindly contributed by @mire with the support of the World Bank
Kindly contributed by CILEA |
 |
Kindly contributed by @mire with the support of MBLWHOI Library and Dryad |
 |
Kindly contributed by @mire with the support of the University of Michigan Libraries |
 | Mobile Theme for XMLUI (beta) Kindly contributed by Miami University Ohio |
| |
| ElasticSearch-based Usage Statistics
Kindly contributed by Peter Dietz with the support of Ohio State University Libraries |
| Improvements to LDAP Authentication
Kindly contributed by Samuel Ottenhoff |
| Info | ||
|---|---|---|
| ||
A full list of all changes / bug fixes in 3.0 is available in the History section of the 3.0 Documentation. |
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
- 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])
Release Coordination
Instead of a single "Release Coordinator", the DSpace 3.0 release will be managed by a "Release Team".
...
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
- 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])
Overview
Content Tools