[dspace-tech] Re: Importing CSV file with special characters into DSpace.

2020-02-24 Thread genevieve.tur...@anu.edu.au 
Hi Fahad,

Are you using the "Improt metadata" or "Batch import" method?  If using the 
Batch Import method I would suggest looking at your bte.xml and you will 
need to use the fields as defined, and in the order defined there (this is 
the one where you select the type input data).  With the Import metadata 
(where you just upload a csv) then I'm not sure what the the problem is.  
Personally for CSV imports I would recommend the Import metadata over Batch 
import.

Regards,

Genevieve

On Wednesday, February 12, 2020 at 12:59:10 AM UTC+11, Fahad Ubaid wrote:
>
> Asalam-o-Aliakum/ Greetings Ali,
>
> I am new user of dspace & facing problem in importing metadata from csv 
> file to the dspace. 
>
> whenever I import a data from csv  to the dspace, It change the filed 
> location for example value of author field goes into the date field, and so 
> on. For the reference picture is attached.
>
> can you help me in this regard,
>
> I am very thankful if you help me
>
>
>
> On Monday, March 28, 2016 at 8:40:20 PM UTC+5, Ali Mansoor wrote:
>>
>> Dear,
>>
>> Open the CSV file in the notepad & go to the save as option & below their 
>> is a encoding option then select the encoding to the UTF-8 & save.Upload 
>> again that csv file in the dspace & see the changes if not then check your 
>> tomcat server.xml file at the "connector" weather the Encoding has set to 
>> the UTF-8 or not, if not then set for UTF-8 & restart the tomcat.
>>
>>
>> On Thursday, March 10, 2016 at 8:18:05 PM UTC+3, Xiping Liu wrote:
>>>
>>> Hello everyone, 
>>>
>>> A few months ago we started a project of cleaning up our electronic 
>>> thesis and dissertation records from DSpace. We exported our data from 
>>> Dspace as a csv file and after the cleanup we are ready to import the data 
>>> back into Dspace. But we noticed that some of the names (accent marks and 
>>> quotes) in our data are not showing correctly (I am assuming the encoding 
>>> is not set correctly in the very beginning after we export). But since we 
>>> have already done our clean up in our file, it will be really painful to go 
>>> back and re export the file from Dspace (so we can set the encoding 
>>> correctly this time) and redo all the editing. I wonder is there any way we 
>>> can correct the encoding after we import the data back into Dspace? Or any 
>>> suggestions to solve this problem? I have attached a small sample of our 
>>> data. 
>>>
>>> Your help is greatly appreicated. 
>>>
>>> Xiping 
>>>
>>>
>>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/5cf2c6f8-fe4d-4448-b78e-b8c7ced473d9%40googlegroups.com.

Re: [dspace-tech] Re: Importing CSV file with special characters into DSpace.

2020-02-24 Thread Paul Münch 
Hello,

welcome in the DSpace community. Are you sure that you filled the
metadata fields with the correct values? DSpace doesn't prove which
value is in which field. On the screenshot it looks like they get out of
their places. Maybe it is a misplaced comma only.

Kind regards,

Paul Münch

Am 11.02.20 um 10:54 schrieb Fahad Ubaid:
> Asalam-o-Aliakum/ Greetings Ali,
>
> I am new user of dspace & facing problem in importing metadata from
> csv file to the dspace. 
>
> whenever I import a data from csv  to the dspace, It change the filed
> location for example value of author field goes into the date field,
> and so on. For the reference picture is attached.
>
> can you help me in this regard,
>
> I am very thankful if you help me
>
>
>
> On Monday, March 28, 2016 at 8:40:20 PM UTC+5, Ali Mansoor wrote:
>
> Dear,
>
> Open the CSV file in the notepad & go to the save as option &
> below their is a encoding option then select the encoding to the
> UTF-8 & save.Upload again that csv file in the dspace & see the
> changes if not then check your tomcat server.xml file at the
> "connector" weather the Encoding has set to the UTF-8 or not, if
> not then set for UTF-8 & restart the tomcat.
>
>
> On Thursday, March 10, 2016 at 8:18:05 PM UTC+3, Xiping Liu wrote:
>
> Hello everyone, 
>
> A few months ago we started a project of cleaning up our
> electronic thesis and dissertation records from DSpace. We
> exported our data from Dspace as a csv file and after the
> cleanup we are ready to import the data back into Dspace. But
> we noticed that some of the names (accent marks and quotes) in
> our data are not showing correctly (I am assuming the encoding
> is not set correctly in the very beginning after we export).
> But since we have already done our clean up in our file, it
> will be really painful to go back and re export the file from
> Dspace (so we can set the encoding correctly this time) and
> redo all the editing. I wonder is there any way we can correct
> the encoding after we import the data back into Dspace? Or any
> suggestions to solve this problem? I have attached a small
> sample of our data. 
>
> Your help is greatly appreicated. 
>
> Xiping 
>
>
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code
> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 dspace-tech+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/0111cc0c-c066-4f83-8e0e-975788fbbe79%40googlegroups.com
> .

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/8f2c0a1a-3e48-b202-675a-f880b3041681%40staff.uni-marburg.de.

