Deaccessions

The deaccessioning process for your institution can be tracked in CollectiveAccess at the item-level by using the "Deaccession Status" bundle. You can place this bundle anywhere in the object editor. If you are writing a profile configuration in XML, the bundle code is ca_objects_deaccession.

To deaccession an item, simply click the deaccesssion checkbox. This will flag the object record as deaccessioned and will also expand the bundle so you can add additional information, such as the date of deaccession, the "type", and any qualifying notes. The deaccession "types" can be customized in the list object_deaccession_types.

Deaccessioned items will be marked in the inspector, like in the following example, as well as the object location history if you are using that bundle. You can also browse on items by their deaccession status.

The element codes for sub-elements of ca_objects_deaccession are listed below. The bundle will appear on the record after the first Save.

Deaccession intrinsic elements

Element Name	Description
deaccession_date	Date of deaccession
deaccession_disposal_date	Date of disposal
deaccession_notes	Deaccession notes
deaccession_type_id	Corresponds to the list object_deaccession_types
is_deaccessioned	Yes/no check

Importing data to Deaccession intrinsic elements

When importing deaccession information to the ca_objects_deaccession bundle, note that the intrinsic elements should be prefixed by the table name "ca_objects". Mapping to each element would look like this.

Table.Element Name	Description
ca_objects.deaccession_date	Imports a data source to date of deaccession
ca_objects.deaccession_notes	Imports a data source to Deaccession notes
ca_objects.deaccession_type_id	Imports a data source to Corresponds to the list object_deaccession_types
ca_objects.is_deaccessioned	Yes/no checkbox: 1=yes; 0=no. You may have to use original/replacement values to transform the source data to 1 and 0.

Don't forget to assign each mapping to a "Group"!

sphinx