[Archivesspace_Users_Group] Importing agents into ASpace that we already have

[Jane LaBarbara]

Good morning,

My department started populating our ASpace repository with some hand-entered information as well as a massive import of Resource Records, which included linked agents.  Now, I'm working to import legacy accession records with the CSV, and I've run into an odd problem that I'm interested to see if anyone else has solved. (We're running v1.5.1 right now, if that matters.)

I've noticed that, in some cases, if I import an accession record via the CSV file that includes a donor agent which already exists in ASpace, the pre-existing agent just gets linked to the newly imported accession record.  This is great except for when I'm trying to import the donor's address info too-I realized the address info I was trying to import was not added to the pre-existing agent record.  Once I noticed this, I thought I'd be smart and check the list of donors in my accession CSV against the agents already in ASpace.  If the agent was already in ASpace, I added the address by hand then deleted the address from the CSV file. Then I imported the CSV file.  It seems that, in at least a few cases, this resulted in the creation of a second agent, so we'll have to do a lot of merging of agent records.

I am assuming that if the content of certain fields in the agent record I'm trying to import match those in an agent record already in ASpace, that will result in a merge rather than a duplicate agent creation. Does anyone know which fields I need to pay attention to?

Thanks,
Jane

/ Jane Metters LaBarbara
Assistant Curator, West Virginia & Regional History Center<https://wvrhc.lib.wvu.edu/>
West Virginia University Libraries
(304) 293-0352 office
jane.labarbara at mail.wvu.edu<mailto:jane.labarbara at mail.wvu.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170706/d7b1e12a/attachment.html>