Well DUH! Guess what, that worked. I don't think the old documentation really explained it this granularly.
I can easily fix the documentation part to give examples in the future. Thanks for the tidbit. Who knew! --Jeff Jeffrey Trimble Associate Director & Head of Information Services William F. Maag Library Youngstown State University 330.941.2483 (Office) [email protected] http://www.maag.ysu.edu http://digital.maag.ysu.edu “The spice must flow...." ________________________________ From: [email protected] <[email protected]> on behalf of Joshua Westgard <[email protected]> Sent: Tuesday, May 10, 2016 9:05 PM To: DSpace Technical Support Cc: [email protected] Subject: Re: [dspace-tech] Re: Batch import fails I've never used the batch metadata editor, but is it correct to have a space between the field name and the language specification? The first thing I would do is to test without the spaces (e.g. "dc.relation.ispartofseries[en_US]"). Josh Westgard University of Maryland College Park On Monday, May 9, 2016 at 1:12:53 PM UTC-4, jatrimble wrote: Allen, Thanks. Well, it’s very strange. I used Open Office because I’ve never really had success with Excel. My csv file looks correct. (I just recompiled my DSpace install just to make sure something didn’t get corrupted) So, several factors: We still running 1.6.2 and we plan to upgrade within the next several month to 5.x (using the new database migration pathway). The schema is the default with DSpace. So I haven’t changed anything there. It’s correct in the postgresql data (I used pgadmin to double check). If you switch the columns around or delete the data in on column, say the dc.relation.ispartofseries… then the next column receives a similar error that it cannot be found. Here’s a sample from my first four lines in my csv file: id$collection$dc.relation.ispartofseries [en_US]$dc.identifier.oclc [en_US]$dc.identifier.other [en_US] 10644$1989/78$Master's Theses no. 1202$682708903$b20701858 11779$1989/78$Master's Theses no. 1552$945634232$b22071659 11784$1989/78$Master's Theses no. 1481$906935863$b21525183 I can’t find anything wrong with it. Here’s the complete output from the run. As you can see the first part makes you think it’s going to work and then it can’t find anything. ==================== dspace:/irmaag/dspace/bin>dspace metadata-import -f /irmaag/batch_edit/1989_78_up_tst.csv ----------------------------------------------------------- Changes for item: 10644 (1989/10670) + Add (dc.relation.ispartofseries [en_US]): Master's Theses no. 1202 + Add (dc.identifier.oclc [en_US]): 682708903 + Add (dc.identifier.other [en_US]): b20701858 ----------------------------------------------------------- Changes for item: 11779 (1989/11773) + Add (dc.relation.ispartofseries [en_US]): Master's Theses no. 1552 + Add (dc.identifier.oclc [en_US]): 945634232 + Add (dc.identifier.other [en_US]): b22071659 ----------------------------------------------------------- Changes for item: 11784 (1989/11776) + Add (dc.relation.ispartofseries [en_US]): Master's Theses no. 1481 + Add (dc.identifier.oclc [en_US]): 906935863 + Add (dc.identifier.other [en_US]): b21525183 3 item(s) will be changed Do you want to make these changes? [y/n] y java.sql.SQLException: bad_dublin_core schema=dc, relation ispartofseries at org.dspace.content.Item.update(Item.java:1640) at org.dspace.app.bulkedit.MetadataImport.compare(MetadataImport.java:465) at org.dspace.app.bulkedit.MetadataImport.runImport(MetadataImport.java:154) at org.dspace.app.bulkedit.MetadataImport.main(MetadataImport.java:1102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:212) ============================ Jeffrey Trimble, MLS William F. Maag Library Youngstown State University 330.941.2483 (Office) [email protected] http://www.maag.ysu.edu http://digital.maag.ysu.edu From: <[email protected]> on behalf of Allen Clayton <[email protected]> Date: Monday, May 9, 2016 at 11:35 AM To: DSpace Technical Support <[email protected]> Subject: [dspace-tech] Re: Batch import fails Hi Jeffrey, If you copied and pasted the error message, then it looks like the schema is incorrect. Look at the top line in your spreadsheet and at the column in question. It should say dc.relation.ispartofseries all parts separated by periods. What you pasted from the error message is dc, relation ispartofseries. If so fix your header in the spreadsheet and try again. You didn't mention it, but I also had problems if I used Excel 2013 to create a csv file. What worked for me was to save the file as a csv in Libre Calc. Hope this helps Allen Clayton Digital Collections Librarian The University of Texas at Dallas 972-883-2949 [email protected] On Saturday, May 7, 2016 at 5:04:03 PM UTC-5, jatrimble wrote: I’ve got a unique issue I’ve never seen before. I’m updating a set of records with the batch import feature. When it runs, it looks like it’s going to be fine, but then when you agree to make the changes, you get the following error: ----------------------------------------------------------- Changes for item: 11784 (1989/11776) + Add (dc.relation.ispartofseries [en_US]): Master's Theses no. 1481 + Add (dc.identifier.oclc [en_US]): 906935863 + Add (dc.identifier.other [en_US]): b21525183 385 item(s) will be changed Do you want to make these changes? [y/n] y java.sql.SQLException: bad_dublin_core schema=dc, relation ispartofseries Now, this is a default field in the DCmetadata, so I don’t understand why I’m getting this. Any one have some clues? Thanks in advance, Jeffrey Trimble, MLS William F. Maag Library Youngstown State University 330.941.2483 (Office) [email protected] http://www.maag.ysu.edu http://digital.maag.ysu.edu -- 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. -- 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]. 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.
