[Archivesspace_Users_Group] brainstorming -- data integrity checking

[Nathan Stevens]

Try a combination of ref_ids and call numbers (I am assuming call numbers
get placed into the component unique id field in AT).  A combination of
those two fields should result in uniquely identifying the resource
components as long as call numbers were always field out.

On Tue, Jun 2, 2015 at 1:59 PM, Callahan, Maureen <maureen.callahan at yale.edu
> wrote:

>  Hi everyone,
>
>
>
> We’re running our fourth of four migrations at Yale this week (WOOHOO),
> and right now I’m doing some data integrity checking between AT and
> ArchivesSpace to get slightly more detailed information than what the
> migrator provides.
>
>
>
> Almost everything looks pretty good, except for one problem – we have 2603
> fewer archival_objects in ArchivesSpace than we had components in
> Archivists’ Toolkit. This wasn’t a problem for migrations for other
> repositories. I am almost positive that this was the result of
> irresponsible SQL delete statements many moons ago, and that the components
> in AT are orphans, but I’d like to figure out a way to check. Does anyone
> have any ideas? Maybe comparing refids and call numbers? All ideas are
> welcome.
>
>
>
> Maureen
>
>
>
> Maureen Callahan
>
> Archivist, Metadata Specialist
>
> Manuscripts & Archives
>
> Yale University Library
>
> maureen.callahan at yale.edu
>
> 203.432.3627
>
>
>
> Webpage: web.library.yale.edu/mssa
>
> Collections: drs.library.yale.edu
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Nathan Stevens
Programmer/Analyst
Digital Library Technology Services
New York University

1212-998-2653
ns96 at nyu.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150602/d78f9804/attachment.html>