Hi,
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).

It sounds like you need one group for (not conference) and another for (conference).

My approach to this would be to create a field to use for groupings of editorial rights (http://wiki.eprints.org/w/index.php/Training_Video:Automatic_Fields).
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.

I can't comment on the 'Reviewed' package in the Bazaar - I haven't used it.

Cheers,
John

-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Yuri
Sent: 18 December 2015 09:11
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: Editoring speed problem and Review queue option

Isn't better to fix the slowness? i wouldn't depend, on big projects, on
plugins found on Bazaar if I'm not sure they're well mantained.

Il 18/12/2015 09:39, Hugo F. Alrøe ha scritto:
> Hi
>
> We have experienced speed problems when editoring on our archive
> Organic Eprints (www.orgprints.org <http://www.orgprints.org>). We

> have +30 editors with responsibilities for different countries and
> projects, and some of them, but only some, experience that the system
> is very slow when they are working with the review buffer. Search etc.
> is not affected.
>
> I finally found out that the number of editorial rights restrictions
> affect the speed of showing the review buffer substantially. We have
> some 16 eprint types (yes, I know, too many, but the archive has many
> different kinds of eprints), and one of these (conference submissions)
> has to be handled by different editors. This means most of our
> national editors have 15 eprint types (all but the conference
> submissions) in their editorial rights restrictions, to avoid
> conference submissions being moved into the archive prematurely by the
> national editors. Some editors have a number of countries and projects
> as well in their editorial rights restrictions, which means that
> showing the buffer can be veeery slow (like, go get a cup of coffee,
> start on something else, and forget about it).
>
> To solve this problem, I think about handling the conference
> submissions differently. In the ePrints Bazaar I found the Reviewed
> queue package, which offers a functionality that potentially can meet
> this purpose by establishing an additional review buffer.
>
> For this to work however, eprints of type conference submissions
> should go automatically into this additional buffer. Is this possible?
> And if so, how?
>
> And preferably it should be possible to restrict most editors from
> seeing this additional buffer. We have editors with different powers
> already (some being able to modify the subject trees to e.g. add new
> research affiliations). But I am not sure whether the additional
> buffer established by Reviewed queue can be allocated to a specific
> editor type. Is this possible?
>
> Can anybody help on these questions?
>
> Best regards
> Hugo Alroe
> Initiator (in 2002) of Organic Eprints and presently temporary archive
> administrator.
>

> Email: hugo.f.alroe@gmail.com <mailto:hugo.f.alroe@gmail.com>
>
>
>
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/


*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/