Hey!  It worked!!  Now that I look, for some reason, my dc.date.accessioned, 
dc.date.available, and dc.date.issued do NOT have en_US showing on the long 
listing page next to them like most of the other fields do.

Thanks so much for your help!!!  That's a really easy fix for me to make in my 
Java program that creates the .csv file!
Best regards,
Sue


Sue Walker-Thornton
(w):  (757) 864-2368
(m):  (757) 506-9903


-----Original Message-----
From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84
Sent: Tuesday, June 12, 2012 6:48 PM
To: Thornton, Susan M. (LARC-B702)[LITES]
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Problem with "Import metadata" option on Admin 
screen in DSpace 1.7.1

On Wed, Jun 13, 2012 at 12:45 AM, helix84 <heli...@centrum.sk> wrote:
> Now I have a hunch that the language qualifier has something to do 
> with it. Try to compare what it does when "[en_US]" is present and 
> when you discard it. (This has bitten me several times while editing 
> normal fields with BME.)

You see, "dc.date.accessioned[en_US]" and "dc.date.accessioned" are actually 
two separate metadata fields for DSpace. That may have caused what you think is 
a duplicity But you should be able to distinguish them in the full item view by 
locale code.

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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to