[m.savazzi]

OK. We rename the table to "persons". I don't like it when the table name is different to primary key column (idPerson). It is easier to see that the field is not linked to another table.

You are fully right. Let me recheck the DB I've done, maybe I messed up.

the table should be named Persons
the PK is idPerson
then there are the personslinkmovie etc...

Do you have an idea to prevent actors with same name that are not the same person? Have TMDB/IMDB a "personally number", linked to a profile?

Yes, IMDB ID is unique and the same goes for TMDB

---

Also I'm not sure if a Set Fanart is needed or used by any skin

Set fanart and posters are used by EVERY skin if you have enabled "group movies to sets" in XBMC settings. But you can only set an individually images over the context menu.
But... There is a plugin for this problem. You need a folder "artwork" in the movie source folder. The poster must be named "<set-name>.jpg" and the fanart "<set-name>-fanart.jpg". Actually quite simple to implement in Ember.

I've also seen that XBMC wants to make a solution for it in next release (14). Thus, we are already one step ahead

Ok,
so the file table and the fileslinkset tables are perfect for this. the set name is in the set name and the files are in the table and the same table can manage poster and fanarts

Nice

---

I looked at the database structure and so far I think it's a good setup - one thing I missed is support for the new VideoTag Field (since v12 Frodo):

What is the VideoTag?

If you mean the keywords (on IMDB) I was already planning to add them.


The keywords table will be identical to genre and linked to movie, shows, episode, etc...