EPrints Technical Mailing List Archive

Message: #07837

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Antwort: RE: Hyperauthorship

Hi,

we thought of limiting the rendering, too. However, in that case, the database has to deliver the author records before the limit is applied, which involves a performance penalty. Anyone who had to deal with a 2000 author item in EPrints can tell what this is like. That's why we decided to limit on input already.  

Cheers,

Martin

Inactive hide details for "John Salter" ---16.05.2019 14:36:13---Hi Martin, Interesting approach. The records I'm, looking at a"John Salter" ---16.05.2019 14:36:13---Hi Martin, Interesting approach. The records I'm, looking at all come via Symplectic or Pure - and w

Von: "John Salter" <J.Salter@leeds.ac.uk>
An: "martin.braendle@id.uzh.ch" <martin.braendle@id.uzh.ch>, "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
Datum: 16.05.2019 14:36
Betreff: RE: [EP-tech] Hyperauthorship




Hi Martin,
Interesting approach. The records I'm, looking at all come via Symplectic or Pure - and we could implement some form of limit to the number of authors - and retain any that are 'resolved' (local) authors.
 
I was thinking of changing the default input rendering for the creator field along these lines:
If there are < LIMIT authors, render input as currently exists
If there are > LIMIT authors, render a static list of them, and enhance with _javascript_ to allow editing of specific entries / re-ordering / searching filtering the list.
 
This could even be deployed as a separate workflow stage (which only appears when there are > LIMIT authors).
 
I'll have to see what people here think about limiting the author list on the way in to EPrints - that sounds like a better place to be…
 
Cheers,
John
 
 
From: martin.braendle@id.uzh.ch [mailto:martin.braendle@id.uzh.ch]
Sent: 16 May 2019 13:22
To: eprints-tech@ecs.soton.ac.uk; John Salter <J.Salter@leeds.ac.uk>
Subject: Re: [EP-tech] Hyperauthorship
 

Hi John,

we have a lot of high energy physics or biomedical articles with hundreds or thousands of authors. Usually, those are submitted via CrossRef or PubMed import.

We have adapted the corresponding import plugins to limit the number of authors by a configurable limit (in our case 30). If the limit is exceeded, "et al" is added as the  ($limit+1)th author, the remaining authors are not imported and a warning message is issued. Submitters are then still free to add the remaining UZH authors manually and use et al for authors outside of UZH.

Instead of the DOI plugin, we have developed a CrossRef plugin that uses the CrossRef REST API . It implements the author limitation as well. We decided to go with the CrossRef REST API because funder information can be imported from there.

Best regards,

Martin

--
Dr. Martin Brändle
https://orcid.org/0000-0002-7752-6567
Zentrale Informatik
Universität Zürich
Stampfenbachstr. 73
CH-8006 Zürich

Inactive hide details for "John Salter via Eprints-tech" ---16.05.2019 14:00:41---Hi, Has anyone done any work on making the EP"John Salter via Eprints-tech" ---16.05.2019 14:00:41---Hi, Has anyone done any work on making the EPrints workflow a bit more sensible when a paper has man

Von: "John Salter via Eprints-tech" <eprints-tech@ecs.soton.ac.uk>
An: "'eprints-tech@ecs.soton.ac.uk'" <eprints-tech@ecs.soton.ac.uk>
Datum: 16.05.2019 14:00
Betreff: [EP-tech] Hyperauthorship
Gesendet von: <eprints-tech-bounces@ecs.soton.ac.uk>





Hi,
Has anyone done any work on making the EPrints workflow a bit more sensible when a paper has many authors (hundreds or thousands)?

Cheers,
John


John Salter
http://orcid.org/0000-0002-8611-8266

White Rose Libraries Technical Officer
IT - Application Support (Research)
10.23B, IT Services Building
University of Leeds
Leeds
LS2 9JT
0113 34 37385

Online: https://whiteroselibraries.wordpress.com/
WRL_email_signature_thelmas_
*** 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/