[Archivesspace_Users_Group] AT Migration problem with repository processing note

[Hardy, Ian]

Thanks Noah and Maureen, I was able to update some test repository
processing notes using Noah's scripts as a starting point for interacting
with the API. I think this will do the trick for us.

On Mon, Feb 1, 2016 at 10:52 AM, Noah Huffman <noah.huffman at duke.edu> wrote:

> Christie,
>
> I have a script that sort of does what Maureen suggests.  Was going to
> mention it earlier, but it's a bit undercooked....
>
>
> https://github.com/noahgh221/archivesspace-duke-scripts/blob/master/duke_archival_object_metadata_adder.py
>
> It can read a two-column spreadsheet (as TSV) and batch add Repository
> Processing notes to archival objects via the API based on ref_ID values in
> the spreadsheet:
>
> The example above is a modified version of a script that folks at the
> Bentley wrote:
>
> https://github.com/djpillen/bentley_scripts/blob/master/update_archival_object.py
>
> The comments in the script should help you figure out what you might need
> to modify.  For full disclosure, I'm a Python noob, so this is probably
> terribly written, but I can confirm that it works for my use case.
>
> -Noah
>
> -----Original Message-----
> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of
> Callahan, Maureen
> Sent: Monday, February 01, 2016 10:43 AM
> To: Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> Subject: Re: [Archivesspace_Users_Group] AT Migration problem with
> repository processing note
>
> Hey Christie,
>
> Doing it now, we would probably write a script to do an update using the
> API (better built-in validation, fewer opportunities to do something
> stupid). During the migration, there's a choice to keep or re-assign refids
> - you're definitely going to want to keep those to help match up the
> components.
>
> It's worth noting that we made those SQL updates because of mistakes in
> the migrator. I'm interested to know if those ever got fixed.
>
> MC
>
>
> > On Feb 1, 2016, at 10:36 AM, Peterson, Christie <
> cspeterson at email.gwu.edu> wrote:
> >
> > Hi Noah,
> >
> > Yep, that's the kind of thing we're probably going to end up doing.
> >
> > Many thanks!
> >
> > Christie
> > _______________________________________________
> > Archivesspace_Users_Group mailing list
> > Archivesspace_Users_Group at lyralists.lyrasis.org
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.
> > org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zW
> > uuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=n1N3sMK
> > X9kb8hCXfWyWw-9rmsPmqB9BhN_6Kckdfo5g&s=XXk6iOoNajjfK6Ebn6n3Oe4cvYGTMPW
> > o6wDb_Hto0q8&e=
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>



-- 
Ian Hardy
Systems Specialist
GW Libraries
ihardy at gwu.edu <ihardy at email.gwu.edu>
helpdesk: (202) 994-8278
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160201/858eae2c/attachment.html>