What's your idea?
Only show metadata source fields on the metadata edit page if that metadata source is available for the current library.
Since one of the app’s strong points is its metadata editor, and there have already been several requests for additional metadata sources, the metadata edit page could become more crowded over time. Some of those sources may only be relevant to certain library types.
For example, if a library is configured to use only specific metadata providers, then the edit metadata page should only show fields for those available providers instead of showing every possible metadata source field.
What problem does it solve?
This would make the metadata edit page cleaner and easier to use.
Currently, metadata source fields that are not relevant or not enabled for a specific library may still appear in the edit page. As more metadata sources are added, this can make the editor feel cluttered and confusing, especially when a user manages different types of libraries with different metadata providers.
For example, a light novel library may need different metadata sources than a general book, manga, comic, or audiobook library. Showing only the fields that are usable for that specific library would make the edit page more focused.
Anything else? (optional)
This would pair well with library-level metadata provider settings. If a provider is disabled or unavailable for a library, its related metadata source fields should be hidden from that library’s edit metadata page.
This would also help future-proof the metadata editor as more metadata sources are added.
Also, the visibility logic should also account for metadata overrides. If a metadata source is enabled through global defaults, library-level settings, or library-specific overrides, then its fields should be shown. If a source is disabled or removed for that library through overrides, then its fields should be hidden from the edit page.
In other words, the edit page should reflect the effective metadata configuration for the current library, not just the global/default configuration.
Want to help?
I can help test and give feedback
Before submitting
What's your idea?
Only show metadata source fields on the metadata edit page if that metadata source is available for the current library.
Since one of the app’s strong points is its metadata editor, and there have already been several requests for additional metadata sources, the metadata edit page could become more crowded over time. Some of those sources may only be relevant to certain library types.
For example, if a library is configured to use only specific metadata providers, then the edit metadata page should only show fields for those available providers instead of showing every possible metadata source field.
What problem does it solve?
This would make the metadata edit page cleaner and easier to use.
Currently, metadata source fields that are not relevant or not enabled for a specific library may still appear in the edit page. As more metadata sources are added, this can make the editor feel cluttered and confusing, especially when a user manages different types of libraries with different metadata providers.
For example, a light novel library may need different metadata sources than a general book, manga, comic, or audiobook library. Showing only the fields that are usable for that specific library would make the edit page more focused.
Anything else? (optional)
This would pair well with library-level metadata provider settings. If a provider is disabled or unavailable for a library, its related metadata source fields should be hidden from that library’s edit metadata page.
This would also help future-proof the metadata editor as more metadata sources are added.
Also, the visibility logic should also account for metadata overrides. If a metadata source is enabled through global defaults, library-level settings, or library-specific overrides, then its fields should be shown. If a source is disabled or removed for that library through overrides, then its fields should be hidden from the edit page.
In other words, the edit page should reflect the effective metadata configuration for the current library, not just the global/default configuration.
Want to help?
I can help test and give feedback
Before submitting