On Fri, May 24, 2013 at 12:21 PM, Evans, Kev <[email protected]> wrote: > Yes this is the kind of duplication, although only using one language [en]
These are inconsistencies in your user data - you should have your own policy whether you always use a language code for a certain field or not. The inconsistency between NULL and empty string is DSpace's fault because different processes (submission/edit/import methods) are not consistent in what they put in by default. Sorry about that, we should fix it, it's just low priority. Anyway, the Batch Metadata Editor makes it extremely easy to move data between these columns, and re-import them. Moving a data value from the dc.title[] column to dc.title and leaving the value under dc.title[] empty will do what you'd expect - create a new metadata value with NULL language and get rid of the metadata value with empty string as language. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
