Another option would be to add further parameters to the cfg.d/plugin.pl configuration, and let read and process them by the Screen plugin that creates the menu do the work.

We have something similar for the import plugins as well:

# UZH CHANGE 2014/11/05 ZORA-353
#$c->{plugins}->{"Import::DOI"}->{params}->{rankthem} = 10;
$c->{plugins}->{"Import::DOI_CrossRef"}->{params}->{rankthem} = 10;
$c->{plugins}->{"Import::PubMedID"}->{params}->{rankthem} = 20;
$c->{plugins}->{"Import::UZHOrcid"}->{params}->{rankthem} = 30;
$c->{plugins}->{"Import::ScopusAbstract"}->{params}->{rankthem} = 40;
$c->{plugins}->{"Import::BibTeX"}->{params}->{rankthem} = 50;
$c->{plugins}->{"Import::Citavi"}->{params}->{rankthem} = 60;
$c->{plugins}->{"Import::EndNote"}->{params}->{rankthem} = 70;
$c->{plugins}->{"Import::XML"}->{params}->{rankthem} = 80;
$c->{plugins}->{"Import::ISIWoK"}->{params}->{rankthem} = 90;
$c->{plugins}->{"Import::RIS"}->{params}->{rankthem} = 100;
# END UZH CHANGE ZORA-353

This ranking was created according to statistics derived on import usage.

With regards to my saying on cost, I just looked up in JIRA how long the ZORA Search project took from initial concept design, early prototypes, implementation, beta, tests, production and go-live, documentation, help, deconstruction (Xapian), setting up maintenance procedures, and migrating associated services (Journal database www.jdb.uzh.ch, TrendTerms in ZORA). First sprint issue was started in May 2019. Last sprint issue was closed now in Sep 2021. 15 sub- and associated sprint issues.

P.S. On 16th November, 18:00 (Zurich time, CET, UTC+1) there will be a Elasticsearch Meetup streamed on Youtube where Jens and I will present our use case. We will post a link as soon as we have it.

Kind regards,

Martin



"John Salter" ---08/10/2021 11:42:57---> the price you pay is development and maintenance cost ☺ so true!

Von: "John Salter" <J.Salter@leeds.ac.uk>
An: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, "martin.braendle@uzh.ch" <martin.braendle@uzh.ch>, "Yuri" <yurj@alfa.it>
Datum: 08/10/2021 11:42
Betreff: RE: [EP-tech] Antwort: Re:  Export formats - v3.3.16+

The following permissions in the export plugin control behavior:

$self->{accept}  --> result list and / or details page , and which dataset
$self->{visible}  --> role, who can export
$self->{advertise} --> general visibility 

As pointed out before, there is no distinction between advanced and simple search in a standard installation of EPrints.

If you have your own implementation of search (as we did here at University of Zurich with Elasticsearch), you are able to fine-tune, e.g. which plugins are used and in which order they appear in the dropdown menu.

Search example:

https://www.zora.uzh.ch/search/?q=blood%20protein&size=n_10_n

Configuration example:

https://github.com/eprintsug/EPrintsElasticsearch/blob/main/archives/repositoryname/cfg/cfg.d/z_elasticsearch_export_plugins.pl

Code on Github for Elasticsearch in EPrints:

https://github.com/eprintsug/EPrintsElasticsearch

As with every non-standard installation, the price you pay is development and maintenance cost.

Kind regards,

Martin


"Yuri via Eprints-tech" ---08/10/2021 10:40:14---CAUTION: This e-mail originated outside the University of Southampton. For a project, I've added the

Von: "Yuri via Eprints-tech" <eprints-tech@ecs.soton.ac.uk>
An: eprints-tech@ecs.soton.ac.uk
Datum: 08/10/2021 10:40
Betreff: Re: [EP-tech] Export formats - v3.3.16+
Gesendet von: <eprints-tech-bounces@ecs.soton.ac.uk>

For a project, I've added the export dropdown to the single abstract page. As John pointed out, the list is regulated by the plugin permissions, so it is not possible to change the list based on search.

Maybe if you have a use case to explain us, there could be another solution.

Il 08/10/21 03:07, Matthew Brady via Eprints-tech ha scritto:
CAUTION: This e-mail originated outside the University of Southampton.
Hi All,

When conducting a search, the results get listed, and there is a dropdown with options for different export formats (DC, EndNote, Ref Manager et. al.).

I am having a mental blank at the moment… but is it possible to adjust which export options can be used, based on which search was performed…

e.g.
simple search (cgi/search/simple)
advanced search (cgi/search/advanced)
admin staff search (cgi/search/eprint/staff)

Thanks for any help/advice that can be offered.

Matt 

__________________________________________________________________
This email (including any attached files) is confidential and is  
for the intended recipient(s) only. If you received this email by  
mistake, please, as a courtesy, tell the sender, then delete this  
email.
The views and opinions are the originator's and do not necessarily  
reflect those of the University of Southern Queensland. Although  
all reasonable precautions were taken to ensure that this email  
contained no viruses at the time it was sent we accept no  
liability for any losses arising from its receipt.
The University of Southern Queensland is a registered provider  
of education with the Australian Government.
(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081)

*** 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/*** 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/