Edit Plex metadata and understand why a refresh keeps the value

The useful distinctions

• Manual metadata changes lock affected fields.
• Locked fields do not update during metadata refreshes.
• The Edit Details interface exposes the lock state.
• Changes must be saved to persist.

Decide who owns the field

A local recording title and a provider-supplied release date may have different authorities. Decide which fields you intentionally maintain rather than locking everything after one correction. Keep the original wording in a note before editing so an accidental change can be reversed. A field-level plan is easier to maintain than a vague instruction that the whole item should never change again.

Read persistence as behavior

If a carefully edited summary survives a refresh, that can be the intended result of its locked state. Conversely, a field that should follow provider corrections may need to be unlocked. Inspect the actual state instead of repeatedly refreshing and expecting a different outcome. The synthetic review note separates a locally authored training title from metadata that can continue to be supplied automatically.

Keep the edit review small

Change one field, save it and inspect the item outside the editor. Confirm identity and path before making a series of similar edits across the library. In a shared administration workflow, record why a value was intentionally made local so another maintainer does not unlock it as a supposed repair. Presentation of lock controls can differ by web release, so follow the visible field state rather than relying on an old screenshot’s colour.

A focused way to proceed

1. Open Edit Details for the intended item.
2. Change only the title, summary or other field you intend to own locally.
3. Inspect the visible lock state for that field.
4. Save and verify the displayed value.
5. If provider updates should resume, unlock that field through the installed interface and refresh selectively.

Worked example · synthetic

Title: locally curated → retain lock
Summary: locally authored → retain lock
Other provider fields: review independently
Change reason: describe the intended editorial correction

Read the comparison

A refresh leaving a locked value unchanged is expected and does not prove refresh failed.

When to stop or ask for help

If the state is unclear, record web/server versions and the affected field before mass unlocking metadata.