[Archivesspace_Users_Group] ArchivesSpace admin/frontend URLs are context dependent

[Chris Fitzpatrick]

Hi Steve,


Yes, that's a feature.


The idea, I think, is in the staff UI  the select repository serves as the context. So searching and browsing is restricted to the selected repository.


However, I do see a use for having a specific staff ui link that can be shared and redirect to directly to an object...currently you'd have to provide the link and say what repository it's in.

b,chris.



Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Steven Majewski <sdm7g at virginia.edu>
Sent: Thursday, December 11, 2014 7:07 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] ArchivesSpace admin/frontend URLs are context dependent


Not sure if it's a bug or a mis-feature:

We just discovered that ArchivesSpace admin/frontend URLs are context dependent on which repo is selected.

When I send a URL to a colleague and they attempt to open it, if they have a different repo
selected from the one I have selected, they get the error:

Record Not Found

The record you've tried to access may no longer exist or you may not have permission to view it.

This is going to make collaboration somewhat awkward!


The public links don't have that context dependency, and to link back to the frontend EDIT uri,
the EDIT button uses an indirect link:

http://archives-test.lib.virginia.edu:8080/resolve/edit?uri=/repositories/8/resources/3978&autoselect_repo=true




- Steve Majewski / UVA Alderman Library
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141212/9a950274/attachment.html>