Now I have a hunch that the language qualifier has something to do
with it. Try to compare what it does when [en_US] is present and
when you discard it. (This has bitten me several times while editing
normal fields with BME.)
Regards,
~~helix84
Hello,
We are running DSpace version 1.7.1, PostgreSQL 8.2, Sun Solaris 10 Unix
and are having a problem with the metadata import feature - both online and the
metadata-import script. The problem is I can't figure out how to delete or
modify the existing dc.date.accessioned,
Hi Sue,
first, I admit I never tried to actually modify values of these fields
using batch metadata editor (BME). But I just checked
dc.date.accessioned, dc.date.available and dc.description.provenance
on an item which was created using BME and later a metadata value of
the same item was modified
: Re: [Dspace-tech] Problem with Import metadata option on Admin
screen in DSpace 1.7.1
Hi Sue,
first, I admit I never tried to actually modify values of these fields using
batch metadata editor (BME). But I just checked dc.date.accessioned,
dc.date.available and dc.description.provenance
On Wed, Jun 13, 2012 at 12:45 AM, helix84 heli...@centrum.sk wrote:
Now I have a hunch that the language qualifier has something to do
with it. Try to compare what it does when [en_US] is present and
when you discard it. (This has bitten me several times while editing
normal fields with BME.)
)[LITES]
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Problem with Import metadata option on Admin
screen in DSpace 1.7.1
On Wed, Jun 13, 2012 at 12:45 AM, helix84 heli...@centrum.sk wrote:
Now I have a hunch that the language qualifier has something to do
with it. Try
6 matches
Mail list logo
