I am currently developing a program that can fetch data from OMDb (Online Movie Database) and display it when you select a profile in DVD Profiler. Here is what it looks like at the moment (partial screenshot of DVD Profiler):


The reason that I'm getting data from OMDb and not IMDb is that OMDb has an open API, whereas IMDb does not. So there is no need to fiddle about with screen scraping.

The program is designed to show above DVD Profiler, so I wanted to keep it as small as possible. But I am also considering making it possible for the user to configure which data should be presented. The data returned from OMDb includes:
Production year, rating, US release date, runtime, genres, director(s), writer(s), main actors, plot, language, country, awards, Metacritic rating, IMDb rating, # of IMDb votes, IMDb id, type (movie/TV show), DVD release date, box office $, studios.

I would like to know which of these fields you think might be useful to you.

Production year, rating, US release date, runtime, genres, director(s), writer(s), main actors, plot, language, country, IMDb id, type (movie/TV show), DVD release date, studios.

OK, that was more than I expected. If you'd configure everything, that window would cover most of DVD Profiler (unless you have two monitors). My main idea was to provide data that Profiler doesn't already have. But then again, I often find that people use my tools in ways that I hadn't predicted. I guess I have some work ahead of me … 

Quoting mediadogg:

Quote:
Wow, seems cool. Would it be legal for me to use that API inside DVDPca to auto generate a profile (its original purpose)?

I think so. You can check it out at omdbapi.com. You can even test it online.