AllRovi movie script

[Ivek23]

I do this later to see how and what.
Would be generally the script or more for you.

In this case, I do not know help, I did not find a script with such a practical case, it would be nice if it could be somehow regulated, maybe we are Nostra mercy and help.

[Ivek23]

I added a procedure ParseDVDReleases and now here are the DVD Links to AllRovi DVD Releases

The annex was also added in txt format Rovi Fields list

Notice:
Adding in the first post new AllRovi Script Version 0.1.0.8
This version, for those which have the same script option, as it is in Rick.ca.

RICK_CA      = True;   //Set to False for default script options

NEW:
I also added in the first post new AllRovi+ Script Version 0.1.0.8
This version, for those which have the same script option, as it is in Rick.ca. (default script options)

RICK_CA      = False;   //Set to False for default script options


Edit: AllRovi+ Script Version 0.1.0.8 has been removed from the first post because the a duplicate script with one minor change.

[attachment deleted by admin]

[deazo]

 Thanks a lot to both of you Ivek23 and Rick for your efforts, updating my movies right now with this.

[Ivek23]

 Thanks a lot to both of you Ivek23 and Rick for your efforts, updating my movies right now with this.

Welcome

[rick.ca]

Using your example, your 8 Mile record now has the AllRovi URL recorded: http://www.allrovi.com/movies/movie/8-mile-v261159. If you run the script again, the function GetDownloadURL will retrieve that from the record and use it to access the page directly—no search will be done. It's able to select that URL from the URL field—which may contain many URL's—because we've provided the BASE_URL: http://www.allrovi.com.

I don't understand the logic of the script, but there must be a way use this function like this:

• with BASE_URL = 'http://www.allrovi.com';
• if there is no result, again with BASE_URL = 'http://www.allmovie.com';
• if a URL is retrieved, then ParsePage;
• otherwise, do the search.

Just to be clear, the only thing different here is step 2. And I don't think the script has much to do with step 4—the main application downloads the page (whatever it is) and ParsePage handles it. For the same reason, I have difficulty seeing a point at which step 2 might be inserted. Unless this is straightforward, it's probably not worth the bother. But I think it would be very helpful generally if we understood how things like this work.

Nostra advises me there's a way to do this. He'll help us with that when he finds the time. Although it's not a critical issue, it will make the script much more efficient for databases that already have allmovie URL's. I also look forward to learning the technique involved. 

[Ivek23]

Nostra advises me there's a way to do this. He'll help us with that when he finds the time. Although it's not a critical issue, it will make the script much more efficient for databases that already have allmovie URL's. I also look forward to learning the technique involved.  

The good news, we are happy to wait for Nostra, to help us.

[rick.ca]

Notice:
Adding in the first post new AllRovi Script Version 0.1.0.8
This version, for those which have the same script option, as it is in Rick.ca.

RICK_CA      = True;   //Set to False for default script options

NEW:
I also added in the first post new AllRovi+ Script Version 0.1.0.8
This version, for those which have the same script option, as it is in Rick.ca. (default script options)

RICK_CA      = False;   //Set to False for default script options

It's not necessary to post a new script in which the only difference is an option. This and other such options are intended to be set by the user. If one wishes to use the personal options I've added to the script (they can search for "if RICK_CA then" to see what those are), they will set RICK_CA to 'True'. The reason for doing it this way is so we do not have to maintain two versions of essentially the same script.

I have revised the top post accordingly.

[Ivek23]

I have revised the top post accordingly.

OK, that's right that there is only one version of the script, sorry, I just wanted to help, it would not be necessary to change these settings in the script.

[rick.ca]

Version 9 attached (and to top post). Just a few minor changes to Ivek's version 8...

• corrected 'ParseSearchResults' to include 'Year' in search results dialog
• changed 'DVDs RoviLink' to include only 'Name' in hyperlink
• replaced 'FIELD STATUS' reference with 'FIELD USE' (thanks, Ivek)

[attachment deleted by admin]

[Ivek23]

Year in Search Results is the one piece of code which part I am not able to add search result, btw; look at it SCRIPT_VERSION  ,something is not changed.

[Ivek23]

I changed only the number of SCRIPT_VERSION

[rick.ca]

I changed only the number of SCRIPT_VERSION

