EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #07840

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

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

Hi Chris,

I have implemented this but it is still under testing to see how much
it speeds things up.  I will see if I can make this available as a
branch on GitHub at some point.  However, I seem to be already being
two jobs at the moment.  So doing interesting EPrints development
rather than basic additional functionality and bug fixing is a bit of a
luxury time does not afford.

Regards

David Newman

On Thu, 2019-05-16 at 14:25 +0000, Christöpher Gutteridge via Eprints-
tech wrote:
> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Fjesusbagpuss%2Ffbec13d9986fba8e93b56ae5ba34c1&amp;data=01%7C01%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=KtuR5f2iHGmou05PSFBe9gBGPUHysftSpm45fiJq5ZE%3D&amp;reserved=0
> > 64
> >
> > 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: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bou
> > nces@ecs.soton.ac.uk] On Behalf Of martin.braendle--- via Eprints-
> > tech
> > Sent: 16 May 2019 14:36
> > To: John Salter <J.Salter@leeds.ac.uk>
> > Cc: eprints-tech@ecs.soton.ac.uk
> > 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
> >
> > "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>, "eprin
> > ts-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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Forcid.org%2F0000-0002-7752-6567&amp;data=01%7C01%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=qIXKkapxfjls3RlJNIk1jFq6iHzJ1QDRU%2BDWdusCxu0%3D&amp;reserved=0
> > Zentrale Informatik
> > Universität Zürich
> > Stampfenbachstr. 73
> > CH-8006 Zürich
> >
> > "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
> > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Forcid.org%2F0000-0002-8611-8266&amp;data=01%7C01%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=vLP6sDRdshb%2F3OpMWzD48cJZqBB9LpPrVavpjU%2Fw5Tc%3D&amp;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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhiteroselibraries.wordpress.com%2F&amp;data=01%7C01%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=mEzwPMNdtRW%2BHfR0hEaHYAoG6MyRyigmW%2BOlc1aCrVY%3D&amp;reserved=0
> >
> > *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprint
> > s-tech
> > *** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=01%7C01%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=F%2Fr5vbP1R3Z%2BeCgsRZfhzceXQKBRxji3ydSDUbc14Zo%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%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=LuUePIwz0nDo%2FZ%2Bht%2B%2FL7fpym9tj8c7VRIJUQ4r4L1M%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%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=qGNs7NX0iQB%2BHvSZTO8NJIkEZJ4UaCdnTgMuGrxHfRw%3D&amp;reserved=0
> >
> >
> >
> >
> > *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprint
> > s-tech
> > *** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=01%7C01%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=F%2Fr5vbP1R3Z%2BeCgsRZfhzceXQKBRxji3ydSDUbc14Zo%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%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=LuUePIwz0nDo%2FZ%2Bht%2B%2FL7fpym9tj8c7VRIJUQ4r4L1M%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%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=qGNs7NX0iQB%2BHvSZTO8NJIkEZJ4UaCdnTgMuGrxHfRw%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%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=F%2Fr5vbP1R3Z%2BeCgsRZfhzceXQKBRxji3ydSDUbc14Zo%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%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=LuUePIwz0nDo%2FZ%2Bht%2B%2FL7fpym9tj8c7VRIJUQ4r4L1M%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%7C%7C5bace195462f44ce8a3a08d6da0bb925%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=qGNs7NX0iQB%2BHvSZTO8NJIkEZJ4UaCdnTgMuGrxHfRw%3D&amp;reserved=0