You were spot on, Noah -- migrating to an earlier version fixed it. Thanks for sharing your experience.
For anyone else facing this problem, try migrating from Archivists' Toolkit to ArchivesSpace v1.2.0, then upgrading to v1.5.2. The cataloged notes should map first to collection management in v1.2.0, then to outcome notes in v1.5.2. In our case, the field didn't migrate directly to versions 1.3.x or higher. Adam -- Adam Jazairi Digital Library Applications Developer Boston College Libraries (617) 552-1404 [email protected] On Tue, Jan 24, 2017 at 3:57 PM, Noah Huffman <[email protected]> wrote: > Strange. My cataloged_note content from AT mapped to the Outcome Note > field of the event record (see screenshot). But, I migrated from AT to an > early version of ASpace (1.3?). I wonder if the mappings have changed > since. Let me know what you discover. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Adam > Jazairi > *Sent:* Tuesday, January 24, 2017 3:24 PM > *To:* Archivesspace Users Group <archivesspace_users_group@ > lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Cataloged note field > > > > Hi Noah, > > > > Thanks for getting back to me. I should've clarified that though we're > currently running 1.5.2, we used the plugin to migrate to 1.4.2 first. > Sorry for any confusion. > > > > Our ArchivesSpace instance maps cataloged notes to events, but only > partially. The events include the date accessioned and the linked record, > but not the note itself. I wonder if this is an issue with the Archivists' > Toolkit migration plugin. I'll have a look at the source code and see if > anything looks awry. > > > > Adam > > > -- > > Adam Jazairi > > Digital Library Applications Developer > > Boston College Libraries > > (617) 552-1404 > > [email protected] > > > > On Tue, Jan 24, 2017 at 2:47 PM, Noah Huffman <[email protected]> > wrote: > > 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 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.org_wp-2Dcontent_uploads_2016_08_ATMappingDocument-5FAT-2DASPACE-5FBETA.xls&d=CwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=WcmBsuGlb9ApLc8yY4sF1uHL9H906uxVXhBwPBMQx08&s=V6WfCK63oS8_HayEqroq1xtsZEfAslZq8hUXD2KL-YY&e=>, > 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 <(919)%20660-5982> > > http://library.duke.edu/rubenstein/ > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Adam > Jazairi > *Sent:* Tuesday, January 24, 2017 10:13 AM > *To:* Archivesspace Users Group <archivesspace_users_group@ > 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 > > [email protected] > > > _______________________________________________ > Archivesspace_Users_Group mailing list > [email protected] > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=WcmBsuGlb9ApLc8yY4sF1uHL9H906uxVXhBwPBMQx08&s=E-JridPRBkvjUti6ofnE-Kits69o7Oesk6yFjaEhRNc&e=> > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > [email protected] > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