[dspace-tech] Re: Importing CSV file with special characters into DSpace.

2020-02-11 Thread Fahad Ubaid 
Asalam-o-Aliakum/ Greetings Ali,

I am new user of dspace & facing problem in importing metadata from csv 
file to the dspace. 

whenever I import a data from csv  to the dspace, It change the filed 
location for example value of author field goes into the date field, and so 
on. For the reference picture is attached.

can you help me in this regard,

I am very thankful if you help me



On Monday, March 28, 2016 at 8:40:20 PM UTC+5, Ali Mansoor wrote:
>
> Dear,
>
> Open the CSV file in the notepad & go to the save as option & below their 
> is a encoding option then select the encoding to the UTF-8 & save.Upload 
> again that csv file in the dspace & see the changes if not then check your 
> tomcat server.xml file at the "connector" weather the Encoding has set to 
> the UTF-8 or not, if not then set for UTF-8 & restart the tomcat.
>
>
> On Thursday, March 10, 2016 at 8:18:05 PM UTC+3, Xiping Liu wrote:
>>
>> Hello everyone, 
>>
>> A few months ago we started a project of cleaning up our electronic 
>> thesis and dissertation records from DSpace. We exported our data from 
>> Dspace as a csv file and after the cleanup we are ready to import the data 
>> back into Dspace. But we noticed that some of the names (accent marks and 
>> quotes) in our data are not showing correctly (I am assuming the encoding 
>> is not set correctly in the very beginning after we export). But since we 
>> have already done our clean up in our file, it will be really painful to go 
>> back and re export the file from Dspace (so we can set the encoding 
>> correctly this time) and redo all the editing. I wonder is there any way we 
>> can correct the encoding after we import the data back into Dspace? Or any 
>> suggestions to solve this problem? I have attached a small sample of our 
>> data. 
>>
>> Your help is greatly appreicated. 
>>
>> Xiping 
>>
>>
>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/0111cc0c-c066-4f83-8e0e-975788fbbe79%40googlegroups.com.
id,collection,dc.contributor.author,dc.date.accessioned,dc.date.available,dc.description.abstract[en_US],dc.description.provenance[en],dc.identifier.date[en_US],dc.identifier.doi[en_US],dc.identifier.frompage[en_US],dc.identifier.issn,dc.identifier.issue[en_US],dc.identifier.jabbrv[en_US],dc.identifier.jname[en_US],dc.identifier.topage[en_US],dc.identifier.uri,dc.identifier.volume[en_US],dc.publisher[en_US],dc.subject[en_US],dc.title.alternative[en_US],dc.title[en_US]
"2321","123456789/2","ali khan, author 1","2020-02-10T16:25:00Z","2020-02-10T16:25:00Z","abstract","Submitted by fahad ubaid (fahadubai...@gmail.com) on 2020-02-10T16:25:00Z
No. of bitstreams: 1
dummy.pdf: 13264 bytes, checksum: 2942bfabb3d05332b66eb128e0842cff (MD5)||Made available in DSpace on 2020-02-10T16:25:00Z (GMT). No. of bitstreams: 1
dummy.pdf: 13264 bytes, checksum: 2942bfabb3d05332b66eb128e0842cff (MD5)","2019","3232/234/24","1","2323-2332","2","abreviated","journal name","3","http://localhost:8080/xmlui/handle/123456789/26","8","UET taxila","IT||TCP/IP","other title","title 1"

