Thank you Benjamin for your fast response I will update my sword package
right now.
On 20/06/13 08:17, Benjamin Ryan wrote:
Moises,
This is a problem with the 1.8 SWORV2 version, there is an updated
package at https://github.com/swordapp/DSpaceSWORDv2
There is also an updated config file that you should check.
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:*Moisés Álvarez [mailto:[email protected]]
*Sent:* 20 June 2013 06:52
*To:* [email protected]
*Subject:* [Dspace-tech] SWORDv2 ingestion error
I've got a problem ingesting DSpaceMETSSIP packages using SWORD v2
method on DSpace 1.8.0.
I've created a simple collection without submission workflows defined
on it and when I upload zip packages to it from a sword v2 client I
get "Invalid workflow state" exception on sword server side and
ingestion fails. I've found the source of such exception inside
/WorkflowManagerDefault/ class, specially on it's function:
resolveState(Context context, Deposit deposit, DepositResult result,
VerboseDescription verboseDescription, boolean){
...
// or find out if the item is in the archive
boolean inarch = item.isArchived() || item.isWithdrawn();
// in progress inws inwf inarch action description
// 0 0 0 1 ERROR the
deposit finished, and the item is in the archive; this should never be allowed
to arise
// 0 0 1 0 NOTHING the
deposit finished, and the item is in the workflow. Carry on as normal
// 0 1 0 0 START WF the
deposit is finished, and the item is in the workflow, so we start it
// 1 0 0 1 ERROR the
deposit is not finished, and the item is in the archive; this should never be
allowed to arise
// 1 0 1 0 STOP WF the
deposit is not finished, and it is in the workflow. Pull it out into the
workspace
// 1 1 0 0 NOTHING the
deposit is not finished, and is in the workspace; leave it there
if (!deposit.isInProgress() && inarch)
{
verboseDescription.append("The deposit is finished, but the item is
already in the archive");
throw new DSpaceSwordException("Invalid workflow state");
}
...
}
My package has inarch=true (archived, not withdrawn) and is not
inProgress so such exception raises, as stated in status table "this
should never be allowed to arise" but arises for every try to upload
files via SWORDv2, it's a code bug or do I need to create collection
workflows to ingest to collection with SWORDv2? If I comment throw
line, ingestion is done correctly.
Thank you in advance
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
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
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
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
