<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>+1 : I can contribute as well. </p>
<p><br>
</p>
<div id="x_Signature">
<div class="x_BodyFragment"><font size="2">
<div class="x_PlainText"><br>
-- Steve Majewski / UVA Alderman Library </div>
</font></div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Seth Shaw
<seth.shaw@unlv.edu><br>
<b>Sent:</b> Thursday, August 3, 2017 11:38:20 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting library</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">I'm interested in this too. I was doing some python scripting just<br>
this week (<a href="https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py#L85-L117">https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py#L85-L117</a>),<br>
if you want to throw that on the prior art pile.<br>
<br>
Also for the prior art pile: I know the folks at the Rubenstein (Duke)<br>
have also done a good deal of ArchivesSpace python scripting (see<br>
<a href="http://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/">http://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/</a><br>
and <a href="https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python">
https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python</a>).<br>
<br>
On Thu, Aug 3, 2017 at 6:47 AM, Mayo, Dave <dave_mayo@harvard.edu> wrote:<br>
> One thing I think might be useful, especially in planning stages, is<br>
> collecting the “prior art” in one place to look at – because there are a lot<br>
> of scripts people have built around the API, and they probably capture at<br>
> least a fair bit of “what people want to do most with the API.”<br>
><br>
> So, whenever the github is set up, we should do this.<br>
><br>
> - Dave<br>
><br>
><br>
><br>
> From: <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of<br>
> "rsdoiel@caltech.edu" <rsdoiel@library.caltech.edu><br>
> Reply-To: "rsdoiel@caltech.edu" <rsdoiel@caltech.edu>, Archivesspace Users<br>
> Group <archivesspace_users_group@lyralists.lyrasis.org><br>
> Date: Thursday, August 3, 2017 at 9:21 AM<br>
> To: Archivesspace Users Group<br>
> <archivesspace_users_group@lyralists.lyrasis.org><br>
> Subject: Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting<br>
> library<br>
><br>
><br>
><br>
> Hello Patrick,<br>
><br>
><br>
><br>
> I have written some tools in go and mocked up functionaity in Python a few<br>
> years ago I'd be interested in the project.<br>
><br>
><br>
><br>
> Robert Doiel<br>
><br>
> Caltech Library<br>
><br>
> rsdoiel@caltech.edu<br>
><br>
><br>
><br>
> On Aug 3, 2017 6:10 AM, "Galligan, Patrick" <PGalligan@rockarch.org> wrote:<br>
><br>
> Hi all,<br>
><br>
><br>
><br>
> For a while now the RAC has been bouncing around the idea of developing an<br>
> AS Python library that would hold a lot of the functions we find ourselves<br>
> working with a lot when scripting against the AS API. I know Greg Wiedeman<br>
> at U Albany has done some work to this end, but I wanted to send a blast out<br>
> to the list to see who else might be interested. We’d love to make this as<br>
> collaborative and exhaustive as possible so that we can cover the most<br>
> bases.<br>
><br>
><br>
><br>
> I’m thinking of setting up a Github project that we can collaboratively work<br>
> in. Anyone have better ideas?<br>
><br>
><br>
><br>
> Let me know.<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
> Patrick Galligan<br>
><br>
> Rockefeller Archive Center<br>
><br>
><br>
> _______________________________________________<br>
> Archivesspace_Users_Group mailing list<br>
> Archivesspace_Users_Group@lyralists.lyrasis.org<br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Archivesspace_Users_Group mailing list<br>
> Archivesspace_Users_Group@lyralists.lyrasis.org<br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
><br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
Archivesspace_Users_Group@lyralists.lyrasis.org<br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
</div>
</span></font>
</body>
</html>