Re: [EP-tech] Antwort: RE: Hyperauthorship

We should have made something long ago which can cache the rendered versions of citations and Export plugins for single items, and invalidated the cache when records are altered or the config is changed... would speed up everything a load.

(Sorry, I sketched the idea years ago and never implemented it)

On 16/05/2019 15:08, John Salter via Eprints-tech wrote:
The database takes a big hit for OAI-PMH requests that include hyper-authored papers.
We have a block of 100 records that contains ~10 ATLAS research papers - each with 3,000+ authors.
This takes a while to generate the XML response (there's *a lot* of nodes that get created).

I've got this EPScript addition to limit the authors in a citation (it's not perfect - I should have used a couple of phrases in there - if I was going to share it formally).
https://gist.github.com/jesusbagpuss/fbec13d9986fba8e93b56ae5ba34c164<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Fjesusbagpuss%2Ffbec13d9986fba8e93b56ae5ba34c164&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=WXoXXScPyfe7eLVtCGvua3f84f3JiOnX2rMCw9HeY9U%3D&reserved=0>

On our summary page we also have the full author list displayed.
For us, the issue we're concerned about is that when we have a paper with loads of authors, if someone editing the item visits a workflow stage with the authors on it, it takes *ages* to do anything.

Our repo staff want to retain the complete author list - so I'll continue looking down the 'improved input methods' path rather than 'truncate from source' option.

Cheers,
John

From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of martin.braendle--- via Eprints-tech
Sent: 16 May 2019 14:36
To: John Salter <[email protected]><mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: [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" <[email protected]<mailto:[email protected]>>
An: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
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: [email protected]<mailto:[email protected]> [mailto:[email protected]]
Sent: 16 May 2019 13:22
To: [email protected]<mailto:[email protected]>; John Salter <[email protected]<mailto:[email protected]>>
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<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Forcid.org%2F0000-0002-7752-6567&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=CWPsWBeUqFRkv34GIezkxMT0DxmZ5xrOotrtreOW6Tk%3D&reserved=0>
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" <[email protected]<mailto:[email protected]>>
An: "'[email protected]'"<mailto:'[email protected]'> <[email protected]<mailto:[email protected]>>
Datum: 16.05.2019 14:00
Betreff: [EP-tech] Hyperauthorship
Gesendet von: <[email protected]<mailto:[email protected]>>

________________________________




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<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Forcid.org%2F0000-0002-8611-8266&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=ZiektqJssCwepp5tcJk8mIvB5LuBO2FyCnFVLKz8eQo%3D&reserved=0>

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/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhiteroselibraries.wordpress.com%2F&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Pn16LPHC43zJkrbNWvymKHHcEmK4BhF4%2Fc1LA3Aj9A4%3D&reserved=0>
[WRL_email_signature_thelmas_]
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Om%2Fxu1lSg5dezNb4n8gvqoaFZdWSDE%2B0UxcDiw7emFE%3D&reserved=0>
*** EPrints community wiki: http://wiki.eprints.org/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=f2KUeAX9cg%2BNJojwg42QW7dv0RX7NS9KOSms8cUj%2FnU%3D&reserved=0>
*** EPrints developers Forum: http://forum.eprints.org/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fforum.eprints.org%2F&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=5CmncO7nVmMNzNPF3MrQfaj92NfIcBmfS%2BS%2BvKxzG3E%3D&reserved=0>




*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Om%2Fxu1lSg5dezNb4n8gvqoaFZdWSDE%2B0UxcDiw7emFE%3D&reserved=0>
*** EPrints community wiki: http://wiki.eprints.org/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=f2KUeAX9cg%2BNJojwg42QW7dv0RX7NS9KOSms8cUj%2FnU%3D&reserved=0>
*** EPrints developers Forum: http://forum.eprints.org/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fforum.eprints.org%2F&data=01%7C01%7C%7C9757061df5374473d29408d6da0a5e35%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=5CmncO7nVmMNzNPF3MrQfaj92NfIcBmfS%2BS%2BvKxzG3E%3D&reserved=0>

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