Documentation

CollectiveAccess

Summary

  1. Resolve the 21 collision clusters via physical survey. Assign final identifiers to the 68 affected records.
    1. Remove 68 affected records to second sheet.
  2. Build the data model in CA: object type list, metadata elements, entity relationship types.
  3. Build the vocabulary lists in CA: admc_material_category (hierarchical) and admc_material_terms (flat), built from cleaned and merged DSpace subject fields.
  4. Build the storage location hierarchy in CA.
  5. Pre-process the export: parse dc.description into holdings flags, split subject strings on ||, map rights to access values, load your new idno column.
  6. Write the import mapping: two passes, entities first then objects.
  7. Test import on a 20-record slice. Iterate.
  8. Production import of the 310 clean records.
  9. Import the 68 collision records after physical survey.
  10. Establish media naming convention for future digitisation; no media ingest yet.

Data model  →  Lists/vocabularies  →  Import mapping  →  Test import  →  Production import  →  Media (later)

Resources

https://camanual.whirl-i-gig.com/providence/

https://manual.collectiveaccess.org/providence/user/editihttps://camanual.whirl-i-gig.com/providence/user/dataModelling/listsAuthoritiesng/lists_and_vocab.html
https://manual.collectiveaccess.org/providence/user/dataModelling/primaryTables.html

Primary tables

CA is structured around several primary tables, with editors that can be enabled or disabled depending on project requirements. The ones most relevant to the ADMC:

Table What it holds
ca_objects The physical or born-digital items themselves
ca_object_lots Accession events grouping multiple objects acquired together
ca_entities People and organisations (creators, donors, manufacturers)
ca_collections Intellectual groupings of objects (series, fonds, donor collections)
ca_storage_locations A hierarchical map of physical storage
ca_places Geographic locations (hierarchical, linkable to GeoNames)
ca_occurrences Flexible: events, exhibitions, publications, activities
ca_loans Outgoing or incoming loan records
ca_movements Optional: object movement history

An object record does not contain the entity's name as a text string. It contains a relationship to a separate entity record. This is the relational model in practice. If "Hansgrohe AG" is a manufacturer of 40 objects in the ADMC, there is one entity record for Hansgrohe, and 40 relationships from 40 objects to that record. Correct it once; it updates everywhere.

Metadata elements to create (or verify)

CA element code Maps from Data type Notes
admc_idno_legacy dc.identifier.other Text Preserve the old location code as a legacy field, non-searchable by default
admc_description dc.description (substantive only) Text (long) Only for the ~20 records with real text
admc_physical_holdings dc.description (parsed) List (multi-value) "Sample available," "Booklet available" as checkboxes
admc_manufacturer_url dc.publisher.uri URL Product page; can also live on the entity record
admc_subject_classification dc.subject.classification List (hierarchical) See vocabulary design below
admc_dspace_handle dc.identifier.uri URL Preserve the DSpace handle for provenance
admc_intake_year dc.date.issued Text or Date Record the upload year if at all; do not call it "date issued"

VRA Core fields that should already exist and need no new elements: title (preferred_labels), dimensions, material, technique, condition.

Sandbox -- AS

Task 2: Build the data model

Notes - 9 June

Notes - 10 June

Notes - 6 July

Notes - 8 July

Creating Object Records in CollectiveAccess

Accessing Providence

CollectiveAccess has two interfaces, Providence and Pawtucket. Providence is for admin and Pawtucket is for the public. The URL for the ADMC’s Providence site is https://library.berlin-international.de/collections/admin. Once logging in, you will be able to create and edit object and entity records.

Before you begin

Checking Entity Records

Every object record must be linked to an entity record of its manufacturer. To prevent duplicate entity records from being created, first check if the manufacturer already has an entity record in the system. Follow the instructions in the "Creating Entity Records in CollectiveAccess" article for searching and creating entity records before creating an object record.

Identifier

The format for object identifiers is YYYY.2.NNN. The unique identifier for a new object record is determined by the highest existing identifier for the current year in CA.

Finding the highest existing identifier:

  1. Go to Find in the menu, then click Objects in the dropdown. This will take you to the Basic Search for all object records in CA.
  2. In the list view of all object records, there will be a column titled Object identifier. Click on the title to sort the records by their identifier. Higher identifiers will be at the top of the list.

  3. Once you have determined what the highest existing identifier in use is, use the next number in the sequence for the new object record. For example, if the highest existing identifier is 2026.2.15, the next identifier will be 2026.2.16.

