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 > <mailto: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 > <https://groups.google.com/d/msgid/dspace-tech/0111cc0c-c066-4f83-8e0e-975788fbbe79%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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.
