I've often wondered why users are asked what new fields they would like added to MC, when we can add whatever custom fields we might need. It now dawns on me maybe we are being asked so that if the handing of any particular field needs to be optimized in any particular way, that can be "built-in" as well. For example, perhaps People and Keywords are optimized (e.g., they are handled in a relational fashion), but if we were to add custom fields for actors and tags (i.e., the exact same data types) their handling would not be optimized.
Is there any truth to this? If there is, is it likely to make much difference? It would be common for users to have 1,000's of movies, but not 100,000's.
If this does matter, we need to understand. PVD is built on a relational database, and allows users to add any type of custom field they want. Importing all of this into MC won't be a problem if it's just a matter of adding custom fields as needed. On the other hand, if "special" fields need to be used for certain data types, we need to understand that. And we may need to think harder about what additional fields we might need. For example, I can map my "tags" to Keywords, but what should I do with my "themes" and "tones"? Can I just add custom fields, or should I be asking for more fields like Keywords?