[Archivesspace_Users_Group] AR-1326 - "I transferred a component and now I can't update it"
maureen.callahan at yale.edu
Wed Sep 30 11:45:02 EDT 2015
Thanks for this, Brian — I’m running the database setup locally right now and I’ll be happy to report back.
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.
On Sep 30, 2015, at 12:09 AM, Brian Hoffman <brianjhoffman at gmail.com<mailto:brianjhoffman at gmail.com>> wrote:
Hello ArchivesSpace Users,
If you are experiencing issue AR-1326 (https://archivesspace.atlassian.net/browse/AR-1326<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=>) please consider testing this development release:
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).
I know that this issue is affecting Duke and believe Yale may have reported it as well.
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group