I am hoping that someone might be able to help me with this problem.
For input fields where it is not possible (or practical) to implement
controlled vocabularies or drop down lists, is there a less labour-intensive
way of preventing data entry errors? For example: The author of several
documents is "ABC Statistics Inc.", but each document is added by a different
ePerson,and each of these people makes a spelling error when filling out the
AUTHOR field, so these items appear to have different authors. ("ABC
Statisitcs, Inc.", "ABC Statistics, Inc", "ABC Statistics", etc.).
Originally I thought that this would be a minor issue, easily correctable
through raw SQL queries to update the offending fields. Unfortunately, my
estimates as to the number of mistakes that would be made has proven to be
extremely conservative. I do not want to be responsible for correcting so many
entries myself, nor do I want to reject so many entries asking users to match
the existing AUTHOR name that already exists.
I know that I could code a solution if that is absolutely necessary, but I
wonder if someone else in the community hasn't already addressed this issue.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
