It was a bug in the DSpace-CRIS 5.x, now it is fixed and you can use the
official dublin_core.xml file
https://github.com/4Science/DSpace/commit/9e925eeed17155160c031f3775d5fec6436d79bf
Cheers,
Andrea
Il 01/12/2017 09:49, Marianna Mühlhölzer ha scritto:
Thanks for the replies. The problem is s
Thanks for the replies. The problem is solved now. It occurs only with
DSpace CRIS. Here the dublin_core.xml should have Metadata-tags instead of
dcvalue. If I change the dublin_core file, it works.
Am Dienstag, 21. November 2017 19:25:18 UTC+1 schrieb Terry Brady:
>
> I know that I have seen th
I know that I have seen this error before, but I am having trouble
recreating this error message in my repository.
Here is a minimal dublin_core.xml file that I am using in a call to the
command to remove a bitstream.
https://my-repo.edu/handle/10822.2/1359
I find that if I change the tag
Yes, the subfolder are items exported by the export tool. There is a valid
dublin_core.xml with all metadata of the item.
I tried it also with the doi of the item (-i dc.identifier.doi), but the
error message is the same.
I think the identifier is not found because the dublin_core.xml is not
l
Could you describe the contents of the -s directory_archive folder that you
are using?
Each subfolder of that folder must have a metadata file that will uniquely
identify en existing DSpace item. dc.identifier.uri it the default field
that is used to make a match.
On Mon, Nov 20, 2017 at 3:34 AM
Hi everyone,
we are working with Dspace-Cris v.5.8 and try to delete some metadata
fields via ItemUpdate tool on the command line. It cannot load the data:
"processing item 1
Loaded metadata with 0 fields" and consequently does not find the
identifier: "Exception processing item 1: java.lang.Ex