[Archivesspace_Users_Group] exporting an identifier for use in a URL to the public user interface

[Karen Miller]

Thank you, Steven!

I’m going to pass this along to our developer so he can implement it. I get the gist of it, but my coding skills stop at XSL. I really appreciate the quick and detailed response!

Karen


Karen D. Miller
Monographic Cataloger/Metadata Specialist
Northwestern University Libraries
Northwestern University
1970 Campus Drive
Evanston, IL 60208
www.library.northwestern.edu
k-miller3 at northwestern.edu
874.467.3462

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Monday, October 31, 2016 11:59 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] exporting an identifier for use in a URL to the public user interface



In the staff interface, there is a ‘View Published’ button (in the same row as the ‘Edit’ button) that takes you to the resource in the public interface.

The template code producing that button is in frontend/app/views/shared/_resource_toolbar.html.erb :


https://github.com/archivesspace/archivesspace/blob/master/frontend/app/views/shared/_resource_toolbar.html.erb#L37-L41<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_master_frontend_app_views_shared_-5Fresource-5Ftoolbar.html.erb-23L37-2DL41&d=CwMGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=mSeY-rdXXr63jFudhwZaHzl4qc8jfI7c3LP0OnBTsiA&s=SSlJBRkMsLGptD9crM4rDHMJ4RcJ9itGa1BlSVYOWOM&e=>


          <% if record.publish %>
          <div class="btn-group">
              <%= link_to I18n.t("actions.view_published"), File.join(AppConfig[:public_proxy_url], record.uri).to_s, :target => "_blank", :class => "btn btn-sm btn-default" %>
            </div>
          <% end %>


And all it’s doing is concatenating the AppConfig[:public_proxy_url] and the resource .uri value, which has the repo value embedded. ( If you prefix it with the backend base URI instead, you’ll get the JSON model from the backend API. )



[ Note: If you are proxying public interface thru apache to another virtual host, you probably need to have changed AppConfig[:public_proxy_url] in your config.rb file from it’s default. And even if you’re not proxying, check to make sure it’s not pointing at localhost. ]

— Steve Majewski



On Oct 31, 2016, at 10:51 AM, Karen Miller <k-miller3 at northwestern.edu<mailto:k-miller3 at northwestern.edu>> wrote:

Good morning.

We are getting ready (at long last!) to migrate from Archon to ArchivesSpace at Northwestern University. Currently we have a customized EAD Export from Archon that writes an <eadid at identifier> value that can be stuck to the end of a static URL to create a link back to the finding aid in our customized portal. The portal we use now is a Blacklight interface that draws from finding aids stored in Fedora. When we move to ArchivesSpace, we’ll be using the ArchivesSpace PUI instead of the Fedora/Blacklight setup.

My question is whether there’s a way to export an <eadid> element either with a url attribute that contains a full URL to the finding aid in the PUI or with an identifier attribute that can be used to build a URL. We are currently using the EAD exported from Archon to create records for ingest into our Primo discovery layer and I’d like to continue doing this with ArchivesSpace.

I saw this question raised about a year ago in the Google Group for ArchivesSpace, but the only response was a suggestion to copy the URL from the finding aid in the PUI into the EAD Location field in the Finding Aid Data sub-record in the staff interface before exporting the EAD. We have over 1100 finding aids that we’re going to have to reharvest into Primo (not to mention ArchiveGrid and the Chicago Collections website) with updated URLs, and I just don’t see that as a good option for us.

I though perhaps I could use the URL that appear in the staff interface (like this one):

http://archival2-d.library.northwestern.edu:8080/resources/53/edit#finding_aid

to build the URL that appears in the public user interface (like this one):

http://archival2-d.library.northwestern.edu:8081/repositories/2/resources/53

but that requires knowing the repository that holds the resource. I suppose that could be gotten from the filedesc\publicationstmt, but it seems a little inelegant, and perhaps dicey as well.

Has anybody else come up with an elegant solution to this issue? I can’t imagine we’re the only institution that’s repurposing our EAD. Any suggestions are appreciated!

Karen

Karen D. Miller
Monographic Cataloger/Metadata Specialist
Northwestern University Libraries
Northwestern University
1970 Campus Drive
Evanston, IL 60208
www.library.northwestern.edu<http://www.library.northwestern.edu/>
k-miller3 at northwestern.edu<mailto:k-miller3 at northwestern.edu>
874.467.3462

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwMGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=mSeY-rdXXr63jFudhwZaHzl4qc8jfI7c3LP0OnBTsiA&s=ldvZX13JbQnwmOZwZczOV1zZHENuYJrZqJdfEPTT9iA&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161031/73238f35/attachment.html>