qjhart
commented
9 years ago For this application, I don't think we should allow alternative names. We should scrub those up when they go into the database, and then that shorter list should be all that's available to the users and administrators for new data, and updates. Any administrative interface should not allow alternatives.
The other badness is another common issue we run into, controlled vocabularies. After completing my first pass of Santiago's budgets, I have a general list of categories and items for those categories. But even then, he as 'alternative names' for many items. I have created a simple schema that supports alt names, but I don't think that is optimal, more a quick patch to work around the problem. Currently, to add a item cost or item amount at a locality, the item must exist in the schema.