Mapping DCMI metadata to EAs

System

Hey folks -

This might actually belong in the metatagger forum, but I'm going to try here first in case someone else has already thought through this. The Dublin Core metadata specifications have a core principle that there is a one to one mapping between metadata elements and values. However, multiple iterations of an individual element are allowed, so, if you had an asset that had keywords of "cat", "****", "kitty kitty", and "feline", you would end up with four iterations of the element:

dc:subject=cat
dc:subject=****
dc:subject=kitty kitty
dc:subject=feline

Because EAs are implemented as simple key value pairs, you can't model that in TeamSite. The lack of flexibility on the metadata capture CGI also makes this a pain in the rump. My solution thus far has been to break the rule and do a delimited list of values for an element, but I was curious if anyone had a better solution. If I ever have to do an import or export of metadata to another system, or build a crosswalk into a master metadata repository that uses a different classification system, I expect it would be a pain.

Thoughts?