Hi Sue,

This is the only way I've found to get many of my imports to work, and they 
seem to work without a problem.  When they get entered into the db, they're 
UTF-8, as far as I can tell.  Values show up correctly in the interface, and 
are searchable.

B--

From: Thornton, Susan M. (LARC-B702)[LITES] [mailto:[email protected]]
Sent: Thursday, February 07, 2013 1:40 PM
To: [email protected]
Cc: Dedmond, Nicole K. (LARC-B702)[LITES]
Subject: [Dspace-tech] ItemImport.java failing due to extended ASCII characters 
from an external repository

Hi,
     I am in the process of importing content from an external repository, 
using ItemImport.java, and it keeps failing because there is a LOT of metadata 
that has extended ASCII characters like Comisiâon and Genáese.  What is the 
best way around this?  If I change my xml header in the Dublin_core.xml file 
from "encoding="utf-8"" to "encoding="ISO-8859-1"", it can successfully parse 
and import the record, but I thought we were only supposed to use UTF8 in 
DSpace.  Is there any harm in regenerating all my import files and using 
ISO-8859-1 instead of UTF8?
Thanks in advance,
Sue


Sue Walker-Thornton
Software Developer/Database Administrator
NASA Langley Research Center - LITES Contract
[email protected]<mailto:[email protected]>
(W) 757-864-2368
(M)  757-506-9903

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
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

Reply via email to