Thanks. I changed the attachment to my above post as well.

Year in Search Results is the one piece of code which part I am not able to add search result

That's what I changed. The search results dialog should now include the year.

[Ivek23]

Year in Search Results is the one piece of code which part I am not able to add search result,

I tried to say that I have not found the correct solution in previous versions to see the year in the search results dialog.

That's what I changed. The search results dialog should now include the year.

It works.

[minolotus]

The annex was also added in txt format Rovi Fields list

Thank you for the file, this has been very helpful.

I have recently started to update my database and the script is running perfect.  Thank you very much to both of you, Ivek23 and rick.ca!

[Ivek23]

The annex was also added in txt format Rovi Fields list

Thank you for the file, this has been very helpful.

I have recently started to update my database and the script is running perfect.   Thank you very much to both of you, Ivek23 and rick.ca!

We always welcome.

[Ivek23]

The annex was also added in txt format Rovi Fields list

Open the WordPad or anything else, because they might be some changes, as it is written in txt format Rovi Fields list.

[rick.ca]

The annex was also added in txt format Rovi Fields list

This has been added to the script itself—as part of it's "self-documentation." We'll maintain it there.

Code: [Select]

FIELD USE:

Rovi data:          PVD field:          Type:

AMG ID              AMG WID             short text
Category            Work type           multiselect list
Cast                Cast                memo
Characteristics     Characteristics     memo
Country             mfCountry           standard multiselect list *
Director            mfDirector          standard multiselect list *
Flags               Flags               multiselect list
Run time            Run time            number
Genres              mfGenres            standard multiselect list *
MPAA rating         MPAA rating         short text
Produced            mfStudio            standard short string *
Production(crew)    Production          memo
Rovi rating         Rovi rating         rating
Review              Review              memo
Release date        Released            short text (multiple dates)
OR     Released     Released            short text (more common single date)
Releases            mfFeature           standard memo (link to Rovi Releases tab saved)
             OR     DVDs RoviLink       memo (link each Rovi DVD page saved)
Released by         Released by         short text
Synopsis            mfDescription       standard memo
Sub-Genres          Types               multiselect list
Title               mfTitle             standard short text
Year                mfYear              standard number
             OR     Year                short string (or revise code to save as integer)
Themes              Themes              multiselect list
             OR     mfCategory          standard multiselect list (RICK_CA option)
Updated             Updated             long text
URL                 mfURL               standard memo *

* In many cases where data is saved to a standard field,
the script also saves the data to custom field of the same name.
This allows a number of options:

1. Use the data saved to the standard field (normally the default) and ignore the custom field.
Data saved to a non-existent custom field goes nowhere.

2. Ignore the data entirely by disabling the standard field in the "Overwrite fields" options.

3. Add the custom field to PVD and disable the standard field so it's free for use by another plugin or script.

These optional custom fields are named the same as their standard counterparts.
To avoid confusion, you may wish to rename them (i.e., in the script, in PVD and your skin).
For example, change "Year" to "Rovi Year"--so as to not be confused with the standard field used by another source.

Hopefully it will be clear—maybe from the notes at the bottom—this is only meant to point the user in the right direction. There's no avoiding the inherent complexity involved in getting data from a secondary source (most of us will get data from Rovi in addition to a primary source like IMDb). The user must decide what information they want and were to put it. This will very likely involve modifying the script to suit their personal preferences. This is one of the reasons for providing a scripting engine—so options, fields used and minor modifications can be made directly to the script by the user. Other than the standard Overwrite fields options, no script options are available in the UI.

[RazorHall]

Hey guys, thanks for your hard work on this script.  I'm having some problems, though.  When I add a new movie, I'm getting information in most fields, but I'm not getting the Rovi Rating, cast, or run time.  I've made no changes to the script itself and made sure that the appropriate boxes are selected in the "overwrite fields" section.  Any idea what might be keeping the above info from being downloaded?

[rick.ca]

but I'm not getting the Rovi Rating, cast, or run time.

These all require custom fields. Have you added them to the database (at Preferences>Movies>Custom items)? Are they of the right type (rating, memo and number)?

[RazorHall]

These all require custom fields.

Oh, okay.  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?  If this can be explained in simple terms, anyway.