Maybe a wish already posted, but IMHO is a must to enhance the database structure.
The fields Actors and Director have a great problem when you don't read the movie info ever from the same source. So, you could have same actor/director with different string (i.e.: Robert De Niro, R. De Niro, De Niro, De Niro Robert, De Niro R., etc.).
More obvious problem arises if you wrongly type the name.
The most evident impact is on searches and /or filters, mainly with synonimous or confusing names/surnames.
Supposing a structure with:
cast table with fields: movieID, people ID, character, awards, notes
direction table with fields: movieID, peopleID, awards, notes
people table with fields: peopleID, firstname, surname, truename, dateofbirth, stateofbirth, notes, etc.
we could have a lot of benefits:
1. same person will have only one record in people table
2. will be possible to search for a person despite of his rule of actor and/or of director (think to Mel Gibson, Charlie Chaplin, etc.)
3. also infos strictly related to the movie could be saved
4. the peopleID could be strongly related to IMDB id
It's a very heavy change in database structure, but could be a great step in amc enhancement.
What you think about?