[dspace-tech] Re: Importing CSV file with special characters into DSpace.

2016-03-15 Thread Xiping Liu 
Hi euler,

Thanks for your suggestion. I tried uploading our cleaned csv into google 
spreadsheet and as you said most of the accent marks are retained. The 
problem is depending where � is, it represents different special 
characters, in name field it can be Š or Å. In abstract field, it 
represents ". So we can't do a one stop find and replace. 

We ended up identifying all the names with special characters in our 
cleaned up file (out of 941 records we found 36 records with names of 
special characters so not too bad) and have the same list of names with 
correct encoding in a second column and do a find and replace. 

We were suggested by a colleague on using open office to open up the csv 
file right after export from Dspace to set the encoding right (for future 
reference). It's good to know that Googe spreadsheet has the same function. 

Thanks again for your help. 
Xiping 

On Thursday, March 10, 2016 at 9:18:07 PM UTC-6, euler wrote:
>
> Hi Xiping,
>
> My suggestion is to import or upload your (cleaned-up) csv file into 
> Google spreadsheets. I tested your sample data and accent marks are 
> retained (not 100% though). See my attached screenshot. All you have to do 
> now is to find and replace all the � characters. After cleaning it up, 
> download as CSV and then import it back to DSpace. Take note that once you 
> already downloaded it as CSV, refrain from editing it in MS Excel because 
> in my experience, it will mess up your encoding again. It may seem a 
> tedious task but I would rather do it this way than start all over again.
>
> Hope this helps.
>
> Good luck and best regards,
> euler
>
> On Friday, March 11, 2016 at 1:18:05 AM UTC+8, Xiping Liu wrote:
>>
>> Hello everyone, 
>>
>> A few months ago we started a project of cleaning up our electronic 
>> thesis and dissertation records from DSpace. We exported our data from 
>> Dspace as a csv file and after the cleanup we are ready to import the data 
>> back into Dspace. But we noticed that some of the names (accent marks and 
>> quotes) in our data are not showing correctly (I am assuming the encoding 
>> is not set correctly in the very beginning after we export). But since we 
>> have already done our clean up in our file, it will be really painful to go 
>> back and re export the file from Dspace (so we can set the encoding 
>> correctly this time) and redo all the editing. I wonder is there any way we 
>> can correct the encoding after we import the data back into Dspace? Or any 
>> suggestions to solve this problem? I have attached a small sample of our 
>> data. 
>>
>> Your help is greatly appreicated. 
>>
>> Xiping 
>>
>>
>>

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Importing CSV file with special characters into DSpace.

2016-03-10 Thread euler 
Hi Xiping,

My suggestion is to import or upload your (cleaned-up) csv file into Google 
spreadsheets. I tested your sample data and accent marks are retained (not 
100% though). See my attached screenshot. All you have to do now is to find 
and replace all the � characters. After cleaning it up, download as CSV and 
then import it back to DSpace. Take note that once you already downloaded 
it as CSV, refrain from editing it in MS Excel because in my experience, it 
will mess up your encoding again. It may seem a tedious task but I would 
rather do it this way than start all over again.

Hope this helps.

Good luck and best regards,
euler

On Friday, March 11, 2016 at 1:18:05 AM UTC+8, Xiping Liu wrote:
>
> Hello everyone, 
>
> A few months ago we started a project of cleaning up our electronic thesis 
> and dissertation records from DSpace. We exported our data from Dspace as a 
> csv file and after the cleanup we are ready to import the data back into 
> Dspace. But we noticed that some of the names (accent marks and quotes) in 
> our data are not showing correctly (I am assuming the encoding is not set 
> correctly in the very beginning after we export). But since we have already 
> done our clean up in our file, it will be really painful to go back and re 
> export the file from Dspace (so we can set the encoding correctly this 
> time) and redo all the editing. I wonder is there any way we can correct 
> the encoding after we import the data back into Dspace? Or any suggestions 
> to solve this problem? I have attached a small sample of our data. 
>
> Your help is greatly appreicated. 
>
> Xiping 
>
>
>

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.