<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><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">Phone: +45 61775599</div></div></div></div>
<br><div class="gmail_quote">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><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc 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 class=""><br>
-----Original Message-----<br>
From: <a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">eprints-tech-bounces@ecs.soton.ac.uk</a> [mailto:<a href="mailto:eprints-tech-bounces@ecs.soton.ac.uk">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">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 class="">> 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 class="HOEnZb"><div class="h5">> 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 class="HOEnZb"><div class="h5">> Email: <a href="mailto:hugo.f.alroe@gmail.com">hugo.f.alroe@gmail.com</a> <mailto:<a href="mailto:hugo.f.alroe@gmail.com">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><br></div>