[Archivesspace_Users_Group] Cataloged note field

[Noah Huffman]

Hi Adam,

It’s recommended that you run the AT migration plugin to ArchivesSpace v.1.4.2 and then upgrade to ArchivesSpace to 1.5.2.

Even so, I’m not clear on where the cataloged_note field maps.  According to the AT migration mapping documentation<http://archivesspace.org/wp-content/uploads/2016/08/ATMappingDocument_AT-ASPACE_BETA.xls>, it should map to a collection management record, but I’m not seeing that field in collection management.  As part of the 1.4.2 to 1.5.X upgrade, some collection management fields were converted to event records.  You might check to see if any of your cataloged_note fields from AT now exist as event records in ArchivesSpace.  I’m seeing some in my database, so I suspect that is what happened.

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Adam Jazairi
Sent: Tuesday, January 24, 2017 10:13 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Cataloged note field

Hello all,

My institution is in the process of migrating from Archivists' Toolkit to ArchivesSpace, and we've noticed that the cataloged note field doesn't seem to map. This seems to be intentional, based on the discussion in the following ticket: https://archivesspace.atlassian.net/browse/AR-827<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D827&d=CwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=_UavDv-WFzRDpRRsTFP9lN1gC9C2F7trcOMsD9sYV2g&s=R5PHnR7r5x2wkM08L5uu_CiDDznDXI593YLjcyQFSxY&e=>

This is problematic for us because some of our records have important data in this field that we don't want to lose. Has anyone else encountered this issue? If so, I'd appreciate any advice on how to resolve it.

For reference, we're running ArchivesSpace 1.5.2 and used the AT migration plugin<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_at-2Dmigration&d=CwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=_UavDv-WFzRDpRRsTFP9lN1gC9C2F7trcOMsD9sYV2g&s=Zzmw9n2vFZfKygUD4yFpazrlJhx08f8oTnYPfkhP7z0&e=> to migrate our database.

Thanks,

Adam

--
Adam Jazairi
Digital Library Applications Developer
Boston College Libraries
(617) 552-1404
jazairi at bc.edu<mailto:jazairi at bc.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170124/e2f83a6c/attachment.html>