Skip to content

Commit

Permalink
More explicit words about restoring metadata backup (#2337)
Browse files Browse the repository at this point in the history
  • Loading branch information
chazlarson authored Dec 3, 2024
1 parent a26a9b6 commit 94f8d45
Showing 1 changed file with 15 additions and 2 deletions.
17 changes: 15 additions & 2 deletions docs/config/operations.md
Original file line number Diff line number Diff line change
Expand Up @@ -869,8 +869,7 @@ You can create individual blocks of operations by using a list under `operations
<div id="metadata-backup" />Creates/Maintains a Kometa Metadata File with a full `metadata` mapping based
on the library's items locked attributes.

If you point to an existing Metadata File then Kometa will Sync the changes to the file, so you won't lose non plex
changes in the file.
If you point to an existing Metadata File then Kometa will sync the changes to the file, so you won't lose non plex changes in the file.

<hr style="margin: 0px;">

Expand All @@ -896,3 +895,17 @@ You can create individual blocks of operations by using a list under `operations
sync_tags: true
add_blank_entries: false
```

The resulting metadata file can be used like any other [metadata file](../files/metadata.md) in Kometa, for example, you can use it to apply metadata to a new library or to restore metadata to a library.

???+ example "Example"

```yaml
libraries:
Movies:
metadata_files:
file: config/Movie_Backup.yml # restore this metadata file to the library
Movies - Alternate:
metadata_files:
file: config/Movie_Backup.yml # apply this metadata file to the library
```

0 comments on commit 94f8d45

Please sign in to comment.