1. CollectionSpace
  2. Current and Past Releases

Release 6.0

Created by Ray Lee
Last updated May 29, 2020

The version 6.0 release includes the ability to search on any field in a record, a public-facing browser, new (to version 6) profiles, and many other new features and bug fixes.

Release date and schedule

CollectionSpace version 6.0 was released in May 2020.

September 16, 2019: Development Begins
February 2020: Development Ends
March 2020: QA Testing Begins
April 2020: QA Testing Ends
April 2020: Release
April 2020: Formal Announcement to the Community

Release notes

Release 6.0 contains a number of breaking changes. If you have customized your installation of CollectionSpace, you may need to update your configuration to work with 6.0. If you have written reports, you may need to update those reports to be compatible with 6.0. Breaking changes are noted below with BREAKING.

New profiles

  • The Herbarium profile, previously available only for CollectionSpace 4, is now available for CollectionSpace 6. 
  • The Botanical Garden profile, previously available only for CollectionSpace 4, is now available for CollectionSpace 6. 

New functionality

  • BREAKING Any field is now searchable in advanced search. The configured advanced search fields for a record type are now only used as defaults if a user has not added/removed fields to be searched. 
    If you have customizations, changes may be required to make fields appear correctly on the advanced search form:
    • Many fields now have fullName or groupName messages in addition to the name message. If you changed the labels of any fields by customizing the name message, you must now also customize the fullName/groupName message if one exists for the field, so that your customized label will appear on the advanced search form. Use the messages reference or source code to see if a field has a fullName or groupName message.
  • An optional built-in public-facing collection browser application can now be deployed along with CollectionSpace.   
  • Data may now be automatically migrated when upgrading to a new version of CollectionSpace with schema changes. This happens when the new version is started for the first time, and an older database is detected. 
  • The Password and Confirm Password fields of immutable users can now be configured to be editable in the UI. This would allow the password of built-in users to be changed in the UI, if desired. By default, these fields remain read-only in the UI. 
  • A new data update, Merge Authority Items, is available. This can be used to merge duplicated authority items together. 
  • BREAKING Permissions for viewing/editing the metadata of reports and data updates are now distinct from permissions to run the reports and data updates. Two new resources now appear when setting permissions for a role: Data Update Invocations, and Report Invocations. A role must be granted Write access to these resources in order to run data updates and reports. When upgrading, review all roles to ensure that these permissions are set properly so that the correct users are still allowed to run data updates and reports. 
  • An individual report may now specify the roles that are allowed to run it (in addition to having the appropriate Report Invocations permission). 
  • Reports may now use JasperReports built-in functions and JavaScript expressions. 
  • Report metadata may now specify the MIME types that are supported. When running a report in the UI, only the supported mime types will be selectable in the output format selector. 
  • On the full size image viewer, rotate left/right buttons are now available. This only affects the current display. It does not change the rotation of the saved image. 

Schema changes

  • BREAKING On the Use of Collections Record, several fields have moved. Data will be automatically migrated from the old fields to new fields when CSpace 6 starts up for the first time. If you have written reports that use the old fields, your queries will need to be updated to use the new fields. 

    Old FieldNew Field
    uoc_common:location
    		uoc_common:locationList/location
    uoc_common:authorizedByuoc_common:authorizationGroupList/authorizationGroup/authorizedBy
    uoc_common:authorizationDateuoc_common:authorizationGroupList/authorizationGroup/authorizationDate
    uoc_common:authorizationNoteuoc_common:authorizationGroupList/authorizationGroup/authorizationNote
    uoc_common:startSingleDateuoc_common:useDateGroupList/useDateGroup/useDate

    Many new fields have also been added. 

  • BREAKING On the Intake record, the Current Owner field is now repeating. The Depositor and Depositor's Requirements fields are now members of a repeating group. Data will be automatically migrated from the old fields to new repeating fields when CSpace 6 starts up for the first time. If you have written reports that use the old fields, your queries will need to be updated to use the new fields. 

    Old FieldNew Field
    intakes_common:currentOwnerintakes_common:currentOwners/currentOwner
    intakes_common:depositorintakes_common:depositorGroupList/depositorGroup/depositor
    intakes_common:depositorsRequirementsintakes_common:depositorGroupList/depositorGroup/depositorsRequirements

  • BREAKING On the Organization record, Contact Name has moved into a repeating group. Data will be automatically migrated from the old field to new field when CSpace 6 starts up for the first time. If you have written reports that use the old field, your queries will need to be updated to use the new field. 

    Old FieldNew Field
    organizations_common:contactNames/contactName

    organizations_common:contactGroupList/contactGroup/contactName

    The new contactGroup also contains the following new fields: contactRole, contactDateGroup, contactEndDateGroup, contactStatus.

  • BREAKING In the Anthropology profile: On the Object record, the NAGPRA Cultural Determination field has moved into a repeating group (as the Note field). Data will be automatically migrated from the old field to new field when CSpace 6 starts up for the first time. If you have written reports that use the old field, your queries will need to be updated to use the new field. 

    Old FieldNew Field
    collectionobjects_nagpra:nagpraCulturalDeterminations/nagpraCulturalDetermination

    collectionobjects_nagpra:nagpraDetermGroupList/nagpraDetermGroup/nagpraDetermNote

    The new nagpraDetermGroup also contains the following new fields: nagpraDetermCulture, nagpraDetermType, nagpraDetermBy. 

  • BREAKING On the Object record, the data type of the following fields have changed from string to date. Data will be automatically updated when CSpace 6 starts up for the first time. If you have written reports that use these fields, you may need to format the results differently, since they will now contain a timestamp. 
    • collectionobjects_accessionuse:accessionUseGroupList/accessionUseGroup/accessionUseRequestDate

    • collectionobjects_accessionuse:accessionUseGroupList/accessionUseGroup/accessionUseFilledDate

    • collectionobjects_annotation:annotationGroupList/annotationGroup/annotationDate
  • On the Media record, a new field has been added: Publish To. This field is used to determine if the media record's associated image will appear in the public browser (if the value is All or CollectionSpace Public Browser). 
  • In the Public Art profile:
    • A new field has been added to the Person record: Biographical Note. 
    • A new field has been added to the Place record, in the repeating Address group: County. 

