Release 8.0

The version 8.0 release includes support for SAML single sign-on, new pre-installed reports, improvements to keyword search, and numerous bug fixes.

Release date and schedule

CollectionSpace version 8.0 was released in March 2024.

Release notes

Release 8.0 contains breaking changes. If you have customized your installation of CollectionSpace, you may need to update your configuration to work with 8.0. If you have written reports or API integrations, you may need to update them to be compatible with 8.0. Breaking changes are noted below with BREAKING.

New functionality

• BREAKING OAuth 2 authorization code grant is now supported for log in. Support for OAuth 2 password grant has been removed.

• Support for SAML single sign-on has been added. For configuration instructions, see https://collectionspace.atlassian.net/wiki/spaces/UNR/pages/2759950337.

• BREAKING Configuration of CORS allowed hosts has moved from the application-security.properties file to an XML configuration file. For instructions, see https://collectionspace.atlassian.net/wiki/spaces/UNR/pages/2894233605.

• New pre-installed reports have been added:

  • Artwork Description

  • Borrowing Receipt

  • Full Object with Place Details

• Additional fields from Object records are now indexed in Elasticsearch, making them available to the public browser:

  • contentDescription

  • contentEvents

  • contentOrganizations

  • contentPersons

  • rightsGroupList/rightsGroup/rightStatement

  • rightsGroupList/rightsGroup/standardizedRightStatement

  • rightsInGroupList/rightsGroup/rightReproductionStatement

• Various improvements have been made to reports in the public art profile.

• Keyword searches are now accent-insensitive (for example, searching for “sauté” finds records containing “saute”, and vice versa).

• The structure date parser service now accepts dates with roman-numeral months.

• The blob service now supports ranged requests for blob content.

• Detection of images in uploaded media files has been improved.

• Responses to API queries for records that use a given authority item (refObjs queries) now contain a value in each authority-ref-doc-item, containing the full ref name that is used. This allows the requester to determine which term (synonym) of the authority item was used.

• Various single-line note fields now allow multiple lines of text.

Schema changes

• Associated authority fields have been added to Chronology, Person, and Place records.

• BREAKING On the Object record, the Number of Objects field (numberOfObjects) has been replaced with the repeating Object Count group (objectCountGroupList/objectCountGroup). Data in numberOfObjects will be migrated automatically to objectCountGroupList/objectCountGroup/objectCount. Reports and API integrations that refer to numberOfObjects should be changed to use objectCountGroupList/objectCountGroup/objectCount instead.

• BREAKING On the Object record, the Field Collection Place field (fieldCollectionPlace) has been replaced by a repeating field (fieldCollectionPlaces/fieldCollectionPlace). Data will be migrated automatically. Reports and API integrations that refer to fieldCollectionPlace should be changed to use fieldCollectionPlaces/fieldCollectionPlace instead.

• On the Organization record, the Name Note (nameNote) field has been added.

Bug fixes

• On certain profiles, the Occasion field on the Use of Collections record did not allow selecting or creating terms. This now works correctly.

• The controlled object name and controlled material fields are now indexed in Elasticsearch, so their values will now appear in the public browser where expected.

• The Tombstone with Creator and Tombstone with Budget reports now correctly display an image for each Object, when run on multiple Objects.

• BREAKING On Object records, the Computed Current Location field is now set to null (no value) when a location can not be determined, instead of the “~Indeterminate Location~” value, which could not be searched for. Reports and API integrations that depend on the “~Indeterminate Location~” value should be adjusted to accept the null value.

• BREAKING In structured dates returned by the structured date parser service, the earliestScalarValue and latestScalarValue values now contain a time part (set to T00:00:00.000Z), in order to be consistent with structured dates returned from other services. API integrations that use the structured date parser should ensure that the time part is expected.

• The structured date parser service no longer fails to parse certain date formats on February 29.

• In the Accessions, Condition, Deaccessions, and Basic Object with Current Location reports, duplicate rows no longer appear when there are multiple thumbnail images.

• BREAKING Punctuation characters except for " and * in keyword search terms are now ignored (replaced with space), since these were causing unexpected results. This causes the following changes:

  • ' can no longer be used to enclose a phrase search (but " still can).

  • - can no longer be used to negate a search term (but not still can).

  • % can no longer be used for a prefix search (but * still can).

  • \ can no longer be used to escape (the remaining * and ") operators (but there was no practical use for this anyway, since punctuation was never indexed).

• Various big fixes have been made to reports in the public art profile.

• In the Local History and Material Culture profile, the Object Production Place field on the Object record is now correctly indexed in Elasticsearch, so that it no longer appears as a URN in the public browser.

• Contrast ratio has been improved in some user interface text.

Other

• BREAKING Version 2 of the public gateway application (cspace-public-gateway) has been released, and that version must be used when it is deployed to the same servlet container as CollectionSpace 8. Running the public gateway as a standalone application (with embedded Tomcat) is no longer supported.

Upgrading to v8.0

Instructions for upgrading to v8.0 can be found on our Documentation wiki.