Thanks for posting the examples of how to configure, but just want to be sure I understand what's expected as a result.trixmoto wrote:Ok, here goes!! You can select any field from the list, and then choose a white- or black-list, then you can list the specified items in a comma separated list...
This will only import matches where Genre from Last.fm is either Pop, Rock or Jazz. No other hits - correct?Genre | White | Pop,Rock,Jazz
If you want you can use an automatic whitelist, this means that all the current values in the database for that field are used...
Genre | White | *
If you want you can now used the automatic whitelist from another field...
Custom1 | White | *Genre
If you want to include values which is not in the automatic whitelist, you can add them - you can also remove them (I call these "modifications")...
Genre | White | *+Pop+Rock-Jazz-Sountrack
You can also use a wildcard character in the modifications, either at the beginning or the end...
Genre | White | *+Pop%+%Rock-Jazz-Soundtrack
I think that's most stuff covered, hopefully it should be fairly powerful and allow you to do most things. If you set the log level up higher and check out the logfile then the list is written there so you can check that your modifications are working as expected.
trixmoto wrote:Yes, if you specify a whitelist then only these values should be allowed.
With the automatic whitelist the values are taken from the database, so maybe you have some genres in the database which are not appearing in your tree, I'm not sure why this would be.
I forgot to mention one other thing. You can add translations using the equals sign - by the sound of it you want...
Genre | White | *%Rock=Rock
Yes, the current Genre values would be used to populate the Custom1 field in my earlier example.
The modifications are applied to the whitelist, so in my example Pop and Rock would be added (if they didn't already exist in the list) and Jazz and Soundtrack would be removed (if they did already exist in the list). Then only values returned from Last.Fm that were in the list would be used.
The values are not added to the automatic whitelist during the processing. The first time the whitelist is calculated it is then stored for the rest of the processing to improve performance.
You can play around with these options by increasing the log level and ticking the confirmation screen option. Then you can cancel thus not making any changes, and check the logfile to see what happened with the lists.
MM3 monkey wrote:Thanks for asking all these questions, bob61. Please keep it up.
I'd love to have "idiots guides" for this script and other ones ('extract fields' and especially magic nodes).
Even the (very valuable) information you've gleaned above will soon just be hidden away on page 12 of the script thread.
I'm eagerly anticipating the 'changes to the website' which are going to come with the official release of MM3. Hopefully it will involve a structure for making information about scripts easier to find - and better still, some good tutorials and examples.
Ditto!As always I want to make clear that above all I am very grateful to all the scripters and skinners for anything
trixmoto wrote:@nynaevelan - at the moment this is not possible, you can only get the automatic whitelist from a single field.
trixmoto wrote:@bob61 - I'll check this out and see what I can do, maybe mixing the wildcard and translation doesn't work at the moment.
Users browsing this forum: No registered users and 18 guests