Hey Guys,
Andrea was on the money with the header being out of whack. It seems to be
matching thing much better so far. I'll continue testing.
Thanks for the help again.
Cheers
George
From: Benjamin Ryan [mailto:[email protected]]
Sent: Friday, 7 December 2012 3:36 PM
To: Andrea Schweer; George Rokkas
Cc: [email protected]
Subject: RE: [Dspace-tech] Dspace 1.8 Batch Edit
I think this is a bug in the import code as the same problem was discovered by
CottageLabs when they were doing some work on metadata quality for us.
I will look up the details and post to the list.
Regards,
Ben
------------------------------------------------------------------
Dr Ben Ryan
Jorum Technical Manager
5.12 Roscoe Building
The University of Manchester
Oxford Road
Manchester
M13 9PL
Tel: 0160 275 6039
E-mail:
[email protected]<https://outlook.manchester.ac.uk/owa/redir.aspx?C=b28b5bdd1a91425abf8e32748c93f487&URL=mailto%3abenjamin.ryan%40manchester.ac.uk>
------------------------------------------------------------------
From: Andrea Schweer [mailto:[email protected]]
Sent: 07 December 2012 03:44
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [Dspace-tech] Dspace 1.8 Batch Edit
Hi George,
On 07/12/12 16:17, George Rokkas wrote:
I want to perform a batch edit on a whole bunch of records, but when I do so
using the /bin/dspace metadata-import -f test_update.csv command I get all the
fields I'm updating as duplicate fields.
Is there a way to overwrite and not create?
It should overwrite rather than create by default. I suspect something isn't
quite right with the headers in your CSV file. My first thought would be the
language part of the headers -- DSpace takes that into account when checking
whether the field exists or not. That is, dc.type[en] is different from
dc.type[en_AU] etc.
How did you create the CSV file -- via metadata export? Try comparing the first
few lines of the original CSV file with the first few lines in your edited
version, using a standard text editor. The program you used to make your
changes may have done something to the CSV that DSpace doesn't like (especially
if you used Excel).
If you can't spot anything obvious yourself, maybe you could create a "minimal
example" with just one or two items and one or two metatada fields -- something
you could then send to this list so we can have a look.
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
UTS CRICOS Provider Code: 00099F
DISCLAIMER: This email message and any accompanying attachments may contain
confidential information.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or
attachments. If you have received this message in error, please notify the
sender immediately and delete
this message. Any views expressed in this message are those of the individual
sender, except where the
sender expressly, and with authority, states them to be the views of the
University of Technology Sydney.
Before opening any attachments, please check them for viruses and defects.
Think. Green. Do.
Please consider the environment before printing this email.
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
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
