[Archivesspace_Users_Group] Lock Version
ljdavis at jhu.edu
Thu Nov 10 12:38:32 EST 2016
I'm happy to (try to) answer more in depth questions if you've got 'em, but most directly it is a versioning measure. Each time a record is saved, the lock_version increases by one. As we've gone about doing a lot of metadata cleanup here via the API the lock_version has been a constant source of attention/consideration to us as you cannot POST data if there is a lock_version mismatch (this is, indeed, a GOOD thing since it will keep you from posting old data over new!). It gets complicated, though, given the linking of certain record types to others (e.g. accessions linked to resources). For example, we intended - during the process of relinking new subject/agent records to all our accessions and resources - to post ALL our resources and accessions in at once. It ended up that once an accession record was posted with a link to a resource record that the lock versions of BOTH the accession and resource records were upped due to the link between them. We had to GET fresh resource records (with updated lock_versions), link our subject/agents, and then repost just the resources after doing so first with the accessions.
Hope that makes sense and helps,
Lora J. Davis
The Sheridan Libraries
Johns Hopkins University
3400 North Charles Street
Baltimore, MD 21228
ljdavis at jhu.edu
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Fortney, Kyle
Sent: Thursday, November 10, 2016 9:58 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Lock Version
I may be dense but I cannot seem to find an explanation of the lock_version field. Can anyone explain this field?
308 Edmon Low Library, OSU
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group