Versions Compared

Old Version 24

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 25

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  • OpenAIRE suggestions (Publication Claim): this feature provides a closer integration between DSpace and two OpenAIRE services: the Notification Broker and the OpenAIRE REST API. See Publication Claim documentation for details. OpenAIRE suggestions was made possible thanks to the OpenAIRE Call Innovation funded project "Enrich local data via the OpenAIRE Graph” awarded by to 4Science.
  • COAR Notify Protocol: DSpace 8 has implemented the COAR Notify service Protocol. Refer to DSpace documentation to enable the service. See 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. Documentation available (needs login) at Kim's wiki space: Basic Duplicate Detection for DSpace 8 [MUST BE COPIED IN A PUBLIC SPACE]. Developed by The Library Code with support of TU Berlin, FHNW and ZHAW.
  • New processes overview page organization: to simplify process management throught the administrator UI, the process page has been restructure to splits and group processes into separate sections for running, scheduled completed and failed. These lists update automatically.
  • Better Primary bitstream management: submitters can now define if a bitstream is a "primary" bitstream directly on the submission page once a bitstream has been uploaded. This feature also add a bitstream switch on the download page for each file and anothor in the modal editing window of a specific file, which can be used to make a bitstream the primary one. A primary bitesteam badge now appears aside the file name of the bitstream that has been eventually set as primary.
  • Search Facets: facets can now be used on home page and all Community, and Collection pages.
  • Advanced Search page : DSpace provide an new search page with Boolean options. The operator drop-down list should have four values: Contains, Not Contains, Equals, and Not Equals.
  • Lookup in external sources in the edit item page (Relatinships tab): new relations can be added between items using external sources (i.e. ORCID) in the Edit Item page.
  • Multiple import source (e.g. DOI -> Crossref, DataCite):  a new external source has been added which can be configured to query multiple existing sources simultaneously, returning results from either.
  • Make forgot-password link removable: new configuration has been added 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.
  • Enable lookup for metadata controlled by authority in edit view: User are now able to edit metadata controlled by vocabularies in item's metadata edit form in the same way that is done in submission form. (Donated by Toni Prieto)
  • RIOXX v3 OAI profile support: DSPace can expose metadata in the OAI module in the Research Outputs Metadata Schema (RIOXX) Application Metadata Profile Version 3. See RIOXX version 3 specification for technical details.
  • OAI XOAI Resource Policies for every bitstream: access rights at bitstreams level is available in the OAI XOAI format and has been added to the following OAIS format: OpenAIRE and UKETD/EthOS.
  • OpenAIRE OAI Crosswalk: the OpenAIRE OAI format as been improved to include the access rights conditions at the bitstream level (accessRightsURI attribute of oaire:file element.
  • Research Organization Registry (ROR) Integration: when using configurable entities ROR can now be used as Organization Data Provider. It enable live-import from the ROR API. The ROR icon is also displayed on DSpace organiztion page, as suggested by the ROR-ID guidelines.
  • Recently Added Items display on Community pages: similar to the homepage, new available items are also displayed their respective community page.
  • Item submission process can be configured at community level: In the "item-submission.xml" configuration, it is now possible to map a submission form to a Community. This will cause all descendant collections to use the mapped 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. (Donated by Toni Prieto)
  • DSpace Users correction: enables all logged users to create WITHDRAWN and REINSTATE requests for an item using the quality DSPace assurance event mechanism. Gives the possibility to create or retrieve quality assurance events 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. Once a WITHDRAWN or REINSTATE request is submitted, it can also be also canceled. The feature can be configured (local.cfg). It is disabled by default and require to configure the user group that will be able to make Withdrawn and Reinstate requests, the name of the group must be set qaevents.withdraw-reinstate.group property.
  • DSpace Reports: 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.

...