Description to the film library (theory, perhaps someone will be interested and implementation)

Today I thought about how good it is to have a certain number of films you love, but unfortunately the film library is constantly growing, the memory is clogged, i.e. far from all the films I can remember by name (what about what in the sense). And if this is some kind of public repository? A person climbs a movie, I really want to see something, he sees the names and starts using Google to find the info on the movie (well, or more or less competent climb on imdb and look at the description and most importantly - the rating is already there). Agree - not too convenient !? What does most do? They write saytik on php, create a database with movies, descriptive, kammentami, posters, etc. Agree - to fill this matter is also quite hemorrhoid?

So the very thought:
- read the names of files / folders in the directory
- (here it depends on how the storage of files is arranged), if the name is in English - go to the next item, if in Russian - we push the name of the movie into the Google dictionary with the script, we get what we need
- we climb with the name of the movie on imdb, we put the name of the movie in the search, we find a page with a description and parsim it

well, then there may be a different implementation - either pushing all this information into the database one time or into a text file with the movie name and putting it next to the file, or simply parsing the page with each request, do not load the server with unnecessary junk, well, time to generate a page with a description of course It will take a little more (here's another question - how long will it take to parse a similar page with a description? But in any case it will be faster than copying the name to Google and finding the description manually), but I think this is a more convenient solution.
')
what (in my opinion) is worth focusing on?
- work on all platforms - Windows / * nix
- support for all types of files (avi, mkv, ts, etc. while not forgetting about the folder with DVDs and do not forget about the fact that the film can be cut into pieces)

maybe someone will complement the idea or vice versa - they will explain to me that the idea is bad

Well, I would also like to turn to fellow programmers:
1. What is a better idea to implement?
2. Maybe someone will find the idea interesting and take up implementation? (I, unfortunately, have not yet grown to write such things, maybe in theory I understand how this can be implemented, but in practice I will not master it)