To expand a little on helix84's answer:
Those duplicate columns in CSVs are not something to worry about, but
you can clean it up in the CSV itself in order to correct it. But first,
let me explain why this occurs...
In DSpace, all metadata values have a "Language" column associated with
them. Often times, this "Language" value is either defaults to not being
set, or to your specified default (e.g. "en_US" , US English). However,
in some scenarios (usually either a bulk data load or migration), the
"Language" value might be accidentally set to an empty value (e.g. a
single space or empty string). That's what causes the seemingly
duplicate field names. Here's an example:
1. dc.title = a Title with no specified Language value
2. dc.title[] = a Title that has an empty string / single space as the
specified Language value (Normally, this shouldn't occur in normal
interactions with DSpace, but sometimes these odd empty values get in
via data migration or bulk load. They don't harm anything, but they do
look odd in CSV exports.)
3. dc.title[en_US] = a Title where the Language is specified as "en_US"
(USA English)
In DSpace itself, all three of these Titles would be treated similarly
in the User Interface (and the first two are seen as "identical"). So,
this difference in Language settings only appears in the database or in
CSV exports. If it's bothersome, you can correct it by simply moving all
the values in a column like "dc.title[]" into the column named
"dc.title" (or "dc.title[en_US]", depending on the Language you want
set). Then, when you upload the updated CSV, DSpace will detect that
change and modify the Language as you requested.
- Tim
On 4/15/2016 4:20 PM, helix84 wrote:
dc.identifier.uri[] has empty string as the language,
dc.identifier.uri has null as the language. You can move the values
from one column to the other and re-import. Alternatively, you can fix
it in the DB.
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
On Fri, Apr 15, 2016 at 11:03 PM, Stuart A. Yeates <[email protected]
<mailto:[email protected]>> wrote:
There is a bug where dspace sees significance in white space in
language fields.
The trick is to find the white space and remove it.
Cheers
Stuart
On Saturday, 16 April 2016, Chris Gray <[email protected]
<mailto:[email protected]>> wrote:
When exporting metadata for items I get duplication of
columns. For instance, the CSV will have a column for
dc.identifier.uri and a column for dc.identifier.uri[]. This
happens with other columns too.
I know you get this when you have different languages
associated with values in the same field, but in this case
there is no language associated with the fields. They look
identical in the UI, but get separated into two columns in the
metadata output.
Does anyone know what would do this? I assume we've
misconfigured something. Is it bad not to associate any
language with some fields?
--
You received this message because you are subscribed to the
Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
--
...let us be heard from red core to black sky
--
You received this message because you are subscribed to the Google
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
--
You received this message because you are subscribed to the Google Groups "DSpace
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
