On Sep 18, Alen Ribic <[EMAIL PROTECTED]> wrote:
> What I noticed immediately is that the imdbID I saw previously using
> 'web' accessSystem is not the same id's I see now that I have a
> local sql db.
It's detailed in the documentation here and there.
Definitions:
- imdbID: one of the unique IDs used by _the IMDb web site_ to identify
something (you need to specify if it's a movie/person/character/company).
They are unique (amongst the same kind of information), and never reused.
- movieID/personID/characterID/companyID: IDs that _IMDbPY_ uses to
uniquely identify something.
Using the 'html' and 'mobile' data access system, they are easy to
choose: just use the imdbID!
With 'local' and 'sql' you have to deal with a very sad reality:
IMDb doesn't distribute the associations between imdbID and movies' titles,
people's names and so on.
Uh-oh... that's a nice hill of camel shit to dig into. :-)
You're forced to fabricate them, and it goes without saying that
they never match the imdbIDs.
As a side note: imdbIDs (and movieID/personID/... in the 'http'
and 'mobile') are strings (with leading zeros), while in 'sql'
and 'local' the movieID/personID/... are integers.
> So I am not 100% sure what you mean by "...(on-line, so
> that the "real" imdbID can be retrieved and associated to a
> movie/person/whateverID internally used by the db...".
In my usual enlightened wisdom I had foreseen that IMDbPY users may want
to convert a movieID to the corresponding imdbID; while you already have
it for 'http'/'mobile', you need to be on-line and try an "Exact
Primary Title Search" (a somewhat hidden feature of the IMDb search
system) to convert a title to an imdbID.
With 'sql', once the conversion is done, the value is also stored
in the database, so that future queries will not need to ask the
IMDb server again. These imdbIDs are also saved, updating an
existing db.
In the code, you can convert a movieID/whateverID to an imdbID with:
from imdb import IMDb
i = IMDb('sql or local')
m = i.get_movie(thisIsAmovieID)
imdbID = i.get_imdbURL(m) # here the IMDb server is accessed.
If you're wondering: there's no way that I'll wrote a script to
fetch the imdbID for every movie/person/... from the IMDb site,
and I'll never support anyone who want to do this: it would be an
heavy violation of their policy.
So don't do it, and never ever use IMDbPY to misuse the IMDb site.
> I notice that some movie (titles) that have the "plot"/"plot outline"
> detail in web/mobile accessSystem do not appear to have any sql db.
> Could this be that it was updated recently and not available in
> plain text version? (I actually tried a few)
Here you faced another sad fact of live: the plain text data files
are far from completes. :-/
Only the files which descend from the original free database are
available (you won't find "dvd" or "faqs" information and many
others: they were added later).
Plot outline is one of the missing information, while as far as
I know "plot" should be complete - but I may be wrong.
> I have logic for getting the "cover url" and "headshot". It works
> fine in web/mobile accessSystem but nothing is returned when using
> local sql accessSystem.
Headshot and "cover url" are not available in the plain text data
files.
> So I am trying to see how I can fix those or at least provide
> alternative solutions for a production environment in mind.
It's never too late for a little disclaimer. :-)
Don't take it personally, the paragraph below is part of something I
say every time someone comes to me with a Great Idea(tm) about IMDbPY.
What kind of "production environment"?
Beware that the data you get from IMDb are _not_ free, except
for personal usage (in fact, if you want to use them for commercial
purposes, you have to pay tens of thousands of US dollars in licence fees).
You need to accept their conditions (for the web site):
http://www.imdb.com/help/show_article?conditions
Or, for the plain text data files:
http://www.imdb.com/interfaces.html
IMDbPY is free software (open source) and you can use it in any way
you like (respecting the terms of the GPL2 licence), but the data
you access with it is not free.
Use it for yourself as you like, but don't resell, redistribute
or create non-personal/commercial services with these data!
> >
> > http://sourceforge.net/mailarchive/forum.php?thread_name=464CD583.2090609%40buro302.nl&forum_name=imdbpy-devel
>
> I read this few days ago. Would be a great idea. Has there been
> enough interest shown in requesting this feature?
Besides admiration for such an high intellectual challenge? ;-)
Seriously: there is interest, but so far noone has offered
his body in sacrifice to The Mighty Python to help... ;-)
--
Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47]
http://erlug.linux.it/~da/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Imdbpy-devel mailing list
Imdbpy-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
