[Archivesspace_Users_Group] problem with collection-level Digital Object links

Edgar Garcia edgar-garcia at northwestern.edu
Mon Dec 4 15:07:30 EST 2017


There is a pull request that I believe touches on this: https://github.com/archivesspace/archivesspace/pull/1047

I think this is why it happens.

I’ve been trying to look over this code because this pull request I think will break because our digital repository doesn’t accept POST requests for our object pages and it was requiring us to refresh the page for it to load.

I *think* when a thumbnail is missing, the page uses a form as a link instead of an anchor tag and that is where GET/POST. I haven’t been able to figure out why this was the decision.

Does anyone else know the answer to this? I’d rather some generic icon/img be used with an anchor tag to avoid this form/POST issue.

Edgar Garcia
Senior Software Developer
Discovery Platform Services
Metadata & Discovery Services
Digital Strategies
Northwestern University Libraries
Northwestern University
Evanston, IL 60208

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Benn Joseph <benn.joseph at northwestern.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Monday, December 4, 2017 at 1:53 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] problem with collection-level Digital Object links

Hi all,
Strange problem here, but perhaps there’s an easy solution. For some of our Resource records we’re trying to create a collection-level Digital Object that will contain a link to the area on our repository that contains digitized content from those collections. For a collection of glass slides, for instance, will create a collection-level Digital Object with this link as the File URI:


What we’ve discovered, though, is that even though the whole link is in there, ArchivesSpace somehow drops everything after the question mark and leaves you with:


…which is just a link to the main Images Repository intro page (not very helpful).

So, we decided to get around this by creating an ARK for each publicly available image collection in our Images Repository and using that as the File URI in ArchivesSpace. This works great! But only in Firefox and Internet Explorer. Chrome and Safari take the ARK (http://n2t.net/ark:/81985/n2t19k<https://urldefense.proofpoint.com/v2/url?u=http-3A__n2t.net_ark-3A_81985_n2t19k&d=DwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=qL9mtrzN5YM9JLty72jmSvS2xXL_z4-MUTBxVwpL3SM&m=nIbrgvRzWkv6cogejgr_s-4XfBKELuEIFInE9xtIm9E&s=ucJHzb1my_-9169XBGPTll1pyR6sXv7L3cguGNwvRkg&e=>, for example) and add a question mark (“?”) to the end of the url, which results in a page displaying an error message relating to our ARK setup. It appears that ArchivesSpace is adding this question mark, but whereas Firefox just ignores it (and makes it go away), Chrome gets tripped up.

We tried using a bit.ly link in desperation, and it works just fine in all browsers…but we’d prefer not to actually start using bit.ly links in finding aids on our production server. Does anyone know how we can go about creating collection-level Digital Object links to our digitized materials in a stable manner? Seems like ArchivesSpace can link to an image file no problem, but it gets confused with other types of urls.


Benn Joseph
Head of Archival Processing
Northwestern University Libraries
Northwestern University
benn.joseph at northwestern.edu<mailto:benn.joseph at northwestern.edu%0d>

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

More information about the Archivesspace_Users_Group mailing list