Page History

Versioning & support model

Starting from DSpace-CRIS 7 the project has adopted its own versioning model to assure ensure accurate tagging and tracking of the changes across the different releases. Version numbers will use the following schema year.major.minor. The major number will reset to 01 each year, minor numbers start from 00, for example 2021.01.00, 2021.01.01, 2021.02.00, 2022.01.00, etc.

• Minor versions are expected to be easier to upgrade to, REST API is guaranteed to be backward compatible;
• Major versions are used to highlight important functional or breaking changes. The changelog will highlight the highlights new features and configurations, the configuration and REST API changes and the version of the plain DSpace that is used as basis;
• Year versions are assumed to be major. Minor versions related to the previous year can still occur for security fixand bug fixes.

The latest version is actively maintained by 4Science and community members as volunteer work. Support for past versions will be based on availability of resources and funding from the community. Security fixes will be brought to the current version and the previous major if the current version is a new one (i.e. minor = 00). For example if version 2021.02.00 is the current one, security fixes will be released for both 2021 major 01 and 02, i.e. version 2021.01.01 and 2021.02.01 will be released. Once version 2021.02.01 will be out, security further fixes will come as 2021.02.02.

DSpace-CRIS and DSpace releases are independent, the . The plain DSpace version used as basis for a DSpace-CRIS version will be noted in the changelog . Butbut, whenever appropriate, it will be possible to release an official DSpace-CRIS version based on a DSpace unreleased version (as it was the case for the first DSpace-CRIS 7.0 release). In such situations, the DSpace-CRIS development team will have reviewed the known issues in DSpace and provided custom remediation, workarounds or alternative functionalities to support the relevant use cases. Some limitations can also be acceptable and just noted in the release notes as they may impact edge scenarios or a limited users' base.

...

DSpace-CRIS 2024.01.00 by April July (not to use in production)

...

• Authorship Claim: provide a way for an user to claim its role over a publication, project, etc. (previously named publication/item claim in DSpace-CRIS 5 renamed as it collides with a different feature introduced in DSpace 8)
• FAIRiCat https://signposting.org/FAIRiCat/
• Resourcesync

• collecting the contributor Roles (CredIT support)​

• Enforce validation and management of hierarchical metadata via an application profile also in the administer mode and over the API (PUT)​

• Collect metrics from the OpenCitation​

• Integrate OpenAlex as a live and suggestion provider ​

2024

DSpace-CRIS 7 2023.02.05 July, 11st

This version, released on the 11st July 2024, provides minor improvements and bug fixing.

Key Enhancements

• New configuration introduces identifier subtypes, allowing customization of the name, icon, icon position, and link for each subtype. This includes the update for identifier subtype ROR with identifier.ror rendering type. ROR ID on the OrgUnit details page is displayed following the guidelines
• Improved visualization of related items (crisref rendering) by creating a new view for the crisref link rendering type that displays metadata in a popup when hovering and closes it automatically when moving away
• Improved the item poller org.dspace.app.rest.enhancer.RelatedItemEnhancerUpdatePoller to use its own consumers list. This allows to configure specific consumers for the item poller or add/remove not needed ones
• Implement Domino for Server-Side Rendering stability
• The validation of patch requests against Edit Item, i.e. request generated by the edit of the deposited item via the Edit “submission like” modes, is now using a more relaxed check accepting to update the item also if the resulting item results in a number of validation error not greater than before the patch. Indeed, it is important to note that a deposited item could have existing validation errors under some scenarios. The most common one is that the deposited item has been created in bulk importing data from a legacy system (migration) or has become “invalid” due to changes in the configuration where more validation criteria have been enforced. In all these scenarios, the updated logic allows editing the item without having to solve all the validation errors at the same time, as long as each edit improves the validation status of the item (i.e. reduces the amount of JSON path involved in validation errors)

Minor changes

• Set the alphabetic order in the “Entity type“ dropdown menu during the creation of a Collection
• Reload the page automatically if loading hangs up
• The visibility on the homepage of the AddToAny social sharing bar has been improved
• The user_id field of processes is now set to null when an EPerson is deleted to fix errors in process retrieval
• The search box now dynamically adapts to screen dimensions, ensuring it respects screen borders. On viewports with width less than or equal to medium-sized screens (including tablets and smartphones), the search box width is limited to the lesser of 250px or 40% of the viewport's width
• Removed old occurrence to cris.owner metadata in the Person entity input form
• Improvements of import for bulk file operations

Bug fixes

• CC License step, if mandatory, is now working correctly
• Fixed issue with export process fails when run 2 times on the same item
• Fixed the error of removal of inputs of type “link“ in submission forms
• Fixed Region Name issues with S3 storage configuration
• Resolved the issue of thumbnails not visible in search page by adding a missing check for the default configuration on thumbnails
• Fixed the wrong layout for the item administration page
• Fixes the behaviour of the Altmetric label. It will now only be displayed when the badge is available and contains data
• Fixed search when using directly an ORCID ID instead of the person’s name
• Deleted the z-index rule to make the Export button stay in the background of the dropdown menu in MyDspace
• Fixed an issue where, by pasting a DSpace URL in the address bar, the current page (e.g. in search results) was not retrieved correctly.

