[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Antwort: RE: Hyperauthorship


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.



Von:	"John Salter" <J.Salter at leeds.ac.uk>
An:	"martin.braendle at id.uzh.ch" <martin.braendle at id.uzh.ch>,
            "eprints-tech at ecs.soton.ac.uk" <eprints-tech at 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?


From: martin.braendle at id.uzh.ch [mailto:martin.braendle at id.uzh.ch]
Sent: 16 May 2019 13:22
To: eprints-tech at ecs.soton.ac.uk; John Salter <J.Salter at 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

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,


Dr. Martin Br?ndle
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 at ecs.soton.ac.uk>
An: "'eprints-tech at ecs.soton.ac.uk'" <eprints-tech at ecs.soton.ac.uk>
Datum: 16.05.2019 14:00
Betreff: [EP-tech] Hyperauthorship
Gesendet von: <eprints-tech-bounces at ecs.soton.ac.uk>

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


John Salter

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

Online: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhiteroselibraries.wordpress.com%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C9848f3511de64c83e91208d6da0411d5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=92hjAwhBFqfB7XomrfjKFK8RR6RFkMCeyGXIWThqjKM%3D&amp;reserved=0
 *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C9848f3511de64c83e91208d6da0411d5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=FVByIsAFzHbJtAzQEIFzoCJFGCrcWra0Fs7YXMXaPFI%3D&amp;reserved=0
*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C9848f3511de64c83e91208d6da0411d5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=56YmBrf4KnKEjqfswBWIxstdyic0kOiUFBM43J5Zj24%3D&amp;reserved=0
*** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fforum.eprints.org%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C9848f3511de64c83e91208d6da0411d5%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=2n3z4yQF8qY1aVQOuhWLpb9ey3%2FrfRd6KBvBznaIKoQ%3D&amp;reserved=0

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20190516/b54756fb/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20190516/b54756fb/attachment-0001.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 29112330.jpg
Type: image/jpeg
Size: 15968 bytes
Desc: not available
Url : http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20190516/b54756fb/attachment-0001.jpg