I am developing a Web Sources Script for a site . I've encountered a structural limitation in the Web Sources framework regarding how search results are handled.
Currently, the [ParserScriptIndex] generates a list of results. However, the Mp3tag interface only allows selecting one single entry to proceed to the [ParserScriptAlbum] stage.
My issue is that for multiple media files, the metadata I need is spread across two or more different search result pages. Because the current framework enforces a "one Index entry to one media file" relationship, I cannot pull data from multiple URLs simultaneously into the tags of files.
Is there any way to enable multiple selection in the search result dialog so the parser can fetch data from multiple URLs for multiple files?
Sadly no, it’s one request at a time, one result passed through at a time.
I support the idea of multiple requests being made, as you say metadata can be split across multiple parts of a website/calls to an API. As unlikely as it is, it could be open to abuse or mistakes pulling excessive amounts of data so I’m not sure if it’ll be considered.
You could cheat “multiple” search results if all the metadata you need is in the [ParserScriptIndex] stage to combine into “one result” or however permutations needed to get what you want.
Until then, would you mind sharing what site you’re interested in developing a script for to help explore your options?
Data for the same series of products is spread across different pages.
If I set precise keywords, I can find all the products from the same series in the search results. I have finished the script, but it can only fetch data for one product at a time because there is no way to select multiple entries.
Ah, apologies. Every web source has got the same limitation.
It might seem inconvenient at first but it might be easier in the long run for your users focusing on tagging one product at a time.
The only other suggestion I could offer is if those precise keywords can be broken up into tags like TITLE, ALBUM or even GENRE, your users can save that into their files before-hand.
You can then load those tags as %placeholders% into [SearchBy] and construct a search for your users automatically. That way, it’s less tedious typing or copy-pasting a search for the same series over and over. e.g. a search for any "Undertale" CD's could be saved to ALBUM :
Thanks for the clarification and the suggestion! It seems the current framework indeed has its limitations regarding multi-selection. I appreciate your help and the insights into how the web sources script handles these requests!