Work records migration and retirement

• You will not have access to your work record data
• Your propagated data in item/asset records will remain
• You can still create containers and/or compound objects for your projects on your own

• You will no longer be able to add, edit, or delete work records in Forum.
• Links to Shared Shelf Works (SSW) vocabulary data will eventually stop working.

Recommended: Update your read-only cataloging fields to be editable in each affected project if they relied on propagation from works, since work records will no longer be editable.

• We won’t publish your migrated content
• You can still edit and publish, suppress, or delete records at any time

During migration selection

By December 1, 2023

Consider containers if:

• Your records contain mixed content types (images, documents, etc.)
• Your records have item-level metadata.
  
  • Please note that unlike with work records, container-level metadata does not propagate to individual item records. Instead, it is listed on the container page which is linked from each associated item's page.
• Rights vary across items.

Consider compound objects if:

• Your institution had intentions to switch to compound objects. (Work records pre-dated compound objects in Forum.)
• Your records have minimal to no item-level data.
• Rights across your items are consistent.
• Your records are images of the same file type.
  • Compound objects do not support documents, audio, video, or panorama content.
  • Compound objects do not support mixing image file types (ex. JPEG and TIFF) within a single item.

During the migration

December 1 - 12, 2023

We will:

• Preserve your work record data with a metadata schema.
• Create a new “Work Records Containers” list in your institution’s Forum instance.
• Add a new "Sequence Number" field to your project.
• Load work record data into containers (container list terms).
• Link and sequence related items in their respective containers.
• Set the lead item in each work record as the representative image for its container.

We will:

• Preserve your work record data with a metadata schema.
• Create a new project in your institution’s Forum instance.
• Load work record data and image files into new compound objects. (Note: Your items will receive all new SSIDs.)
• Sequence related images within each compound object. The lead item in each work will display as the compound object's thumbnail.

After the migration

December 12, 2023 - January 31, 2024

Please review:

• Container list permissions
  Institutional Admins should grant permissions to users to see and/or modify the new "Work Records Containers" list as appropriate.
• Visibility of container page fields
  Make any desired changes to container-level field visibility prior to publishing.
• Delimiters
  We'll use pipe delimiters to separate multiple values for a given field.
• Sequencing of items
  Ensure items are in the correct order according to the new "Sequence Number" field in each container.
• Container representative image
  Ensure the representative image for your containers matches your lead item for each work.
• New or empty fields
  You can add or remove fields from your container schema at any time.
  • Please note that unlike with work records, container-level metadata does not propagate to individual item records. Instead, it is listed on the container page which is linked from each associated item's page.
• Qualifiers
  We’re preserving all list term links.

You can use Forum’s bulk-editing tools or manage your data using Excel if needed.

Please review:

• Delimiters
  We'll use pipe delimiters to separate multiple values for a given field.
• Sequencing of images
  Ensure images are in the correct order in each compound object.
• New or empty fields
  You can add or remove fields from your project schema at any time.
• Qualifiers
  We’re preserving all list term links.

You can use Forum’s bulk-editing tools or manage your data using Excel if needed.

Full-Service Publishing

Starting February 1, 2024

We'll re-publish your impacted records to JSTOR on your behalf.

If you choose to opt out of full-service publishing and/or want to re-publish your migrated content prior to February 1, 2024:

• Map your new fields
  Map "Work Records Containers" to "Containers" and "Sequence Number" to "Sequence Number" in your JSTOR publishing target.
• Re-publish to JSTOR
  Re-publish your impacted records to JSTOR.

We'll suppress your existing impacted records, set up a publishing target in your new project, and publish this content to JSTOR on your behalf.

If you choose to opt out of full-service publishing and/or want to re-publish your migrated content prior to February 1, 2024:

• Suppress records
  Suppress impacted records in your existing project, if they were previously published to JSTOR.
• Set up a JSTOR target
  Create a JSTOR publishing target in your new project. This target can point to an existing collection.
• Map your new fields
  Map fields in your new project to your JSTOR target.
• Re-publish to JSTOR
  Re-publish your new project to JSTOR.