You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running large metadata refreshes which include IG as a source ("Official store" set as source for some of the fields such as tags and release date), the metadata search window frequently pops up (for potentially hundreds of IG entries) and interrupts the metadata download for potentially thousands of other non IG entries which can be quite disruptive. I therefore suggest the following behavior to help mitigate/resolve:
Run metadata search in the background without opening a window
If 1 result is found, automatically select it without prompting
If no result is found, skip without warning (similar to Humble bundle)
If >1 results are found, pick first
If after selecting a metadata result, there is a failure (which currently sometimes shows another modal blocking further progress with prompts such as "Request with no data..."), silently skip. Of note there are situations where the metadata search windows shows a result but after selecting it the no data prompt comes up and no image/data is saved for the entry even though one showed up in the results (might be a bug)
Have a log entry for each failed/auto added metadata entry
Make this entire behaviour optional or configurable for each scenario under plugin settings
I don't know how feasible this is but it would greatly help automating this process that currently requires much manual supervision.
The text was updated successfully, but these errors were encountered:
When running large metadata refreshes which include IG as a source ("Official store" set as source for some of the fields such as tags and release date), the metadata search window frequently pops up (for potentially hundreds of IG entries) and interrupts the metadata download for potentially thousands of other non IG entries which can be quite disruptive. I therefore suggest the following behavior to help mitigate/resolve:
I don't know how feasible this is but it would greatly help automating this process that currently requires much manual supervision.
The text was updated successfully, but these errors were encountered: