User and Metadata input
Previous: BBC Guides to HD Encoding | All | Next: HTML5, H.264, VP8 and all that
I saw this post on a forum regarding designing forms for users and thought it was very relevant to the way we design forms for metadata input in out asset management systems. A good reminder to engage the users when designing systems and to come up with schemas that work for everyone! Bad meta data is often worse than no metadata.
Marc Risby
marc.risby@boxer.co.uk
----------------------------------------
Re:In Defense of Artificial Intelligence
by daveime - I'm still getting therapy.
We had a simple field on a form to "Supply a Telephone Number". The users didn't, so we used JS to validate they had filled it in.
Then they filled in garbage, so we enforced numerals only. The users entered "1111111" everywhere.
Then we enforced standard number formats based on a Country selector, with correct International Dialling Codes and pattern / format matching. The users entered "0044 (1)1111111" everywhere.
Finally we checked that the numbers didn't look like "0044 (1)1111111" i.e. too many repeated characters, after extensive testing to avoid false-positives. The users now enter "0044 (1)2121212" everywhere.
The more you Idiot-Proof a system, the smarter the Idiots become. Not smarter at actually entering the correct data, just smarter at bypassing the protections you put in place.
----------------------------------------
Asset management, meta data, users, dam, final cut server