Hi
I developed custom Java code that I am planning to push out to GitHub. I just
didn’t get to it yet.
I am working with version 1.8 but the code should be fine with version 3 and 4.
It implements a command line utility to
1. list things in dspace,
2. to add and delete policies on listed entities,
3. to replace bitstream files
4. to replace individual metadata values
In your case you would do something like the following command, which traces
which the resulting policy settings
> $DSPACE_HOME/bin/dspace bulk-pols -r <CommunityHandle> --type COLLECTION -a
> ADD -d WORKFLOW_STEP_2 -w GROUP.irsubmitter
object=COLLECTION.293 parent=COMMUNITY.37
POLICY.WORKFLOW_STEP_2=[POLICY.35508(GROUP.irsubmitter)]
object=COLLECTION.294 parent=COMMUNITY.37
POLICY.WORKFLOW_STEP_2=[POLICY.35509(GROUP.irsubmitter)]
object=COLLECTION.295 parent=COMMUNITY.37
POLICY.WORKFLOW_STEP_2=[POLICY.35510(GROUP.irsubmitter)]
object=COLLECTION.296 parent=COMMUNITY.37
POLICY.WORKFLOW_STEP_2=[POLICY.35511(GROUP.irsubmitter)]
object=COLLECTION.297 parent=COMMUNITY.37
POLICY.WORKFLOW_STEP_2=[POLICY.35512(GROUP.irsubmitter)]
object=COLLECTION.298 parent=COMMUNITY.37
POLICY.WORKFLOW_STEP_2=[POLICY.35513(GROUP.irsubmitter)]
object=COLLECTION.299 parent=COMMUNITY.37
POLICY.WORKFLOW_STEP_2=[POLICY.35514(GROUP.irsubmitter)]
...
This ADDs the irsubmitter group (which you need to create before using the
command) to WORKFLOW_STEP_2 on all collections that are part of the given
community
The companion list command allows you to check on policies
> $DSPACE_HOME/bin/dspace bulk-list -r 88435/1096 -t COLLECTION --include
> 'object,handle,POLICY.WORKFLOW_STEP_2,name'
object=COLLECTION.293 handle=88435/1097
POLICY.WORKFLOW_STEP_2=[POLICY.35508(GROUP.irsubmitter)] name=Aeronautical
Engineering
object=COLLECTION.294 handle=88435/1098
POLICY.WORKFLOW_STEP_2=[POLICY.35509(GROUP.irsubmitter)] name=Anthropology
object=COLLECTION.295 handle=88435/1099
POLICY.WORKFLOW_STEP_2=[POLICY.35510(GROUP.irsubmitter)] name=Architecture
School
object=COLLECTION.296 handle=88435/1100
POLICY.WORKFLOW_STEP_2=[POLICY.35511(GROUP.irsubmitter)] name=Art and
Archaeology
object=COLLECTION.297 handle=88435/1101
POLICY.WORKFLOW_STEP_2=[POLICY.35512(GROUP.irsubmitter)] name=Astrophysical
Sciences
object=COLLECTION.298 handle=88435/1102
POLICY.WORKFLOW_STEP_2=[POLICY.35513(GROUP.irsubmitter)] name=Biology
object=COLLECTION.299 handle=88435/1103
POLICY.WORKFLOW_STEP_2=[POLICY.35514(GROUP.irsubmitter)] name=Chemical and
Biological Engineering
…
If you are interested I can push the code in the next couple days.
Monika
________________
Monika Mevenkamp
phone: 609-258-4161
Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ
08544
On May 6, 2014, at 3:55 AM,
<amutsik...@uzlib.uz.ac.zw<mailto:amutsik...@uzlib.uz.ac.zw>>
<amutsik...@uzlib.uz.ac.zw<mailto:amutsik...@uzlib.uz.ac.zw>> wrote:
Hi
Hope I found you well. We are in the process of trying to improve the quality
of our submission process. We would like to add a group called irsubmitter for
submission as well as irreviewer to step 2 of the workflows of all
collections in our repository. We have a number of collections so we do not
intend to do this manually. We will appreciate a global way through may be an
SQL statement to achieve that.
Kind Regards,
Admire Mutsikiwa
ICT Projects Manager
Libraries
University of Zimbabwe
Tel:+263-4-303276<tel:+263-4-303276>
“It is easy to dodge our responsibilities, but we cannot dodge the consequences
of dodging our responsibilities.” Josiah Charles Stamp, 1880-1941, former
director of the Bank of England
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
