Hi everyone!
Currently the selection of the XmlWorkflow to use, the submission process
and the DescribeStep's form definition is based on the handle of the
collection which owns the item.
There are many cases in which it would be very useful to be able to define
that configuration based on a comunity's handle, and let the descendant
collections to inherit that configuration. That way you wouldn't have to
replicate the configuration for every involved collection.
We are about to change the selection method in order to look for the
collection's handle first, and then for its parents communities (their
handles), in ascending order.
We would like to hear your thoughts on this and if you think it would be a
useful patch for dspace.
Regards
Nestor
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel