Hi David, what you're describing is a pretty common situation. You'll get the "xyz[]" column if you add a metadata value with an empty string for language (the "text_lang" column of the "metadatavalue" table). You're also completely correct about the way to resolve it using Batch Metadata Editing (BME).
I also encountered the "xyz" column, although I don't exactly remember how I got it. IIRC, you can see it when the "text_lang" column has a NULL in that row. It seems strange that you would get such column in BME if there were no values in it. I can think of these options: a) is that an export of your whole repository or only a part of it (e.g. collection)? If it's only a part, maybe the null is in an item that is not part of your current export. b) if BME doesn't detect any changes, do it in two turns: first, put a bogus value anywhere in that column and import it; second, re-export, remove the bogus value and import it. You can also take a look at the database to understand what's going on. Try these queries: SELECT text_lang FROM metadatavalue GROUP BY text_lang; SELECT count(*) FROM metadatavalue WHERE text_lang IS NULL; SELECT count(*) FROM metadatavalue WHERE text_lang = 'en_US'; SELECT count(*) FROM metadatavalue WHERE text_lang = ''; We'll be glad if you report back with your findings. Regards, ~~helix84 ------------------------------------------------------------------------------ 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