DSpace-CRIS 7 2023.02.04 May, 31st

This version, released on the 31st May 2024, provides minor improvements and bug fixing.

Key Enhancements

• Implemented a custom minting feature. It’s now possible to generate DOI identifiers using custom rules before registering them with Datacite. You can define your own rules for creating DOI identifiers based on specific metadata, naming conventions, or other criteria. Default item filters could also be used to specify conditions under which the custom-generated DOI identifier should be applied
• Metadata export has been updated to reflect the latest changes in the Datacite metadata schema v4.5.
• Publisher element will include the ROR identifier if available. ResourceType uses a mapping based on the COAR Resource Type Vocabulary URI instead of the textual value so that it is language insensitive
• Add support for nesting relation and if within a group in the RefererCrosswalk export templates
• The group rendering in the template engine has been extended to manage children group: relation and if. Moreover, placeholders are ignored in export instead of being exported as an empty string
• Added support/configuration for authority lookup to display icons and labels for the source of each retrieved entry
• When using metadata enhancement by the authority lookup, it’s now possible to display and select alternative entries, if any
• We have introduced indexes in the database to optimize the performance of the RelatedItemEnhancerUpdatePoller
• Improved S3 connector:
  • Added support for different storage URL than the default Amazon URL
  • Added support for setting the maximum number of connections
  • Added support for settings the connection timeouts
• Added support for Datadog Real User Monitoring (RUM)
• Ported the SolrSuggestAuthority from the old DSpace version
• Added support for AddToAny plugin for sharing posts on social media

Minor changes

• Highly enhanced logo editing for community and collections
• Changed the dc.subject label from "Subject Classifications" to "Subject Keywords"
• Hidden bitstreams are no longer shown in the item on the full metadata page
• Added support/configuration for authority dropdown to allow the display of icons and labels for each retrieved entry
• Integrated Mathjax for supporting markdown text
• The ROR integration also shows the country when providing suggestions in a field
• When sharing an item page, the correct item thumbnail is exposed according to the cris layout configuration
• Improve the aspect of the “tag” fields used by the submission form
• It’s now possible to hide an item’s bitstream by the administrative bitstream edit page
• Added additional configuration to enable versioning only on custom entities and to allow the creation of new versions of an item also to non-admin (check allowed group configuration)
• Add support for Link input type. In the submission form It’s now possible to use a new input type “link” to store label as metadata value and link as authority. A related rendering type has been added for visualization on the item page
• Configured Versioning BOX on item page for publication entities
• Added dc.type badge on bitstreams during submission
• Added a fallback behavior when some data loading is taking too much
• Added possibility to show entity icon in the submission form when no authority is set
• Languages enabled by default are only:
  • English
  • German
  • Spanish
  • French
• The dc.publisher metadata is now using the OrgUnitAuthority that by default looks in the ROR Registry
• Added separator for Authors' names in the MyDSpace result list
• Adapted text case for attachment rendering to use title case (first letter uppercase)
• Removes duplicated configuration values out of dspace.cfg file

Bug fixes

• Fixed dc.type mapping for Scopus provider
• Fixed the issue of showing a false error message when editing the End User Agreement
• Fixed issue with the cancel button on some administrative pages
• Added mock OpenAIRE connector for integration test to avoid failure due to service down
• Fixed issue that prevented editing and viewing of EULA
• Fixed issue with the download button shown also for not downloadable files
• Fixed issue with the search box in Navbar, which exceeded the small screen borders
• Added missing labels when importing Patents from EPO
• Added missing labels when importing from ROR
• Fixed issue with export in the MyDSpace page
• Fixed issue with Collection exports when metadata has language attributes with underscores
• Exporting collections containing items with metadata with language attributes that include underscores now works properly
• Fixed accessibility problem in the submission form. Changed the color of the icon for better contrast if there is no authority
• Fixed issue with Versioning alert box, which was missing in the item page of versioned item
• Fixed the issue of the Bulk Export failing when exporting a collection with mapped items
• Fixed visualization order of the metrics boxes on the item page
• Fixed issue with Altmetrics badge, which sometimes wasn’t shown properly
• Fixed issue with links in the versioning table, which were not resolved correctly and throws a 404 error when the page is loaded
• Fixed issue with collapsible sidebar of vertical CRIS layout
• Fixed issue with nested fields which were set with a confidence value of -1 when the authority value is chosen from the dropdown
• Fixed errors while running the update-metrics script
• Fixed issue with search page when filtering results via pie chart
• Fixed issue with Community/collection logo. A max width has been defined and small images are no longer stretched

DSpace-CRIS 7 2023.02.03 March, 29th

...