Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
Upgrade from any past version of DSpace!
Installing DSpace provides an overview of the DSpace 8 installation process and all prerequisite software. You should review this before attempting an upgrade, in order to ensure you are running the required versions of Java, Node, etc.
Upgrading DSpace provides a guide for upgrading from any old version of DSpace to v8. As in the past, your data migrates automatically, no matter which older version you are running. However, as the old XMLUI and JSPUI user interfaces are no longer supported, you must switch to using the new User Interface.
8.0 Release Notes
DSpace 8.0 contains new features :
- Openaire suggestions (publication claim): The features included in this PR are the result of the OpenAIRE Call Innovation funded project "Enrich local data via the OpenAIRE Graph” awarded by 4Science (https://www.openaire.eu/open-call-winner-phase-1-4science). It provides a closer integration between DSpace and two OpenAIRE services, the Notification Broker and the OpenAIRE REST API. Detailed documentation about the aims of the project, the implementation and the configuration options is available at https://4science.github.io/oaire-eld/#/publication-claim
- COAR Notify Integration: Quality Assurance Events and LDN Message Protocol. Technical implementations documented here : COAR Notify Documentation
- Basic Duplicate Detection in submission and workflow: This feature introduces basic Duplicate Detection into DSpace submission and item links, using Solr's ability to search by levenshtein distance. Draft documentation available (needs login) at Kim's wiki space: Basic Duplicate Detection for DSpace 8
- Processes overview page split into sections: splits the process overview page up into separate sections for running, scheduled completed and failed. These lists update automatically.
- Primary bitstream management improvment: allow sumitter to define if a bitstream is a "primary" bitstream directly on the submission page once a bitstream has been uploaded. + Added a bitstream switch on the download page for each file and also add a switch in the modal editing window of a specific file, which can be used to make the bitstream the primary. Added a badge primary aside the file name for the bitstream that has been eventually set as primary
- Search Facets display on all Home, Community, and Collection pages: Added the search section as the default community page tab and moved the community en collection lists to a separate tab. I replaced the recently added section on the collection page with the same search section.
- Advanced Search page with Boolean options: The operator drop-down list should have four values: Contains, Not Contains, Equals, and Not Equals. The operator drop-down list should move above the text field in the Advanced Search section. The advanced search options should be removed from individual facets (Author, Subject, etc)
- Migrate from Joda-Time to java.time: as required by Joda-Time website, using
java.time
: - Import from external source on edit item > relationships: The lookup in external sources is not available in
Edit Item > Relationships
. We can only add internal DSpace entities there as a linked item, now we will also be able to import a new item from an external source there. - UI should have a ProcessPollingService for common polling activities (feature process polling):
dspace-angular
should have aProcessPollingService
which can be used to check if a specific activity has completed. - Multiple import source (e.g. DOI -> Crossref, DataCite): Adds a new external source which can be configured to query multiple existing sources simultaneously, returning results from either.
- [Port main] i18n production improvements: TO IGNORE ? (port from 7.6.10
- Make forgot-password link removable: new configuration to checks for the forgot-password feature. The same feature can also check, whenever is provided, that the user is able to update its password.
- Unable to lookup for metadata controlled by authority in edit view: Implement vocabulary value selectors in item’s metadata edit form + be able to edit metadata controlled by vocabularies in item's metadata edit form in the same way that is done in submission form.
- Header and navbar refactoring: change both header and footer structure to make easier to handle dspace and base themes
- Migrate to standalone components, directives, pipes: Having standalone components, directives and pipes makes it easier to think about the dependencies of the components and are easier to refactor.
- RIOXX v3 OAI profile support: implements a RIOXX v3 compliant OAI profile. RIOXX stands for Research Outputs Metadata Schema and the latest version of the specification is available at https://www.rioxx.net/profiles/v3-0-final/ ATTENTION: ALSO FIXE AN OPENAIRE BUG (MAYBE ADD AS SEPARATE LINE)?
- ROR Integration: introduce a new
Organization
Data Provider for the live-import that retrieves entries using the ROR API . + - Identifier Visualization : introducesi18n-labels
and visualization of the ROR identifier inside the organization page, as suggested by the ROR-ID guidelines - Alteration to index-discovery script to only (re-)index specific type of IndexableObject: https://github.com/DSpace/DSpace/pull/9243 Merging immediately. But, I'm also flagging as "needs documentation" as we should update the indexing script docs for DSpace 8 in Discovery#DiscoverySolrIndexMaintenance If you have a chance to add this new param to those docs, I'd appreciate it.
- Embedding data doesn't work for some rest objects: Rest controllers actually don't use the singular name, but the plural name in their beans. It would be better to normalise this behaviour so that the repositories also work like this. This would also mean that we won't have to use the
makeSingular
method anymore to find the beans. To avoid Some rest objects to throw a 404 error when you try to embed data. - Add "Recently Added Items" to Community pages: similar to the homepage, new available items are also displayed their respective community page.
- Configure Item submission process at community level: allows to use a community handle to map the descendant collections to an item submission process. This can be useful for repositories where top-level communities represent different document types or scopes and descendant collections should share the same submission process.
- DSpace Users correction : Add support for a DSpace internal quality assurance source + Create a DSpace Users correction source with REQUEST/WITHDRAWN and REQUEST/REINSTATE topics + WITHDRAW / REINSTATE requests for an item: "DSpace Users" driven quality assurance source named "DSpace User Corrections". This gives the possibility to create quality assurance event, retrieve quality assurance event created by the current user and delete them. The DSpace User Corrections manage different types of correction providing future proof extensibility that can be discovered via the proposed new REST API correctiontypes endpoint. Enables all logged users to create WITHDRAWN and REINSTATE requests for an item using the quality assurance event mechanism.
Once a WITHDRAWN or REINSTATE request is submitted, it can also be also canceled. Config in local.cfg file disable by default necessary to configure the user group that will be able to make Withdrawn and Reinstate requests, the name of the group must be set to this property qaevents.withdraw-reinstate.group = - Expose 'creationTime' property on Process object and add it to '/search/byProperty' sort options: exposes the
creationTime
property on Process objects and adds it to the possible sort options for/processes/search/byProperty
. AsstartTime
andendTime
are nullable, processes with these properties set tonull
can't be sorted properly. Every process does have acreationTime
however, making for a more reliable sorting mechanism. - OAI: Resource Policies for every bitstream at XOAI: have specific access rights at files level to be available in the OAI interface Also relates to OpenAIRE and UKETD/EthOS.
- DSpace Reports: The Beta release of the DSpace reports only provides the ability to run the reports and display the results in the Angular UI. As such, reports feature must be used with caution. The reports are an Administrator tool. There are 2 reports: Filtered Collection and Metadata Query. See Report documentation for mode details.
8.0 Configurations Removed (Are there any?)
Those Configurations removed included:
- Within the
[dspace]/config/
directory, these are the configuration files which were deleted:dc2mods.cfg
input-forms.xml / dtd
(REPLACED BY submission-forms.xml, see Submission User Interface)log4j.properties
(REPLACED BYlog4j2.xml
)log4j-console.properties
(REPLACED BYlog4j-console.xml
)log4j-solr.properties
(no replacement as Solr now must be installed separately)news-side.html
news-top.html
news-xmlui.xml
workflow.xml
(REPLACED BY./spring/api/workflow.xml
)xmlui.xconf / dtd
emails/bte_*
(BTE import framework was removed in favor of Live Import from external sources)modules/controlpanel.cfg
modules/elastic-search-statistics.cfg
(Elastic Search support was removed in favor of Solr)modules/fetchccdata.cfg
modules/publication-lookup.cfg
spring/api/bte.xml
(BTE import framework was removed in favor of Live Import from external sources)spring/oai/*
(OAI is now part of the backend "server webapp" and needs no separate configurations)spring/xmlui/*
A full list of all changes / bug fixes in 7.x is available in the Changes in 7.x section.
8.0 Acknowledgments
Major Contributing Institutions
The following institutions have been major code contributors to the DSpace 8 release (in general)
Financial Contributors
We gratefully recognize the following institutions who together have generously contributed financially to support the DSpace 8 and individuals who devoted time to fundraising:
Frontend / User Interface Acknowledgments [BASED ON DSpace 7, TO BE REVISE]
The following individuals have contributed directly to the new DSpace (Angular) User Interface in this release (ordered by number of GitHub commits): Giuseppe Digilio (atarix83), Kristof De Langhe (Atmire-Kristof), Lotte Hofstede (LotteHofstede), Art Lowel (artlowel), Marie Verdonck (MarieVerdonck), Julius Gruber (Flusspferd123), Yury Bondarenko (ybnd), William Welling (wwelling and wellingWilliam), Yana De Pauw (YanaDePauw), Tim Donohue (tdonohue), Alessandro Martelli (alemarte), Michael Spalti (mspalti), Jonas Van Goolen (jonas-atmire), Laura Henze (lhenze), Dániel Péter Sipos (dsipos-dev), Samuel Cambien (samuelcambien), Bruno Roemers (bruno-atmire), Matteo Perelli (sourcedump), Bram Luyten (bram-atmire), Ben Bosman (benbosman), Terry Brady (terrywbrady), Raf Ponsaerts (Raf-atmire), Danilo Di Nuzzo (ddinuzzo), Andrea Chiapparelli (andreachiapparelli), Antoine Snyers (antoine-atmire), Corrado Lombardi (corrad82-4s), Courtney Pattison (courtneypattison), Àlex Magaz Graça (rivaldi8), Chris Wilper (cwilper), Christian Scheible (christian-scheible), Andrew Wood (AndrewZWood), Reeta Kuuskoski (reetagithub), Vítor Silvério Rodrigues (vitorsilverio), Alexander Sulfrian (AlexanderS), muiltje, José Carvalho (josekarvalho), Claudia Jürgen (cjuergen), fernandaruizm, Ivan Masar (helix84), Paulo Graça (paulo-graca), Philip Vissenaekens (PhilipVis), Nagy Akos (akoscomp), Kevin Van de Velde (KevinVdV), Sascha Szott (saschaszott), Mohamed Mohideen Abdul Rasheed (mohideen), David Cavrenne (davidatmire), Hardy Pottinger (hardyoyo), Luca Giamminonni (LucaGiamminonni), Mateus Mercer (MatMercer), Denijs Balodis (Denijsb), Pascal-Nicolas Becker (pnbecker), Mikus Zarins (MixonZ), marciofoz, Andrea Bollini (abollini), Martin Walk (MW3000).
Backend / REST API Acknowledgments [BASED ON DSpace 7, TO BE REVISE]
The following individuals have contributed directly to the DSpace backend (REST API, Java API, OAI-PMH, etc) in this release (ordered by number of GitHub commits): Raf Ponsaerts (Raf-atmire), Tim Donohue (tdonohue), Andrea Bollini (abollini), Michele Boychuk (Micheleboychuk), Mark Wood (mwoodiupui), Marie Verdonck (MarieVerdonck), Ben Bosman (benbosman), Luigi Andrea Pascarelli (lap82), Terry Brady (terrywbrady), Tom Desair (tomdesair), Yana De Pauw (YanaDePauw), Chris Wilper (cwilper), Peter Nijs (peter-atmire), Kevin Van de Velde (KevinVdV), Bruno Roemers (bruno-atmire), Giuseppe Digilio (atarix83), Pasquale Cavallo (pasqualecvl), Jelle Pelgrims (jpelgrims-atmire), Andrew Wood (AndrewZWood), Samuel Cambien (samuelcambien), Antoine Snyers (antoine-atmire), Kim Shepherd (kshepherd), Yury Bondarenko (ybnd), Michael Spalti (mspalti), Alessandro Martelli (alemarte), Oliver Goldschmidt (olli-gold), Jonas Van Goolen (jonas-atmire), Kristof De Langhe (Atmire-Kristof), Alexander Sulfrian (AlexanderS), Patrick Trottier (PTrottier), Pablo Prieto (ppmdo), Hardy Pottinger (hardyoyo), Pascal-Nicolas Becker (pnbecker), William Tantzen (tantz001), Paulo Graça (paulo-graca), Luca Giamminonni (LucaGiamminonni), Ivan Masar (helix84), Hrafn Malmquist (J4bbi), Ian Little (ilittle-cnri), Anis Moubarik (anis-moubarik), Claudia Jürgen (cjuergen), Alan Orth (alanorth), xuejiangtao, Danilo Di Nuzzo (ddinuzzo), James Creel (jcreel), Marsa Haoua (marsaoua), Philip Vissenaekens (PhilipVis), Miika Nurminen (minurmin), Bram Luyten (bram-atmire), Christian Scheible (christian-scheible), Nicholas Woodward (nwoodward), József Marton (jmarton), Mohamed Mohideen Abdul Rasheed (mohideen), Saiful Amin (saiful-semantic), Àlex Magaz Graça (rivaldi8)
Additional Thanks
Additional thanks to our DSpace Leadership Group and DSpace Steering Group for their ongoing DSpace support and advice. Thanks also to LYRASIS for your leadership, collaboration & support in helping to speed up the development process of DSpace 8.
Thanks also to the various developer & community Working Groups who have worked diligently to help make DSpace 8 a reality. These include:
- DSpace 7 developers group
- DSpace Community Advisory Team (DCAT) - This team helped organize/lead the DSpace 8.0 Testathon (to bang on the system to find any last bugs), and they also provided us with advice on features, etc.
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. Acknowledgments to those left off will be made in future releases.