What went wrong?

When filling in a new metadata field manually, locking the field before saving causes an HTTP 409 error.

The field has to be saved first before it can be locked successfully. Locking it before saving fails.

This is a problem when manually entering metadata such as a provider ID. For example, I may want to manually fill the provider ID, lock it, and then run auto fill so the provider ID is preserved. However, because locking the field before saving causes an error, I have to save it first, then lock it, then run auto fill.

If I run auto fill before locking the manually entered provider ID, there is a chance the provider ID will be changed.

Steps to reproduce

1. Open the metadata editor for an item.
2. Manually fill in a previously empty metadata field, such as a provider ID.
3. Lock the field before saving the metadata changes.
4. Try to save the metadata.

Expected vs actual behavior

Expected behavior is that a newly filled metadata field should be able to be locked before saving, and the metadata should save successfully.

Current behavior is that saving fails with an HTTP 409 error if the newly filled field is locked before saving. The workaround is to save the field first, then lock it afterwards.

Your setup

• BookOrbit version tag: 1.7.0
• Deployment: docker
• OS: Debian Trixie
• Browser: Firefox 151.0.2

Relevant logs (optional)

Screenshots (optional)

Before submitting

• I've searched existing issues and this hasn't been reported yet.