I think a few things need to be added to Web Source Script interface:
-
User should be able to exclude certain tags in the media file's update popup regardless of the script. E.g. a Discogs/Amazon/MusicBrainz script can fill 15 tags although user wants to use the same script and just leave certain tags untouched.
Each field/column should be somehow included/excluded from update (a checkbox maybe???). An option to save the selection as a variant could be provided.
I think this "wish" was already requested?
-
[SearchBy] popup window should be enhanced with an advanced mode (new button) to support multiple search fields. Something like discogs manual search http://www.discogs.com/search?q=&btn=&type=all.
I.e. search by artist, album, release ID.
[SearchBy]=&artist=$if2(%albumartist%,%artist%)$if(%album%,&release_title=%album%,)$if(%discogs_release_id%,&release_id=%discogs_release_id%,)
currently sets [SearchBy] to &artist=Talking Heads&release_title=Naked&release_id=2942139 in the WebSource popup.
Search fields/values could be displayed in a matrix.
-------------------------------------
Field | Value
-------------------------------------
artist | Talking Heads
release_title | Naked
release_id | 2942139
--------------------------------------
User could add/change/remove (predefined) selection.
Nothing changes on the WebSource itself. The advanced mode doesn't limit itself in any way. API has to support the listed fields.
We can go even further and provide dynamic solution: the list of all possible filter fields is populated in the script (a new variable). E.g. artist, format, label, year, etc.
-------------------------------------
Field | Value
-------------------------------------
artist | Talking Heads
release_title | Naked
release_id | 2942139
label | N/A
year | N/A
--------------------------------------
N/A means ignore this field from the [SearchBy] parameter.
So far there are 2 ways of joining the fields:
- =&=...&=
most of the sites use this format. e.g. artist=Talking Heads&release_title=Naked
- : AND : ....... AND :
This is used mainly by Musicbrainz api v2. e.g. artist:talking,heads AND release:naked.
The would be useful to not use a dedicated script file for each searchby (IndexURL and AlbumParse stay the same).
If someone is not positive for this addition because of available alternative (sort and search though the results) I reply in advance that the aim of mp3tag is to reduce the time of end-user otherwise why would we use mp3tag? The alternative was before mp3tag was created: fill everything manually.
. Seems like all three web sources are working well.
