[Archivesspace_Users_Group] Lock Version

Valerie Addonizio vaddoniz at jhu.edu
Thu Nov 10 12:41:32 EST 2016

The lock version is a failsafe to prevent changes being made while a record is in use. It increments automatically every time a change is made.

For instance, if you got a record out through the API and made a change while another user had that same record open (and saved) in the interface, your change would be rejected because it was not the last lock version number. As an experiment, get a record out, make a change, get it out again and you will see the lock version change.

This can complicate large-scale pushes through the API, and forces you to think hard about what will change what (for instance, all the lock version will change on linked accessions when you push in updates resources records).


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?

Kyle Fortney
Computer Specialist
Library Systems
308 Edmon Low Library, OSU
(405) 744-7924

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161110/77545db8/attachment.html>

More information about the Archivesspace_Users_Group mailing list