When creating item metadata via our input forms, we find that dspace is appending a language code to some (but not all) of the fields. This causes us difficulty when exporting the metadata for re-use elsewhere, because the resulting csv file has duplicate columns. For example, we get dc.title and dc.title[en] columns, with some items with their title data in one column and other items with their title data in the other column.
There's no provision in the metadata registry to specify language codes for each field, but when we edit the metadata of an item via the UI we can see the language codes that have been assigned by dspace to the item. Some of the affected fields are ones that we've added to the dc schema (e.g. dc.citation.volume) but others are standard fields that came with dspace (e.g. dc.title, dc.subject). We've commented out the default_language and default_locale parameters in dspace.cfg, which got rid of the en_US codes (which was the setting for default_language) but not the en codes (which was the setting for default_locale). We can't find any other reference in the dspace manual about how to control these language codes, so any suggestions would be welcome. Linda McDonald University of Dundee Library & Learning Centre ************************************************************ Please consider the environment. Do you really need to print this email? The University of Dundee is a registered Scottish charity, No: SC015096 ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
