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.
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 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.
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 Field | New Field |
|---|---|
uoc_common:location | uoc_common:locationList/location |
| uoc_common:authorizedBy | uoc_common:authorizationGroupList/authorizationGroup/authorizedBy |
| uoc_common:authorizationDate | uoc_common:authorizationGroupList/authorizationGroup/authorizationDate |
| uoc_common:authorizationNote | uoc_common:authorizationGroupList/authorizationGroup/authorizationNote |
| uoc_common:startSingleDate | uoc_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 Field | New Field |
|---|---|
| intakes_common:currentOwner | intakes_common:currentOwners/currentOwner |
| intakes_common:depositor | intakes_common:depositorGroupList/depositorGroup/depositor |
| intakes_common:depositorsRequirements | intakes_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 Field | New 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 Field | New Field |
|---|---|
collectionobjects_nagpra:nagpraCulturalDeterminations/nagpraCulturalDetermination | collectionobjects_nagpra:nagpraDetermGroupList/nagpraDetermGroup/nagpraDetermNote |
The new nagpraDetermGroup also contains the following new fields: nagpraDetermCulture, nagpraDetermType, nagpraDetermBy.
collectionobjects_accessionuse:accessionUseGroupList/accessionUseGroup/accessionUseFilledDate
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 ID | New ID | Comment | Issue |
|---|---|---|---|
| field.persons_common.forename.fullName | field.persons_common.foreName.fullName | uppercase 'N' | |
| field.persons_common.forename.name | field.persons_common.foreName.name | uppercase 'N' | |
| field.persons_common.surname.fullName | field.persons_common.surName.fullName | uppercase 'N' | |
| field.persons_common.surname.name | field.persons_common.surName.name | uppercase '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 |