<div dir="ltr">Hi John <div>Thank you for your help. The video was immensely helpful. We implemented the new automatic field by adding a new configuration file (se file below) and added the field conf_subm ("Conference submissions, Yes, No") to the editor rights restrictions. This was a bit difficult to find, but it is done in the <a href="http://search.pl">search.pl</a> file, in "editor_limit_fields", where I added the line:</div><div><span class="" style="white-space:pre"> </span>"conf_subm", # HFA 6jan2016: Added to allow for selecting the automatic conference submission field </div><div>I added phrases by way of "Edit page phrases".</div><div><div><br></div><div>It works fine. Speed gain on a review buffer of 412 eprints: before (15 restrictions) = 256 seconds to see a buffer of 100, after (1 restriction) = 8 seconds to see a buffer of 100. That is, about 30 times faster.</div></div><div><br></div><div>Best regards,</div><div>Hugo</div><div><br></div><div><br></div><div>----eprint_type_conf_subm.pl----</div><div><div>## HFA 2016jan06: This automatic field function is meant to solve the problem with very slow speed when editors work in their buffer, </div><div>## because most national editors have 15 eprint types (all but the conference submissions) in their editorial rights restrictions to </div><div>## avoid conference submissions being moved into the archive prematurely by the national editors. </div><div>## Any editorial-scope options that are 'set' or 'namedset' fields create some big SQL statements when used together </div><div>## (lots of ORs over lots of tables). See Eprints Tech list mail 18dec2015 on "Editoring speed problem and Review queue option".</div><div>## An automatic field that stores a value 'subm' or 'not_subm' will give a much more efficient </div><div>## (and hopefully quick-enough) way to restrict the review queue for conference submissions.</div><div>## This will create a field (called 'conf_subm')to use for groupings of editorial rights for eprint type 'submission', </div><div>## one group for conference submissions and another for alle the other eprint types.</div><div>## See <a href="http://wiki.eprints.org/w/index.php/Training_Video:Automatic_Fields">http://wiki.eprints.org/w/index.php/Training_Video:Automatic_Fields</a>.</div><div>$c->add_dataset_field('eprint',</div><div>{</div><div><span class="" style="white-space:pre"> </span>name => 'conf_subm',</div><div><span class="" style="white-space:pre"> </span>type => 'set',</div><div><span class="" style="white-space:pre"> </span>options => [</div><div><span class="" style="white-space:pre"> </span>'subm',</div><div><span class="" style="white-space:pre"> </span>'not_subm',</div><div><span class="" style="white-space:pre"> </span>]</div><div>}</div><div>);</div><div><br></div><div>$c->{set_eprint_automatic_fields_eprint_type_conf_subm} = $c->{set_eprint_automatic_fields};</div><div>$c->{set_eprint_automatic_fields} = sub</div><div>{</div><div><span class="" style="white-space:pre"> </span>my( $eprint ) = @_;</div><div><span class="" style="white-space:pre"> </span></div><div><span class="" style="white-space:pre"> </span>my $repo = $eprint->repository;</div><div><span class="" style="white-space:pre"> </span>$repo->call('set_eprint_automatic_fields_eprint_type_conf_subm', $eprint);</div><div><span class="" style="white-space:pre"> </span></div><div><span class="" style="white-space:pre"> </span>## Set value according to eprint type submission or not</div><div><span class="" style="white-space:pre"> </span>my $type = $eprint->get_value( "type" );</div><div><br></div><div><span class="" style="white-space:pre"> </span>if( $type eq "submission")</div><div><span class="" style="white-space:pre"> </span>{</div><div><span class="" style="white-space:pre"> </span>$eprint->set_value( "conf_subm", "subm" );</div><div><span class="" style="white-space:pre"> </span>}</div><div><span class="" style="white-space:pre"> </span>else</div><div><span class="" style="white-space:pre"> </span>{</div><div><span class="" style="white-space:pre"> </span>$eprint->set_value( "conf_subm", "not_subm" );</div><div><span class="" style="white-space:pre"> </span>};</div><div><span class="" style="white-space:pre"> </span></div><div>}</div></div><div>----end of file----</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div style="font-family:arial;font-size:small">Hugo F. Alrøe<br></div><div style="font-family:arial;font-size:small">Email: <a href="mailto:hugo.f.alroe@gmail.com" target="_blank">hugo.f.alroe@gmail.com</a></div><div style="font-family:arial;font-size:small"><br></div></div></div></div>
<br><div class="gmail_quote">2015-12-18 11:57 GMT+01:00 Hugo F. Alrøe <span dir="ltr"><<a href="mailto:hugo.f.alroe@gmail.com" target="_blank">hugo.f.alroe@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><div dir="ltr">Thank you, John,<div>Yes, that was our thought as well, that it was the database queries that multiplied.</div><div>Thank you for the idea on using automatic fields to simplify the proces. As I understand you, this will only influence on how the editorial rights are handled, and not require changes to the eprints types and how the user sees this. It sounds like a doable approach to the problem, and I will look into it. </div><div>We would probably still like to use the Reviewed Queue package to help the conference reviewing process, but in a way where we won't rely on it as an essential element in submission process. </div><div>Cheers,</div><div>Hugo</div></div></span><div class="gmail_extra"><span class=""><br clear="all"><div><div dir="ltr"><div style="font-family:arial;font-size:small">Hugo F. Alrøe<br></div><div style="font-family:arial;font-size:small">Email: <a href="mailto:hugo.f.alroe@gmail.com" target="_blank">hugo.f.alroe@gmail.com</a></div><div style="font-family:arial;font-size:small"><br></div></div></div>
<br></span><div class="gmail_quote"><span class="">2015-12-18 10:45 GMT+01:00 John Salter <span dir="ltr"><<a href="mailto:J.Salter@leeds.ac.uk" target="_blank">J.Salter@leeds.ac.uk</a>></span>:<br></span><div><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
I think that any editorial-scope options that are 'set' or 'namedset' fields create some big SQL statements when used together (lots of ORs over lots of tables).<br>
<br>
It sounds like you need one group for (not conference) and another for (conference).<br>
<br>
My approach to this would be to create a field to use for groupings of editorial rights (<a href="http://wiki.eprints.org/w/index.php/Training_Video:Automatic_Fields" rel="noreferrer" target="_blank">http://wiki.eprints.org/w/index.php/Training_Video:Automatic_Fields</a>).<br>
If you have an automatic field that stores a value 'conf' or 'not_conf' - you then have a much more efficient (and hopefully quick-enough) way to restrict the review queue.<br>
<br>
I can't comment on the 'Reviewed' package in the Bazaar - I haven't used it.<br>
<br>
Cheers,<br>
John<br>
<span><br>
-----Original Message-----<br>
From: <a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk" target="_blank">eprints-tech-bounces@ecs.soton.ac.uk</a> [mailto:<a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk" target="_blank">eprints-tech-bounces@ecs.soton.ac.uk</a>] On Behalf Of Yuri<br>
Sent: 18 December 2015 09:11<br>
To: <a href="mailto:eprints-tech@ecs.soton.ac.uk" target="_blank">eprints-tech@ecs.soton.ac.uk</a><br>
Subject: [EP-tech] Re: Editoring speed problem and Review queue option<br>
<br>
Isn't better to fix the slowness? i wouldn't depend, on big projects, on<br>
plugins found on Bazaar if I'm not sure they're well mantained.<br>
<br>
Il 18/12/2015 09:39, Hugo F. Alrøe ha scritto:<br>
</span><span>> Hi<br>
><br>
> We have experienced speed problems when editoring on our archive<br>
</span>> Organic Eprints (<a href="http://www.orgprints.org" rel="noreferrer" target="_blank">www.orgprints.org</a> <<a href="http://www.orgprints.org" rel="noreferrer" target="_blank">http://www.orgprints.org</a>>). We<br>
<div><div>> have +30 editors with responsibilities for different countries and<br>
> projects, and some of them, but only some, experience that the system<br>
> is very slow when they are working with the review buffer. Search etc.<br>
> is not affected.<br>
><br>
> I finally found out that the number of editorial rights restrictions<br>
> affect the speed of showing the review buffer substantially. We have<br>
> some 16 eprint types (yes, I know, too many, but the archive has many<br>
> different kinds of eprints), and one of these (conference submissions)<br>
> has to be handled by different editors. This means most of our<br>
> national editors have 15 eprint types (all but the conference<br>
> submissions) in their editorial rights restrictions, to avoid<br>
> conference submissions being moved into the archive prematurely by the<br>
> national editors. Some editors have a number of countries and projects<br>
> as well in their editorial rights restrictions, which means that<br>
> showing the buffer can be veeery slow (like, go get a cup of coffee,<br>
> start on something else, and forget about it).<br>
><br>
> To solve this problem, I think about handling the conference<br>
> submissions differently. In the ePrints Bazaar I found the Reviewed<br>
> queue package, which offers a functionality that potentially can meet<br>
> this purpose by establishing an additional review buffer.<br>
><br>
> For this to work however, eprints of type conference submissions<br>
> should go automatically into this additional buffer. Is this possible?<br>
> And if so, how?<br>
><br>
> And preferably it should be possible to restrict most editors from<br>
> seeing this additional buffer. We have editors with different powers<br>
> already (some being able to modify the subject trees to e.g. add new<br>
> research affiliations). But I am not sure whether the additional<br>
> buffer established by Reviewed queue can be allocated to a specific<br>
> editor type. Is this possible?<br>
><br>
> Can anybody help on these questions?<br>
><br>
> Best regards<br>
> Hugo Alroe<br>
> Initiator (in 2002) of Organic Eprints and presently temporary archive<br>
> administrator.<br>
><br>
</div></div><div><div>> Email: <a href="mailto:hugo.f.alroe@gmail.com" target="_blank">hugo.f.alroe@gmail.com</a> <mailto:<a href="mailto:hugo.f.alroe@gmail.com" target="_blank">hugo.f.alroe@gmail.com</a>><br>
><br>
><br>
><br>
> *** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" rel="noreferrer" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
> *** Archive: <a href="http://www.eprints.org/tech.php/" rel="noreferrer" target="_blank">http://www.eprints.org/tech.php/</a><br>
> *** EPrints community wiki: <a href="http://wiki.eprints.org/" rel="noreferrer" target="_blank">http://wiki.eprints.org/</a><br>
> *** EPrints developers Forum: <a href="http://forum.eprints.org/" rel="noreferrer" target="_blank">http://forum.eprints.org/</a><br>
<br>
<br>
*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" rel="noreferrer" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
*** Archive: <a href="http://www.eprints.org/tech.php/" rel="noreferrer" target="_blank">http://www.eprints.org/tech.php/</a><br>
*** EPrints community wiki: <a href="http://wiki.eprints.org/" rel="noreferrer" target="_blank">http://wiki.eprints.org/</a><br>
*** EPrints developers Forum: <a href="http://forum.eprints.org/" rel="noreferrer" target="_blank">http://forum.eprints.org/</a><br>
<br>
*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" rel="noreferrer" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
*** Archive: <a href="http://www.eprints.org/tech.php/" rel="noreferrer" target="_blank">http://www.eprints.org/tech.php/</a><br>
*** EPrints community wiki: <a href="http://wiki.eprints.org/" rel="noreferrer" target="_blank">http://wiki.eprints.org/</a><br>
*** EPrints developers Forum: <a href="http://forum.eprints.org/" rel="noreferrer" target="_blank">http://forum.eprints.org/</a><br>
</div></div></blockquote></div></div></div><br></div>
<br>*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" rel="noreferrer" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
*** Archive: <a href="http://www.eprints.org/tech.php/" rel="noreferrer" target="_blank">http://www.eprints.org/tech.php/</a><br>
*** EPrints community wiki: <a href="http://wiki.eprints.org/" rel="noreferrer" target="_blank">http://wiki.eprints.org/</a><br>
*** EPrints developers Forum: <a href="http://forum.eprints.org/" rel="noreferrer" target="_blank">http://forum.eprints.org/</a><br>
<br></blockquote></div><br></div></div>