Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suggestion : create engines for OMDB API , IMBD json api, TMDB api , rotten tomatoes api #19

Open
devloic opened this issue Jul 14, 2013 · 6 comments
Labels
enhancement Enhancements and improvements, nice to haves for a next release but never mandatory.
Milestone

Comments

@devloic
Copy link

devloic commented Jul 14, 2013

omdb api: http://www.omdbapi.com/
imdb json api : http://stackoverflow.com/questions/1966503/does-imdb-provide-an-api
themoviedb ap ( TMDb ) i: http://www.themoviedb.org/documentation/api
rotten tomatoes api : http://developer.rottentomatoes.com/

omdb api is available as a mysql database. We could include a remote install mechanism to download/install/activate the db locally in videodb.

@andig
Copy link
Owner

andig commented Jul 14, 2013

As far as I know IMDB doesn't have a reliable API- if the inofficial one from IMDB itself works that would be interesting though. Honestly: in the past, too little engines was never a problem. What was a problem was having non-maintained engines en masse that became unusable...

@devloic
Copy link
Author

devloic commented Jul 14, 2013

Yes, maintenance is certainly a big problem on the long term. I'd still like to see some kind of meta-engine which would aggregate data from various engines, especially in the perspective of a multilingual videodb .

@andig
Copy link
Owner

andig commented Jul 15, 2013

Multilingual videodb sounds a little like issue #2 which might generate more interest than new engines. Metaengine that doesn't force you to choose but takes the best data available is an interesting thought though...

@Lewiscowles1986
Copy link

If I might, I'd like to throw a suggestion into this.

Have a format that VideoDB supports for receiving information via REST; and document a trivial example of a cron based scraper (separate to the project or in an examples folder); That gets information from a source and updates a record in VideoDB.

This way encourages modularised VideoDB components, and keeps the main program lean; as I suspect many people don't want or care to scrape details from IMDB.

@andig
Copy link
Owner

andig commented Jun 7, 2016

Definitely good idea. i have a couple more (e.g. replace regexes with CSS selectors engine etc). Unfortunately I don't have time for maintaining videoDB anymore but I'm happy to review and merge any PRs.

@Lewiscowles1986
Copy link

Lewiscowles1986 commented Jun 7, 2016

I Know of a library we could use for CSS selectors phpquery
composer require coderockr/php-query
Code probably needs a refresh for PHP7, but I don't mind looking into both, just give me time 😉

@johanneskonst johanneskonst added this to the 4.3 milestone Dec 15, 2022
pbenke pushed a commit to pbenke/videodb that referenced this issue Nov 26, 2024
…reating_new_movies

Fixed getting runtime
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancements and improvements, nice to haves for a next release but never mandatory.
Projects
None yet
Development

No branches or pull requests

4 participants