Timo,
To answer the question on how to delete the field you don't want. Your best
bet is to use batch metadata editing. When you import a column
(dc.language.iso), with no value, then it treats that as delete that value
from the metadata record.
Export the metadata of the affected collection, and open it in open office.
Remove the columns from the spreadsheet that aren't needed to be touched
(dc.title, dc.contributor.author), you have to keep item id, and collection,
thus leaving dc.language.iso. All the field values for language will be
"fi", so you can then highlight and delete all of the "fi", and when you
import the metadata it should delete them. It will give you a confirmation
in the UI of what it will do so you get a second chance to say "Yes".
--
Peter Dietz
Systems Developer/Engineer
Ohio State University Libraries
On Fri, Feb 4, 2011 at 1:56 PM, Stuart Lewis <[email protected]> wrote:
> Hi Timo,
>
> > I did some metadata gardening using the CSV bulk editor and as I uploaded
> my changes I noticed that the bulk metadata importer added an empty
> dc.description.abstract (with a 'fi' language identifier that is the default
> for our installation nowadays) into just about every record I had in that
> csv. (see: https://helda.helsinki.fi/handle/10138/24620?show=full for
> example). Mea culpa in that regard that I should have noticed this before
> pressing the yes key, but I still think there should be a some kind of a
> sanity check on the importer about not creating empty metadata value fields.
>
> There is a sanity check for this, so I'm not sure how it could have
> happened:
>
> -
> http://scm.dspace.org/trac/dspace/browser/dspace/trunk/dspace-api/src/main/java/org/dspace/app/bulkedit/DSpaceCSV.java#L481
>
> Is the field definitely empty - could it have contained something like a
> single space?
>
> It looks like Item.java, when ingesting metadata, performs a trim() on the
> values, to remove any leading or trailing spaces:
>
> -
> http://scm.dspace.org/trac/dspace/browser/dspace/trunk/dspace-api/src/main/java/org/dspace/content/Item.java#L684
>
> The CSV importer does not perform a trim(). I'll need to test this to see
> if it could be a problem, and if it does cause the problem you're seeing,
> then we'll need to make sure the CSV importer performs a trim too, so that
> it doesn't pass on a single space (or multiple spaces) to Item.java, which
> then trims them and archives them.
>
> Thanks,
>
>
> Stuart Lewis
> Digital Development Manager
> Te Tumu Herenga The University of Auckland Library
> Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand
> Ph: +64 (0)9 373 7599 x81928
>
>
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