Accessing the object record editor

To create a new object record in the system, go to New, then Object in the dropdown. Choose the object type that best fits the item you are cataloging.

Object types

For the ADMC there are three different object types: Physical Sample, Publication and Sample with Publication. To decide which object type applies to the item you are cataloging, assess it based on these criteria:

Once you have chosen one of these object types, a new object record will be created.

Required fields

Every object record must include the following field before it can be saved:

These fields are not required for a record to be saved, but should be filled out if available as they contain important information related to workflow management, public accessibility and specifics for the ADMC:

Saving and checking

Once you are done editing the object record, save the record by clicking the save button at the top or bottom of the record.

CA_image 1.png

If the object is intended to be accessible to the public, verify that the object shows up correctly in Pawtucket. Go to https://library.berlin-international.de/collections. Find the object using the search bar, Browse or Advanced Search on the menu. Once found, ensure that the public can view the object, its title, identifier, related entity and any relevant fields.

Images

If the item you are cataloging has images associated with it, these images can be attached to the object record:

  1. Before any images can be uploaded, the object record must first be created and saved.
  2. You will then have access to the Media tab on the left-hand column of the object record editor.
  3. From here you can upload images to the object record.
  4. To add more than one image, click on “Add representation” at the bottom of the field.
  5. To ensure that the images will be visible to the public, you must change the access field for each image to “accessible to public.”
  6. Save changes.

Once images have been uploaded and processed in CA, you can change which image is primary, meaning which image will appear first in the object’s image carousel in Pawtucket:

  1. Under the Media tab, you will find a right-hand column next to the different media representation files.
  2. Click “Make primary” from the column on the image you wish to change.
  3. Under the image you clicked, it will be noted that the chosen image “Will be primary after save.”

  4. Save changes.

CA_image 2.png

Once images are uploaded and saved to the object record, check on Pawtucket to ensure that the images are visible to the public in the intended order.

Common Mistakes

Follow the directions above as you create a new record to prevent the most common mistakes:

Creating Entity Records in CollectiveAccess

Before you begin

Search first

Before creating a new entity record, you must search in CA to see if an entity record already exists for the manufacturer:

  1. To go Find in the menu, then click on Entities in the dropdown. This will take you to the Basic Search for all entity records in CA.
  2. If an entity record already exists, do not create a new record. Search for it in the Related entities field when creating an object record.

The search-first rule ensures that duplicate entity records are not created. It is easier to prevent duplicate entity records than it is to fix them after they are made.

When to create

If after searching already present entity records in CA you find that a record for a manufacturer does not exist, you can create a new record.

Identifier

The format for entity identifiers is YYYY.1.NNN. The unique identifier for a new entity record is determined by the highest existing identifier for the current year in CA.

Finding the highest existing identifier:

  1. Go to Find in the menu, then click Entities in the dropdown. This will take you to the Basic Search for all entity records in CA.
  2. In the list view of all entity records, there will be a column titled Entity identifier. Click on the title to sort the records by the identifier. Higher identifiers will be at the top of the list.
  3. Once you have determined what the highest existing identifier in use is, use the next number in the sequence for the new entity record. For example, if the highest existing identifier is 2026.1.15, the next identifier will be 2026.1.16.

Accessing the entity record editor

To create a new entity record in the system, go to New, then Entity in the dropdown. There will be further options for entity types.

Entity type

The entity types available are Corporate, Family, Other and Personal. Choose Corporate, as this will identify the record as an organization rather than an individual. Once chosen, a new entity record will be created.

Required fields

Every entity record must include the following fields before it can be saved:

Email address

To access the email address field:

  1. First save the new entity record.
  2. You will then have access to the Contact Info tab on the left-hand column of the entity record editor.
  3. Record the information in the Email address field.
  4. Save changes.

Saving and verifying

Once you are done editing the entity record, save the record by clicking the save button at the top or bottom of the record.

To verify that the entity record was saved correctly, create a new object record and test if you are able to find the entity in the Related entities search bar. If you cannot find the new entity, it might not have been completed correctly.