I suggest allowing custom data for all fields, including those that are currently limited to a pre-defined list of options. Basically, it would work similarly to how genres work now, with custom data not being contributable and only pre-defined options being allowed in the online database.

This would make DVD Profiler much more flexible than it is now, and would also stop endless debates about whether particular countries should be added to the CoO list, or if a new rating should be added, or other such topics.

This wouldn't stop Ken from adding new countries/ratings/whatever, that would then be contributable, while at the same time allowing users the flexibility to enter data locally that we currently cannot, or that we currently have to use tags for.

What's wrong with the Tags?

Quoting Prof. Kingsfield:

Quote:
What's wrong with the Tags?

They're a great tool for sure, but they can be a bit cumbersome.

If I could enter my own countries in the CoO field (for example) both reporting, filtering and statistics would be improved with more accurate data. As it is, getting accurate info involves multi-step processes, and I'm not even sure certain reports or stats can even be created when using a combination of the built-in lists and tags.

Color me undecided, at the moment, Astra. I sense a bear trap, but I don't see it yet.

Quoting Astrakan:

Quote:
I'm curious to hear some reasoning from those who say they wouldn't like it. Since it's not contributable I'm not sure what's not to like. It wouldn't corrupt the online data, and you wouldn't HAVE to use it, so...

Not trying to call anyone out or anything, just genuinely curious why anyone would have a problem with this.

More difficult to support from a programming perspective, and less efficient, especially when it comes to database operations. Ok, ok put down the rotten eggs and tomatoes ... you did ask ... 

i'll vote no for this... if everyone does their own custom thing that is not contributable you run the risk of more people customizing rather then using the standard which would cause the demise of the online database, and therefore poor experience for new users, and therefore the demise of invelos.

Quoting ruineddaydreams:

Quote:
i'll vote no for this... if everyone does their own custom thing that is not contributable you run the risk of more people customizing rather then using the standard which would cause the demise of the online database, and therefore poor experience for new users, and therefore the demise of invelos.

While I don't think there's any danger in this happening, it's an understandable concern.

The majority of the time the pre-existing information is fine and people would simply use that. Most of the time, where this feature would be used is when the pre-existing info simply can't do what we need it to. Such as tracking movies made in Nigeria.

It's my opinion that while there may be some reduction in contribution of one or two fields, the overall improvement to the flexibility of the program is worth it.