Hi Tim,
I was able to solve this issue. It was tied to input forms. Our instance is
multilingual (4 languages) . It looks like that someone was changing
translation versions of the input form, while the main version was
unchanged or there was mismatch. The main input form form was syntactica
Hi Enes,
Sorry, I've run out of ideas here. As you aren't able to reproduce this on
another server, and I cannot reproduce this on my end (or on demo.dspace.org),
it seems to me it's likely to be one of the following (but I don't know
which one):
1. A configuration problem in either curate.cfg o
Hi Tim,
I have tried to copy the original curate.cfg, but it is the same outcome.
I do not thing that it is the problem with curate.cfg. The strange thing
is that curation tasks have worked on this server for several months and
tnen stopped working.
Regards,
Enes
On Monday, March 26, 2018 a
Hi Enes,
Huh, that is weird. That configuration / output looks perfectly reasonable
to me, and I see it includes an entry named "requiredmetadata" which is the
exact task that threw the "Task: requiredmetadata not resolved" error.
So, that's very odd to me... DSpace seems to see you have a confi
Hi Tim,
I executed:
dspace/bin/dspace dsprop -p plugin.named.org.dspace.curate.CurationTask -r
My output is:
[org.dspace.ctask.general.NoOpCurationTask = noop,
org.dspace.ctask.general.ProfileFormats = profileformats,
org.dspace.ctask.general.RequiredMetadata = requiredmetadata,
org.dspace.cta
Hi Enes,
To me, that error "Task: requiredmetadata not resolved", still sounds
suspiciously like a configuration problem. So, I'm wondering if your
primary configuration in curate.cfg is being accidentally overridden
elsewhere (e.g. in local.cfg), or perhaps if the curate.cfg files isn't
being lo
Hi Tim,
This happens on every curation task that I run on this machine. For
example:
dspace/bin/dspace curate -t requiredmetadata -i 123456789/3770 -r - -v
Adding task: requiredmetadata
Task: requiredmetadata not resolved
Starting curation
Curating id: 123456789/3770
Ending curation. Elapsed ti
Hi Enes,
I just did a basic test of Curation Tasks on our http://demo.dspace.org
server. On that server, I ran the following on the commandline:
[dspace]/bin/dspace curate -t checklinks -i 10673/5 -r - -v
And, the "checklinks" curation task ran successfully on this item:
http://demo.dspace.org/
We have three DSpace 6 instances on CentOS 7. On one instance, curation
tasks are not working from either CLI, XMLUI or our custom forms. The
configuration is the same on all three instances. If we run dspace curate
-t taskname -i 123456789/3770 -r - -v , we get Task: taskname not
resolved.
