<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >Hi Maureen,<div><br></div><div>No, no urls should be changed by this update.</div><div><br></div><div>Brian </div><br><br><div>-------- Original message --------</div><div>From: "Callahan, Maureen" <maureen.callahan@yale.edu> </div><div>Date:09/30/2015 11:45 AM (GMT-05:00) </div><div>To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>, archivesspace@googlegroups.com </div><div>Cc: </div><div>Subject: Re: [Archivesspace_Users_Group] AR-1326 - "I transferred a component and now I can't update it" </div><div><br></div>
<div class="">Thanks for this, Brian — I’m running the database setup locally right now and I’ll be happy to report back.</div>
<div class=""><br class="">
</div>
<div class="">I have a quick (and possibly dumb) question, though — does re-sequencing change the database record ids? Does this then change URLs for records in ArchivesSpace, since these are based on database identifiers? If so, has there been any thought
toward making URLs more semantic/persistent? I can think of a lot of use cases that would favor the persistence of ArchivesSpace URLs, even on the staff side. For instance, folks in my repository are doing a huge clean-up project — the to-do lists that they’re
working from are all tied to ArchivesSpace URLs, which is great since it makes it very easy to go directly to that record, but I would have to re-do this report if URLs changed because of re-sequencing.</div>
<div class=""><br class="">
</div>
<div class="">Thanks much,</div>
<div class="">Maureen</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Sep 30, 2015, at 12:09 AM, Brian Hoffman <<a href="mailto:brianjhoffman@gmail.com" class="">brianjhoffman@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hello ArchivesSpace Users,
<div class=""><br class="">
</div>
<div class="">If you are experiencing issue AR-1326 (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1326&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=AN8tn29sNbYDgihSR2HFfVRHmi8_yBET-i8iUci0zjk&s=_J3S7a66xePOSQXK3vYTRojDiNSEbPDm-1peN9e4n7Y&e=" class="">https://archivesspace.atlassian.net/browse/AR-1326</a>)
please consider testing this development release:</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_releases_tag_AR-2D1326-2Dtest&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=AN8tn29sNbYDgihSR2HFfVRHmi8_yBET-i8iUci0zjk&s=0vwMJqhj-i3X03kFF70Ba1xqz0_dEpzQ7UgGX5b4nzw&e=" class="">https://github.com/archivesspace/archivesspace/releases/tag/AR-1326-test</a></div>
<div class=""><br class="">
</div>
<div class="">You will need to create a test copy of your database and then install this release as normal (on a test server or in a test directory).</div>
<div class=""><br class="">
</div>
<div class="">I know that this issue is affecting Duke and believe Yale may have reported it as well.</div>
<div class=""><br class="">
</div>
<div class="">Thank you,</div>
<div class=""><br class="">
</div>
<div class="">Brian</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</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="">
https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=AN8tn29sNbYDgihSR2HFfVRHmi8_yBET-i8iUci0zjk&s=upiorDh0mqJE-XLAPoAjTue79o2gkWHQSr0X5sFRBsw&e=
<br class="">
</div>
</blockquote>
</div>
<br class="">
</body>