English > Scripts and Templates
AllRovi movie script
rick.ca:
--- Quote ---So, why are the custom fields needed instead of that info going into the Additional Rating, Actors, and Duration fields as they did with the old AllMovie script?
--- End quote ---
The reason is as I explained above. There are all sorts of ways you might want it to work. It's up to the user to modify/configure it according to his particular needs. Having said that, there's a logical reason for the default handling of each of the items you mention...
Rovi rating is not put in [orating] because that's the only field available to a secondary plugin. A script has the option of using a custom field, so that's what's used. If there is no likelihood of ever needing to use a secondary plugin, set the GET_RATING option to 'True' to put it in [orating].
Actors (and other people fields) should be filled by a source that can provide both movie and people data—like IMDb. If you are maintaining people data, mixing sources is a bad idea. If this script is your primary source, set the GET_ACTORS option to 'True' to put it in [Actors].
Run time is that of the original theatrical release. In PVD, [Length] (aka 'Duration') is that of the actual media—as scanned by the program. The very point of getting Rovi's Run time is the two are not necessarily the same. I suppose another use of the data could be to provide a duration for records for which there is no media (e.g., 'Wish list' items). When media is acquired, it would be overwritten. If there's an expressed need, I'll add an option for that.
BTW, in looking at the original Allmovie script, I see it has a "Custom field names to use" section for setting those in script variables. Maybe we should do that, so it would be a little easier for users to change the field names to whatever they want to use. The same variables could also be used to indicate if the default PVD field should be used. Each available data element would be set to 'Default' or '[a custom field name]'. Then the code would be something like...
--- Code: ---if ROVI_DATA = 'Default' then
AddFieldValue(mfField, TmpStr)
else
AddCustomFieldValueByName(ROVI_DATA, TmpStr);
--- End code ---
The current "Field Use" documentation could be replaced with a "Fields to Use" section in which all the field variables are set. 8)
minolotus:
--- Quote ---BTW, in looking at the original Allmovie script, I see it has a "Custom field names to use" section for setting those in script variables. Maybe we should do that, so it would be a little easier for users to change the field names to whatever they want to use.
--- End quote ---
I think this is a good idea.
Another suggestion: Maybe it would be helplful if you start a new topic regarding the allrovi script and this new topic should be sticked to the the top instead of this topic. The new topic should include the current version of the scipt and all basic information for the users, e.g.
- Which information could be downloaded,
- Which PVD fields are used,
- which alternative custom fields could be used, included a short hint how to edit a script and how to add custom fields,
- For further information, suggestions and question a link to this threat.
Even if all the information from above is included in this topic, I suppose that there are several users which may lose track here because of the numbers of posts and the code etc.
It would be a pity if users don’t use your script because they don’t know what features the script includes.
rick.ca:
--- Quote ---Another suggestion: Maybe it would be helplful if you start a new topic regarding the allrovi script...
--- End quote ---
Maybe I'll do that when the script is "released" and included in the automatic update system. I suppose users seeing it there may appreciate a more concise and easier to find description and instructions. Ideally, however, a script should be fully self-documented. If I'm curious about a script in the update list, I should be able to install it, open it in an editor, see all the necessary instructions, set my personal preferences, and go. To that end, there should be a View/Edit/Configure this script button in Preferences > Plugins that opens the selected script in the default editor. Or just using the existing Configure button would do.
minolotus:
I agree, if the information would be avaiable directly in PVD and the configuration could also set in PVD, this would be much better and easier to use.
RazorHall:
Thanks! With the above info I was able to get the script to download most of the data in question exactly as the AllMovie one did. :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version