Custom GUIDs
User defined custom GUIDs.
There are no custom GUIDs configured. You can add new GUIDs by clicking on the
button.
Client GUID links
Client <--> WatchState GUID links.
From Client GUID
{{ link.map.from }}
To WatchState GUID
{{ link.map.to }}
Replace
{{ link.replace.from }}
With
{{ link.replace.to }}
There are no client GUID links configured. You can add new links by clicking on the
button.
- Using this feature allows you to extend
WatchState to support more less known or regional
specific metadata databases. We cannot add support directly to all databases, so this feature instead
allow you to manually do it yourself.
-
Adding Custom guid without a client/s links is useless as the parsing engine will not know what to do with
it. So, make sure to add a client GUID link referencing the custom GUID.
- The guid names are unique. Therefore, you cannot reuse existing ones.
- You cannot add link from the same client GUID twice. For example you cannot add
jellyfin:foobar ->
WatchState:guid_foobar and another for jellyfin:foobar -> guid_imdb.
- Editing the
guid.yaml file directly is unsupported and might lead to unexpected behavior.
Please use the WebUI to manage the GUIDs. as we expose the entire functionality via the WebUI. with
safeguards to prevent you from doing something that might break the system.
- If you added or removed Custom GUID, you should run
system:index --force-reindex
command to rebuild the database indexes. While not required, it is recommended to ensure the database is
up to date. and the indexing is correct and for speedy database operations.
- The links are global for each client, not the backend itself. So, For example, if you have NN jellyfin
backends and you add new GUID link for jellyfin, it will be applied to all jellyfin backends. The backends
themselves don't need to report it, however the support will be available for all backends.
- For more information please read the content in the
FAQ.md page, or directly via
this link