<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div>Not sure if it’s a bug or a mis-feature: </div><div><br></div><div>We just discovered that ArchivesSpace admin/frontend URLs are context dependent on which repo is selected. </div><div><br></div><div>When I send a URL to a colleague and they attempt to open it, if they have a different repo</div><div>selected from the one I have selected, they get the error:</div><div><br></div><div><h2 style="margin: 10px 0px; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; line-height: 40px; color: rgb(185, 74, 72); text-rendering: optimizelegibility; font-size: 29.25px; background-color: rgb(242, 222, 222); position: static; z-index: auto;">Record Not Found</h2><p style="margin: 0px 0px 10px; color: rgb(185, 74, 72); font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 13px; line-height: 20px; background-color: rgb(242, 222, 222); position: static; z-index: auto;">The record you've tried to access may no longer exist or you may not have permission to view it.</p></div><div><br></div><div>This is going to make collaboration somewhat awkward! </div><div><br></div><div><br></div><div>The public links don’t have that context dependency, and to link back to the frontend EDIT uri, </div><div>the EDIT button uses an indirect link:</div><div><br></div><div></div><div><a href="http://archives-test.lib.virginia.edu:8080/resolve/edit?uri=/repositories/8/resources/3978&autoselect_repo=true">http://archives-test.lib.virginia.edu:8080/resolve/edit?uri=/repositories/8/resources/3978&autoselect_repo=true</a></div><div><br></div><div><br></div><div><br></div><div><br></div><div>— Steve Majewski / UVA Alderman Library</div></body></html>