Good afternoon all, This is a question about user-defined fields and archival objects. Here in Cambridge we have been working on migration -setting up crosswalks to map data from our existing systems (including AtoM) to ArchivesSpace. There are a small number of fields we have not been able to find a home for in AS and we had envisaged mapping them to user-defined fields. However, it looks as though it's not possible to add a set of user-defined fields to archival objects, though they can be added to other types of record (eg Resources). We are looking at migrating some substantial datasets into ArchivesSpace: in some cases several thousands of records will be nested beneath one parent/resource description (for example the archives of the University of Cambridge) and we want to map all our existing fields to ArchivesSpace (whether the AS records are archival objects or resource descriptions).
I would be really interested in hearing whether anyone else has faced a similar challenge and has any advice about how we might tackle this. I'd also be interested to understand more about the background to the difference between archival objects and resources. Many thanks in advance for any help with this and best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/<http://www.lib.cam.ac.uk/> Normal working days are Monday-Wednesday
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
