This documentation was produced with Confluence software. A PDF version was generated directly from Confluence. An online, updated version of this 3.x Documentation is also available at: https://wiki.duraspace.org/display/DSDOC3x
DSpace 3.6 contains security fixes for the XMLUI. To ensure your XMLUI 3.x site is secure, we highly recommend XMLUI DSpace 3.x users upgrade to DSpace 3.6. See the DSpace Release 3.6 Notes for further details. DSpace 3.6 upgrade instructions are available at: Upgrading a DSpace Installation
DSpace 3.5 contains security fixes for the JSPUI. To ensure your JSPUI 3.x site is secure, we highly recommend JSPUI DSpace 3.x users upgrade to DSpace 3.5 (or above). See the DSpace Release 3.5 Notes for further details.
DSpace 3.4 contained security fixes for both the XMLUI and JSPUI. See the DSpace Release 3.4 Notes for further details.
We also highly recommend removing any "allowLinking=true" settings from your Tomcat <Context> settings. Previously our installation documentation erroneously listed examples which included "allowLinking=true", while the Tomcat documentation lists it as a possible security concern.
If you are running an older, unsupported version of DSpace (1.x.x), we highly recommend upgrading to DSpace 3.6, DSpace 4.5 or DSpace 5.5 to ensure your site is secure. Per our DSpace Software Support Policy, all DSpace 1.x.x versions are now End-Of-Life.
If you are considering an upgrade from DSpace 1.x.x, note that, as of DSpace 5, your existing data (i.e. database contents, search/browse indexes) will now be automatically upgraded from ANY prior version of DSpace. Therefore, you may wish to consider upgrading directly to DSpace 5.x, as the 5.x upgrade process is simplified.
Welcome to Release 3.6. DSpace 3.6 provides XMLUI security fixes to the 3.x platform. For full details on the fixes/patches/improvement, please visit:
The following is a list of the new features included for the 3.x platform (not an exhaustive list):
A full list of all changes / bug fixes in 3.x is available in the History section.
The following individuals have contributed directly to this release of DSpace: Linna R. Agne, Jacob Andersson, Jose Blanco, Andrea Bollini, José Carvalho, David Chandek-Stark, Peter Dietz, Mark Diggory, Tim Donohue, Denis Fdz, Sands Fish, Brian Freels-Stendel, Àlex Magaz Graça, Bo Gundersen, Bill Hays, Onivaldo Rosa Junior, Claudia Jürgen, Artur Konczak, Dirk Leinders, Alex Lemann, Ariel J. Lira, Emilio Lorenzo, Bram Luyten, Ivan Masár , João Melo, Samuel Ottenhoff, Nestor Oviedo, Christina Paschou, Scott Phillips, Hardy Pottinger, James Russell, Andrea Schweer, Jonathon Scott, Milton Shintaku, Denys Slipetskyy, Kostas Stamatis, Rania Stathopoulou, Keiji Suzuki, Steve Swinsburg, Robin Taylor, Elias Tzoc, Kevin Van de Velde, Jennifer Whalan, Jennifer Whitney, and Mark H. Wood. Many of them could not do this work without the support (release time and financial) of their associated institutions. We offer thanks to those institutions for supporting their staff to take time to contribute to the DSpace project.
A big thank you also goes out to the DSpace Community Advisory Team (DCAT), who helped the developers to prioritize and plan out several of the new features that made it into this release. The current DCAT members include: Amy Lana, Augustine Gitonga, Bram Luyten, Ciarán Walsh, Claire Bundy, Dibyendra Hyoju, Elena Feinstein, Elin Stangeland, Iryna Kuchma, Jim Ottaviani, Leonie Hayes, Maureen Walsh, Michael Guthrie, Sarah Molloy, Sarah Shreeves, Sue Kunda, Valorie Hollister and Yan Han.
We apologize to any contributor accidentally left off this list. DSpace has such a large, active development community that we sometimes lose track of all our contributors. Our ongoing list of all known people/institutions that have contributed to DSpace software can be found on our DSpace Contributors page. Acknowledgments to those left off will be made in future releases.
Want to see your name appear in our list of contributors? All you have to do is report an issue, fix a bug, improve our documentation or help us determine the necessary requirements for a new feature! Visit our Issue Tracker to report a bug, or join dspace-devel mailing list to take part in development work. If you'd like to help improve our current documentation, please get in touch with one of our Committers with your ideas. You don't even need to be a developer! Repository managers can also get involved by volunteering to join the DSpace Community Advisory Team and helping our developers to plan new features.
The Release Team consisted of Sands Fish, Ivan Masár, Hardy Pottinger, and Robin Taylor.
Additional thanks to Tim Donohue from DuraSpace for keeping all of us focused on the work at hand, for calming us when we got excited, and for the general support for the DSpace project.