<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Chris, hi John,<br>
<br>
thanks a lot for your quick replies and your hints! I'll take a
look at both solutions and let you know if I got it all to work.<br>
<br>
Regards,<br>
Johannes<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:DB6PR0302MB27119CC6F070C8A3F8BF0EADC4E20@DB6PR0302MB2711.eurprd03.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;
        color:black;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">There
is a different way to achieve this.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">You
can add new 'eprint_status' options.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">This
page:
<a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FBuilding_a_DataSet&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd96c65ccbbc4405b526d08d6fa352912%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=UNSD538gpsWJr3MG3MvE%2Bac26GS9%2FWthD5o5Bud1u5E%3D&reserved=0" originalSrc="https://wiki.eprints.org/w/Building_a_DataSet" shash="LDFpnjLUtDOYUrrD5l41IGTwug5483SCQiyo49inD4yv9P6sSWLL4koXAkanjN2Cz/YHDYgsBymVqVppdj0twO6xBdIOntPZvlwVinak62PaNAn7WoG+1lzit63NnriBEzT0pmCx1gvZmQrO+TUyV+q7FIeOg1+Q7qi0M9Uy9DE="
moz-do-not-send="true">https://wiki.eprints.org/w/Building_a_DataSet</a>
provides details of how to create a 'dark archive' - which
is normally a different end-point for a record - so instead
of:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Inbox
-> buffer -> archive<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">You
can also go:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Inbox
-> buffer -> dark_archive<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">This
plugin does the same:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><a
href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbazaar.eprints.org%2F401%2F&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd96c65ccbbc4405b526d08d6fa352912%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=djBAK9KW%2FJ6zNSybtvtjGS54qA3bQDZOJfTy8F5sK2s%3D&reserved=0" originalSrc="http://bazaar.eprints.org/401/" shash="urSXljIMYkinKdHpJA+jyPv9/O79ZNFbRj3PYpp0EYuKZBswv4sKnY4NnZPIhzLQpnKeUZ0LknH/n9Hwo1bsQjX/YwXYxQnwMGC08IPGOphAvVc4pVJHwkvDHLis5Lk3Z7lh1Uu2NHqcL5H1cLdF52BMGdNsh/g9HtuFUvk1Lwc="
moz-do-not-send="true">http://bazaar.eprints.org/401/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">What
you would need to configure is
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">options
=> [qw( inbox buffer archive deletion bufferX bufferY )],<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">and
also think about whether anyone can move e.g. from buffer to
archive - or whether everything has to go through all
stages.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">You
may want to define more user roles - so a 'normal' editor
can move from buffer to bufferX, but a 'super editor' can
move from buffer to bufferX, bufferY or even to archive.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">You
may also want to create a clone of the review screen that
looks at bufferX and buffer explicitily.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Chris'
solution would also work, each has it's merits!<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Cheers,<br>
John<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">eprints-tech-bounces@ecs.soton.ac.uk</a>
[<a class="moz-txt-link-freetext" href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">mailto:eprints-tech-bounces@ecs.soton.ac.uk</a>] <b>On
Behalf Of </b>Christöpher Gutteridge via Eprints-tech<br>
<b>Sent:</b> 26 June 2019 12:06<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a>; Johannes
Schultze <a class="moz-txt-link-rfc2396E" href="mailto:schultze@effective-webwork.de"><schultze@effective-webwork.de></a><br>
<b>Subject:</b> Re: [EP-tech] Adding more stages to
approval workflow?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>This isn't trivial but would be possible. This is me riffing
and would need refining.<o:p></o:p></p>
<p>First of all, I would add tickbox fields for levels of
signoff. ie. signoffA and signoffB and signoffC.<o:p></o:p></p>
<p>Next I would use conditionals on the "workflow" XML file to
modify it as follows.<o:p></o:p></p>
<p>In the main <flow> section, use a <when>
condition to split behaviour for the 3 stages of the buffer to
add additional stages to the end IF the user has the
appropriate parameters. At an extreme level you can write a
plugin function that takes the user and eprint as inputs and
returns true if they have the right to approve it at stage
a/b/c.<o:p></o:p></p>
<p>If signoffA is false and the user can approve level A on this
EPrint, they see the levelA approve stage which has the
signoffA tickbox on it and they can set it to true.<o:p></o:p></p>
<p>If signoffA is true, but signoffB is false and the user can
approve level B, the see the levelB approve stage which has
the signoffB tickbox<o:p></o:p></p>
<p>Similar for signoffC.<o:p></o:p></p>
<p>The validation for publishing makes "signoffC" approval a
required field so it can't be published without signoffC being
set.<o:p></o:p></p>
<pre><flow><o:p></o:p></pre>
<pre> <stage ref="type"/><o:p></o:p></pre>
<pre> <stage ref="files"/><o:p></o:p></pre>
<pre> <stage ref="core"/><o:p></o:p></pre>
<pre> <stage ref="subjects"/><o:p></o:p></pre>
<pre> <epc:choose><o:p></o:p></pre>
<pre> <epc:when test="eprint_status='buffer' and !signoffA and $current_user{canSignoffA}'><o:p></o:p></pre>
<pre> <stage ref="signoffA" /><o:p></o:p></pre>
<pre> </epc:when><o:p></o:p></pre>
<pre> <epc:when test="eprint_status='buffer' and signoffA and !signoffB and $current_user{canSignoffB}'><o:p></o:p></pre>
<pre> <stage ref="signoffB" /><o:p></o:p></pre>
<pre> </epc:when><o:p></o:p></pre>
<pre> <epc:when test="eprint_status='buffer' and signoffA and signoffB and !signoffC and $current_user{canSignoffC}'><o:p></o:p></pre>
<pre> <stage ref="signoffC" /><o:p></o:p></pre>
<pre> </epc:when><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> </epc:choose><o:p></o:p></pre>
<pre> </flow><o:p></o:p></pre>
<p>This is utterly untested but gives some ideas I hope.
Documentation here:<o:p></o:p></p>
<p><a
href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEPrints_Control_Format&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd96c65ccbbc4405b526d08d6fa352912%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=gce0LpGDdffi9AUeCr6Obukb9LHv5gos0KJt1J6PgQU%3D&reserved=0" originalSrc="https://wiki.eprints.org/w/EPrints_Control_Format" shash="OVMzPllil5tTDdrR/uUmjRXJoHmyW8B0SetgCgcV3sxs438At9YAprSQm1KjUWZbJGMGeTHgU4qhsTv7bz0NOOsNz+jYrjJNPWkdv/nh5tdPnVmPFxlpNht7o0CcEVDuXgjhZ19zp3FoXJJhKExkupCZr8qoJE/s2kPVqLRSHyA="
moz-do-not-send="true">https://wiki.eprints.org/w/EPrints_Control_Format</a><o:p></o:p></p>
<p><a
href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FWorkflow_Format&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd96c65ccbbc4405b526d08d6fa352912%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=P4QuQk3CakBhGMQOaZVQbmvZp%2BirE6erEmjsIn34m5k%3D&reserved=0" originalSrc="https://wiki.eprints.org/w/Workflow_Format" shash="JTVvZe3nFCxwH+ljjp672d8Tup21RijpnNQxJJf0QkzkbK/Mr20g/+gIUxkPS7ZqKFw3DxhOJ8Bw8Od0d2uiZAT4GN7anbiksDPX+AcN1LKCTPhjlcjptQOCMdwl36uW0v9J6hNwlqTPdtnYrponClpqRCNJg96wHUcEKbnNteo="
moz-do-not-send="true">https://wiki.eprints.org/w/Workflow_Format</a><o:p></o:p></p>
<p><a
href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEPScript&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd96c65ccbbc4405b526d08d6fa352912%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=m9VwoypeafWu9ip4O%2B06Idb75KzXy2As%2FGeD%2BL4hko4%3D&reserved=0" originalSrc="https://wiki.eprints.org/w/EPScript" shash="Plc8Rc8Pye1DBp9oILnVzzhRejTXgIiSpdo8X/TsjvEeFCtsFZPxhbi2lPaPogGP+5qg+K/IEiFyYUoAf9r0hEIjtmkHjBUVpEp9w0NlKCFs27yn580AMlUh370pYYgMMQlu1nRWoZVckoNlUyCmCswNLCgW/cl4COiVZ6RbV10="
moz-do-not-send="true">https://wiki.eprints.org/w/EPScript</a><o:p></o:p></p>
<p>It's possible to make custom EPScript functions to do more
complex tests.<o:p></o:p></p>
<p><o:p> </o:p></p>
<p><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 26/06/2019 11:05, Johannes Schultze
via Eprints-tech wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Hi all,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I'm currently evaluating EPrints as a replacement for an old repository <o:p></o:p></pre>
<pre>(custom made). Until now everything worked fine (import of existing <o:p></o:p></pre>
<pre>files and metadata), and I'm now trying to get the release/approval <o:p></o:p></pre>
<pre>workflow configured. As far as I have read in the documentation, there <o:p></o:p></pre>
<pre>are four stages by default:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>inbox -> buffer -> archive -> deletion<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I would need some more levels (and roles) in the approval workflow. <o:p></o:p></pre>
<pre>Something like this:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>inbox -> buffer1 -> buffer2 -> buffer3 -> archive -> deletion<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Different roles in the hierarchy of the organisation should approve the <o:p></o:p></pre>
<pre>submitted eprint in multiple steps. Is it possible to configure such <o:p></o:p></pre>
<pre>behaviour in EPrints? Or can something like this only be implemented <o:p></o:p></pre>
<pre>with some kind of plugin?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Regards<o:p></o:p></pre>
<pre>Johannes<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</blockquote>
<pre>-- <o:p></o:p></pre>
<pre>Christopher Gutteridge <a href="mailto:totl@soton.ac.uk" moz-do-not-send="true"><totl@soton.ac.uk></a> <o:p></o:p></pre>
<pre>You should read our team blog at <a href="http://blog.soton.ac.uk/webteam/" moz-do-not-send="true">http://blog.soton.ac.uk/webteam/</a><o:p></o:p></pre>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Dipl. Inf. Johannes Schultze
Gesellschafter / Entwicklung
Tel. +49 40 60940857-5
Fax. +49 40 60940857-1
<a class="moz-txt-link-abbreviated" href="mailto:schultze@effective-webwork.de">schultze@effective-webwork.de</a>
effective WEBWORK GmbH
Neuer Wall 18
20354 Hamburg
<a class="moz-txt-link-freetext" href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.effective-webwork.de&data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd96c65ccbbc4405b526d08d6fa352912%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=ipJopqjVC0312S7y3e8yvG0pYy0ZIVxPCe07cdqFsTc%3D&reserved=0" originalSrc="http://www.effective-webwork.de" shash="NVSkmFTeC/t3XI2spzsTKHjChLBl7YEqWwedyZ5utU21f0DwWrY1p5T7xJikTQvup8/c1zJh6luuD5JL6ImgS3lrfIwy802SsbttmXmZei+21naofTPeDouwuvIWiQI5dc4tGmbLKnddDZpCUBf29E6Knq+l0r7ESDI5vZbj7Og=">http://www.effective-webwork.de</a>
GF Dr. Matthias Finck
HRB 101108 (Hamburg)
UStId DE254169943</pre>
</body>
</html>