How to match files based on my own database?
Posted: 09 Feb 2016, 10:05
Lately, I've been frustrated that thetvdb and omdb are unable to match most UFC events. I was so frustrated I decided to learn python and solve this myself! I just finished writing the script.
The script creates a spreadsheet that with five columns that store the event number, event title, alternative title, date and venue.
I also wrote a script that stores the weight class and names of the athletes in each fight (for each event) in the summary field of an .nfo file.
Right now, I'm still working on downloading the event posters and writing the .nfo files for importing into pleX and KODI.
Is there a way to point filebot to my database for renaming?
If so, what file format is best (.csv, .txt, .xls, .xlsx...?) and what should the structure look like?
If not, where can I find documentation on how filebot code works?
If I there isn't, are there any other resources that you might know of that would help me with this project? (matching filenames to a database/list, renaming and moving?)
Thanks so much for taking the time to help. I'll keep updating the post as more info come in and will probably post the code on GitHub or somewhere.
The script creates a spreadsheet that with five columns that store the event number, event title, alternative title, date and venue.
I also wrote a script that stores the weight class and names of the athletes in each fight (for each event) in the summary field of an .nfo file.
Right now, I'm still working on downloading the event posters and writing the .nfo files for importing into pleX and KODI.
Is there a way to point filebot to my database for renaming?
If so, what file format is best (.csv, .txt, .xls, .xlsx...?) and what should the structure look like?
If not, where can I find documentation on how filebot code works?
If I there isn't, are there any other resources that you might know of that would help me with this project? (matching filenames to a database/list, renaming and moving?)
Thanks so much for taking the time to help. I'll keep updating the post as more info come in and will probably post the code on GitHub or somewhere.