<div dir="ltr">I'm working with a few member organizations who'd like to integrate with their respective content management systems in order to present their collections to non-specialist, general interest audiences through their branded website, as well offer the means to further enrich resources outside of the DACS paradigm.<div><br></div><div>That said, easy enough to rough out with your favorite HTTP client/framework (Guzzle, for example) and the ASpace API, especially by passing values into search parameters. (Haven't toyed with querying the index directly.) <div><div class="gmail_extra"><br></div><div class="gmail_extra">I don't recall, is there an "integration" advisory committee?</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Jason Loeffler</font></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Principal</font></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Minor Science | Application Development & Metadata Strategy</font></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Brooklyn, New York</font></div></div><div><br></div></div></div></div>
<br><div class="gmail_quote">On Thu, Jan 7, 2016 at 7:54 PM, Arnold, Hillel <span dir="ltr"><<a href="mailto:harnold@rockarch.org" target="_blank">harnold@rockarch.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><div>I wasn’t thinking of EAD export, actually. </div><div>My thinking was more that having a messaging system in ArchivesSpace which allows people to tie systems together based on events opens the door to exporting data in other models and serializations. Which I think would be a good thing.</div><div><br></div><div>Hillel</div><div><br></div><div><br></div><span><div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;border-width:1pt medium medium;border-style:solid none none;padding:3pt 0in 0in;border-top-color:rgb(181,196,223)"><span style="font-weight:bold">From: </span> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of Brian Hoffman <<a href="mailto:brianjhoffman@gmail.com" target="_blank">brianjhoffman@gmail.com</a>><br><span style="font-weight:bold">Reply-To: </span> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br><span style="font-weight:bold">Date: </span> Thursday, January 7, 2016 at 5:22 PM<br><span style="font-weight:bold">To: </span> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [Archivesspace_Users_Group] Code4Lib 2016 events<br></div><div><br></div><div><div style="word-wrap:break-word">
“Real-time updates” and EAD will never go nicely together. People who aren’t serializing their data to XML as an end-in-itself should consider taking EAD out of the equation and moving the data directly from point A to point B. People who do believe having
archival data serialized as XML is an end-in-itself should in the long run consider an alternative to EAD that is more accommodating to granular updates.
<div><br></div><div><br><div><blockquote type="cite"><div>On Jan 7, 2016, at 5:10 PM, Chris Fitzpatrick <<a href="mailto:Chris.Fitzpatrick@lyrasis.org" target="_blank">Chris.Fitzpatrick@lyrasis.org</a>> wrote:</div><br><div><div style="font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:12pt;font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255)"><div style="margin-top:0px;margin-bottom:0px"><br>
Hi Steve,<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">Yeah, so that might be slightly tricky...if a bunch of components are updated, you don't want to trigger multiple EAD exports for each component update, but just a one time EAD export for all the updates.
EAD export can really require a lot of SQL queries, so that could really kill your database server.<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">But, it that the primary use case for most folks? You want to trigger an EAD export when an associated record ( not just a resource, but a child archival object or instance ) is updated?<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">If so, I think your wanting to hook into the backend rather than the indexer is actually a better idea...<br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">b,chris.<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div><div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif;margin:0px"><div><font size="2">Chris Fitzpatrick | Developer, ArchivesSpace<br>
Skype: chrisfitzpat | Phone: <a href="tel:918.236.6048" value="+19182366048" target="_blank">918.236.6048</a><br><a href="http://archivesspace.org/" target="_blank">http://archivesspace.org/</a><br></font></div></div></div><br><br><div><hr style="display:inline-block;width:800.656px"><div dir="ltr"><font face="Calibri,sans-serif" style="font-size:11pt"><b>From:</b><span> </span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>
<<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of Majewski, Steven Dennis (sdm7g) <<a href="mailto:sdm7g@eservices.virginia.edu" target="_blank">sdm7g@eservices.virginia.edu</a>><br><b>Sent:</b><span> </span>Thursday, January 7, 2016 10:45 PM<br><b>To:</b><span> </span>Archivesspace Users Group<br><b>Subject:</b><span> </span>Re: [Archivesspace_Users_Group] Code4Lib 2016 events</font><div> </div></div><div><div><br></div><div>We would have a similar use case. We have not managed to import all of our legacy EAD into ArchivesSpace, so we </div><div>will want to export EAD from ArchivesSpace to XTF whenever published resources are updated. We were considering</div><div>whether this action should be made more explicit by triggering it on an associated Event instead of just an update, </div><div>so that you could save partial updates without triggering this export chain. </div><div><br></div><div>I was thinking of using Sinatra’s after filters in a backend plugin to trigger a check. </div><div>I hadn’t though of hooking into the indexer. </div><div><br></div><div>— Steve Majewski</div><div><br></div><div><br></div><br><div><blockquote type="cite"><div>On Jan 7, 2016, at 4:05 PM, Arnold, Hillel <<a href="mailto:harnold@rockarch.org" target="_blank">harnold@rockarch.org</a>> wrote:</div><br><div><div style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><div>Yeah, the use cases I’m thinking of largely have to do with pushing to a discovery layer other than the public interface (or triggering an application/service that pulls data out of AS into a discovery system. There’s also the possibility of pushing
to a repository solution too, I suppose. I’m sure there would be other use cases – those are just the ones that I’ve thought of thus far…</div></div></div><div style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><div style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
Hillel</div><div style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><span style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="font-family:Calibri;font-size:11pt;text-align:left;border-width:1pt medium medium;border-style:solid none none;padding:3pt 0in 0in;border-top-color:rgb(181,196,223)"><span style="font-weight:bold">From:<span> </span></span><<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of Chris
Fitzpatrick <<a href="mailto:Chris.Fitzpatrick@lyrasis.org" target="_blank">Chris.Fitzpatrick@lyrasis.org</a>><br><span style="font-weight:bold">Reply-To:<span> </span></span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br><span style="font-weight:bold">Date:<span> </span></span>Thursday, January 7, 2016 at 3:59 PM<br><span style="font-weight:bold">To:<span> </span></span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br><span style="font-weight:bold">Subject:<span> </span></span>Re: [Archivesspace_Users_Group] Code4Lib 2016 events<br></div><div><br></div><div><div dir="ltr"><div style="font-size:12pt;font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255)"><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">Hi,</div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">Great. Maybe we can plan some kind of meetup to do some coding work as well...</div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">I am seeing a convergence of your request and the others for the OAI-PHM responder. I like your idea, since it I think most of it is actually pretty much already built in the indexer, since it polls
the Aspace backend for created/updated/deleted records and triggers some actions to be passed off to another API ( i.e Solr's )<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">I think it would be pretty easy to essentially do something else, like "when a record is created, POST the JSON to this URI". Or maybe something slightly more sophisticated, like push it messaging
queue like Redis or RabbitMQ, that a second service (like a microservice ) could listen to and consume messages.<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">What would a use case be? Like pushing to Blacklight or Primo or Ebsco?</div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">best,chris.<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div><div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif;margin:0px"><div><font size="2"><div>Chris Fitzpatrick |<span> </span><font size="2">Developer, ArchivesSpace</font><br>
Skype: chrisfitzpat | Phone: <a href="tel:918.236.6048" value="+19182366048" target="_blank">918.236.6048</a><br><a href="http://archivesspace.org/" target="_blank">http://archivesspace.org/</a><br></div></font></div></div></div><br><br><div><hr style="display:inline-block;width:805.547px"><div dir="ltr"><font face="Calibri,sans-serif" style="font-size:11pt"><b>From:</b><span> </span><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a><span> </span><<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
on behalf of Arnold, Hillel <<a href="mailto:harnold@rockarch.org" target="_blank">harnold@rockarch.org</a>><br><b>Sent:</b><span> </span>Thursday, January 7, 2016 7:47 PM<br><b>To:</b><span> </span>Archivesspace Users Group<br><b>Subject:</b><span> </span>Re: [Archivesspace_Users_Group] Code4Lib 2016 events</font><div> </div></div><div><div><div><div>Hey Chris,</div><div>I’ll be at Code4Lib too, although I’m already committed to other sessions for the preconference.</div></div></div><div><br></div><div>One idea we’ve been batting around here is some sort of messaging system (inspired by Github’s webhooks [1]) which would allow authorized users to activate customizable HTTP callbacks for events, for example creation, modification or deletion
of a resource or component. It seems like people have taken a number of approaches to figuring out when data changes in AS, but as far as I know all of these involve some sort of regularly scheduled cron job that looks at the Solr index or makes a ton of API
calls. It would be amazing if the system could send notifications out – I think it would allow for much more efficient and flexible integration with other systems.</div><div><br></div><div>Hillel</div><div><br></div><div><div><div>-----------</div><div>Hillel Arnold</div><div><font face="Calibri,sans-serif">Assistant Director, Head of Digital Programs</font></div><div>Rockefeller Archive Center</div><div><a href="tel:914.366.6382" value="+19143666382" target="_blank">914.366.6382</a></div></div></div><div><br></div><span><div style="font-family:Calibri;font-size:11pt;text-align:left;border-width:1pt medium medium;border-style:solid none none;padding:3pt 0in 0in;border-top-color:rgb(181,196,223)"><span style="font-weight:bold">From:<span> </span></span><<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of Chris
Fitzpatrick <<a href="mailto:Chris.Fitzpatrick@lyrasis.org" target="_blank">Chris.Fitzpatrick@lyrasis.org</a>><br><span style="font-weight:bold">Reply-To:<span> </span></span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br><span style="font-weight:bold">Date:<span> </span></span>Thursday, January 7, 2016 at 7:29 AM<br><span style="font-weight:bold">To:<span> </span></span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br><span style="font-weight:bold">Subject:<span> </span></span>[Archivesspace_Users_Group] Code4Lib 2016 events<br></div><div><br></div><div><div dir="ltr"><div style="font-size:12pt;font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255)"><div style="margin-top:0px;margin-bottom:0px">Hi,</div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">There was a question shortly before the holidays about some Aspace-related activities at Code4Lib this year in March.<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">I am planning on attending, and will be at the<a href="http://2016.code4lib.org/workshops/Code4Arc/" target="_blank"><span> </span>Code4Arc pre-conf<span> </span></a>,
which was a great session we had last year at C4L.<span> </span></div><div style="margin-top:0px;margin-bottom:0px">I am thinking of also signing up to lead a breakout session one of the days, and might put together something for a lighting talk.</div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">Is anyone else planning on going? Are there some possible ideas that anyone has or would like to see if attending? We might be able to expand on the breakout, if there's critical mass to possibly meet
more somewhere.</div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">Best, Chris.<span> </span><br></div><div style="margin-top:0px;margin-bottom:0px"><br></div><div><div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif;margin:0px"><div><font size="2"><div>Chris Fitzpatrick |<span> </span><font size="2">Developer, ArchivesSpace</font><br>
Skype: chrisfitzpat | Phone: <a href="tel:918.236.6048" value="+19182366048" target="_blank">918.236.6048</a><br><a href="http://archivesspace.org/" target="_blank">http://archivesspace.org/</a><br></div></font></div></div></div></div></div></div></span></div></div></div></div></div></span><span style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"></span><span style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">_______________________________________________</span><br style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Archivesspace_Users_Group
mailing list</span><br style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a></span><br style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a></span></div></blockquote></div><br></div></div></div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Archivesspace_Users_Group
mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a></span></div></blockquote></div><br></div></div></div></span></div>
<br>_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br></blockquote></div><br></div></div></div></div>