<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class=""><br class=""></div>ArcLight project on GitHub: <a href="https://github.com/sul-dlss/arclight" class="">https://github.com/sul-dlss/arclight</a><div class=""><br class=""></div><div class="">ArcLight is a Ruby/Rails+Solr Gem for searching and displaying finding aids. </div><div class="">The display is somewhat similar in style to ArchivesSpace Public User Interface, but ArcLight is only for serving published finding aids — it has none of the authoring and management capability of the ArchivesSpace staff interface. ArcLight imports EAD finding aids and indexes the pieces in Solr for fast retrieval, so it doesn’t have to parse an entire XML finding aid on each access. </div><div class=""><br class=""></div><div class="">If all of your finding aids are in ArchivesSpace, there is not much to be gained from ArcLight over the ArchivesSpace PUI. </div><div class="">However, if you’ve got legacy EAD finding aids that you cannot yet import into ArchivesSpace, or you are trying to build a union catalog with other institutions, then exporting EAD from different systems is probably the only common denominator. </div><div class=""><div class=""><br class=""></div><div class="">We are currently using XTF <a href="https://xtf.cdlib.org" class="">https://xtf.cdlib.org</a>, <a href="https://github.com/cdlib/xtf.git" class="">https://github.com/cdlib/xtf.git</a> for displaying EAD finding aids online, however that technology stack has gotten a <i class="">little long in the tooth, </i>so we’ve been evaluating ArcLight as a replacement. </div><div class="">My evaluation was based on the initial MVP release, which was a while ago, so they may have fixed some of the issues since then. The main issue I ran into was that ArcLight, like ArchivesSpace, had some restrictions and limitation on the EAD that it would import, particularly on the <eadid> values. I made an attempt to override and fix this, but it was not completely successful, so I had to resort to preprocessing the EAD to transform it to ArcLight’s restrictions. ( ArcLight uses eadid value to link all of the sub records together in Solr index, so fixing this issue was less trivial than making some other mods to the application or EAD import process. I will likely make another attempt to dig deeper into this problem when I have the time. ) </div><div class=""><br class=""></div><div class="">Several Virginia Heritage <a href="http://vaheritage.org" class="">http://vaheritage.org</a> members are also ArchivesSpace members and we have been testing using the ArchivesSpace OAI endpoints as a feed into our current XTF implementation, and if we do migrate to ArcLight, we will use the same method to feed updates. ( <a href="https://github.com/bloomonkey/oai-harvest.git" class="">https://github.com/bloomonkey/oai-harvest.git</a> ) </div><div class=""><br class=""></div><div class="">I had initially thought there might be some way to manage the entire union catalog in ArchivesSpace, but my experience with managing an ArchivesSpace instance with 4 different library repositories convinced me that trying to do the same for a much larger group would not be practical. There might be other ways to build a searchable union catalog of ArchivesSpace instances ( merging Solr records, for example ) however they would all require access to ArchivesSpace backend or Solr service, which are both likely to be restricted or firewalled. </div><div class=""><br class=""></div><div class="">— Steve Majewski </div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 7, 2019, at 5:38 AM, Harm Jager <<a href="mailto:harmjager@ruerddevries.nl" class="">harmjager@ruerddevries.nl</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div class=""><p class="">Hello fellow Archivesspace users, </p><p class="">We are sending this mail out to you because we are currently in the process of doing research in to the best way to use the user-interface of Archivesspace. We would like to use the user-interface not only to present our finding-aids but also those of other institutions in the Netherlands that are complementary to our finding-aids and if possible provide extra information surrounding these Finding-Aids</p><p class="">This brings me to our point. Namely the fact that we recently heard of ArchLight and someone said that would be a good fit for us and our objectives with the staff-interface. We are looking to expand our knowledge when it comes to ArcLight. Using Google to find Archlight brings us to a couple of DuraSpace pages, but that’s it.</p><p class="">Therefore I share the following question/request. Does anyone of you have any experience with ArchLight and if so could you share with us your documentation surrounding ArchLight? We would like to know as much as possible about ArchLight before we start to fiddle around with it. Any links or documents would be greatly appreciated.</p><p class="">Thank you very much for helping us along.</p><p class="">Greetings,</p><p class="">Harm Jager</p></div>
_______________________________________________<br class="">Archivesspace_Users_Group mailing list<br class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br class=""></div></blockquote></div><br class=""></div></div></body></html>