Configuration changes to record types, authorities, vocabularies, and option lists

  • BREAKING The following UI message IDs have been changed to follow the conventional message ID format. If you customized any of these messages using the old message ID, update your configuration to use the new message ID.

    Old IDNew IDCommentIssue
    field.persons_common.forename.fullNamefield.persons_common.foreName.fullNameuppercase 'N'
    field.persons_common.forename.name

    field.persons_common.foreName.name

    		uppercase 'N'
    field.persons_common.surname.fullNamefield.persons_common.surName.fullNameuppercase 'N'
    field.persons_common.surname.namefield.persons_common.surName.nameuppercase 'N'
    field.collectionobjects_nagpra.graveAssocCodes.name

    field.collectionobjects_nagpra.graveAssocCode.name

    		remove 's'
    field.acquisitions_common.approvalGroup.fullName
    field.acquisitions_common.approvalGroup.approvalGroup.fullName
    		'approvalGroup' is intentionally repeated
    field.approvalGroupField.approvalGroup.name
    field.acquisitions_common.approvalGroup.approvalGroup.name
    field.intakes_common.approvalGroup.approvalGroup.name

    'approvalGroup' is intentionally repeated.

    Previously, this message was erroneously used on both the intake record and acquisition record. Now there are two separate messages for each record type that can be changed independently.

    field.intakes_common.approvalGroup.fullName
    field.intakes_common.approvalGroup.approvalGroup.fullName
    		'approvalGroup' is intentionally repeated
    panel.collectionobject.livingplant
    panel.conservation.livingplant
    		record type corrected
    field.acquistions_common.acquisitionFundingSourceProvisos.fullName
    field.acquisitions_common.acquisitionFundingSourceProvisos.fullName
    		schema name corrected
    field.acquistions_common.acquisitionFundingSourceProvisos.name
    field.acquisitions_common.acquisitionFundingSourceProvisos.name
    		schema name corrected
    field.intakes_common.despositorsRequirements.fullName
    field.intakes_common.depositorsRequirements.fullName
    		field name corrected
    field.intakes_common.despositorsRequirements.name
    field.intakes_common.depositorsRequirements.name
    		field name corrected
    field.contacts_common.webAddressTypeType.name
    field.contacts_common.webAddressType.name
    		field name corrected
  • The following vocabularies have been added to the Conservator and Other Treatment Party fields on Conservation records: Local Organization, Shared Organization. 

Bug fixes

  • Field groups that are nested in repeating groups, and contain fields with default values, no longer re-appear after deletion. 
  • When downloading UI configuration as JSON from /config, field view types are now included. (This is primarily of interest to CollectionSpace developers). 
  • Edited field values no longer revert to their last saved values when a notification message is auto-closed. 
  • Selected search results no longer become unchecked when changing pages when multiple search conditions are used. 
  • Image thumbnails and snapshots (in the right sidebar) are now oriented according to their exif orientation tag (only on Firefox and Chrome >= 81). 
  • Cloning the current Object record to create a Broader Object no longer fails. 
  • Group records with customized titles that are not ref names are now displayed correctly. 
  • Navigating through image snapshots (in the right sidebar) with the arrow buttons now works correctly. 
  • Viewing an image snapshot (in the right sidebar) by clicking on the thumbnail strip now works correctly. 
  • Roles with Write or Delete permissions on Location/Movement/Inventory records are now able to lock those records. If a role that has those permissions is still unable to lock a record, re-save the role. 
  • On advanced search, searches for numbers with decimals are no longer truncated at the decimal. 
  • Blank options no longer appear twice in option lists that explicitly contain a blank option. 
  • Searches on repeating structured date fields no longer produce incorrect results.   
  • When syncing from a shared authority server, items deleted on the server are now correctly deprecated. 
  • When syncing from a shared authority server, the workflow state of newly created items on the server is now correctly synced. 
  • Syncing from a shared authority server no longer fails when an item has been hard-deleted on the server. 
  • Syncing an authority with more than 2,500 items from a shared authority server is now possible. 
  • The speed of syncing from a shared authority server has been greatly improved. 
  • The UI no longer sends invalid page number/size parameters to the back end. 
  • Deleting a term from a term list with many options no longer fails.