EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #07893
< 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
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, Christöpher Gutteridge <totl@soton.ac.uk>
- Subject: Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: "Newman D.R." <drn@ecs.soton.ac.uk>
- Date: Fri, 21 Jun 2019 16:35:33 +0000
Hi Chris,
I have made the changes you suggested and they seem to be working will push back to GitHub once I have had a chance to fully review them. I have added something to perl_lib/EPrints/Citation/EPC.pm that looks out for the start of a citation that looks
like this:
<cite:citation xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://eprints.org/ep3/control" xmlns:cite=""
cite:disable-caching="yes">
This is very much like the code already present that looks for trim-whitespace.
Regards
David Newman
On Wed, 2019-06-05 at 10:20 +0000, Newman D.R. via Eprints-tech wrote:
Hi Chris,
If it is preloaded this is less of an issue, I will have a look to seehow such a variable could be stored as part of this preload.
Regards
David Newman
On Wed, 2019-06-05 at 10:44 +0100, Christöpher Gutteridge wrote:
Citation XML files are loaded in advance, so that's not an issue:
https://eur03.safelinks.protection.outlook.com/?url="">hub.com%2Feprints%2Feprints%2Fblob%2F3.3%2Fperl_lib%2FEPrints%2FRepository.pm%23L260&data="">684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=hDezkbYKSdim%2FgKrTv%2BUtxByE%2BX9OWaIKBDde9t9Cr4%3D&reserved=0
You'd need to detect the flag inhttps://eur03.safelinks.protection.outlook.com/?url="">hub.com%2Feprints%2Feprints%2Fblob%2F3.3%2Fperl_lib%2FEPrints%2FRepository.pm%23L1001&data="">3684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=5rTcT9srOgaFIypGq1GUj1Y6yja0MxQ6dfckenju7ww%3D&reserved=0somehow.
I know it feels easier to put the "no cache" config elsewhere but itreally should be part of the citation file itself.
On 05/06/2019 10:21, Newman D.R. wrote:
Hi Chris,
From a repository admin's point of view I can see this being theeasiest and probably most obvious way of stating it should not becached. I am just not sure how much of an impact there would behavingto load the citation file each time before making a decision.Maybethere is something that caches this periodically (i.e. at the startofwhen generate_views runs and when EPrints is reloaded in Apache).
Regards
David Newman
On Fri, 2019-05-31 at 13:46 +0100, Christöpher Gutteridge wrote:
I would suggest that the exception should be added to thecitationfile.The issue.xml citation is part of /lib/ so can easily be modifiedinanupgrade, which was why that was designed that way.
On 31/05/2019 13:02, Newman D.R. wrote:
Hi Chris,
Thanks for the info. I will look into it. I was certainlythinkingthat citation.pl should probably be called citation_caching.pl.
Contextual citations may be an interesting edge case to dealwith.Isthis something that is likely will be present for all modernrepositories or just the odd few? I can add an exceptions listbasedon DataObj type and citation name (e.g. user, eprint, etc. anddefault,brief, etc.).
Regards
David Newman
On Fri, 2019-05-31 at 12:08 +0100, Christöpher Gutteridgewrote:
I would suggest maybe calling it CitationCache to make itlessconfusingas much of the documentation uses "citation" to refer to thecitationconfiguration files.
I seem to recall from when I looked into this years ago thatthere'safew citations that should not be cached as they havecontextualinformation. eg.https://eur03.safelinks.protection.outlook.com/?url="">2F%2Fgithub.com%2Feprints%2Feprints%2Fblob%2F3.3%2Flib%2Fcitations%2Feprint%2Fissue.xml&data="">6450f41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=VehZmkq%2BhGtlV2BoXyoF3Y9hn2zyBc0ki%2FcLJVyYCsA%3D&reserved=0
On 31/05/2019 12:01, Newman D.R. wrote:
Hi all,
As promised here is the code that I wrote for citationcaching:
https://eur03.safelinks.protection.outlook.com/?url="">A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Fcommit%2F6aedd1c2b1ba4ce68fceb5cda5&data="">41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=dIoNVArFilGXLssfRvSqnwCLQcA7Jfc43o9I98shzGw%3D&reserved=0c16545a72b9d53
You need to copy default_zero/cfg.d/citations.pl to yourlocalarchiveand set enabled to 1. You then need to run epadmin updatetocreatethe Citation dataset.
I have found that on large browse view listing (e.g. 400-500)ifthecitations are already cached I get an improvement from a 6secondloadtime to 2 seconds. However, if the citations need cachingbeforethebrowse view can be generated then the first load time is 10seconds.However, this will be a one off unless you run therefresh_citationsepadmin command that works like refresh_abstracts but forcitations.
Please feel free to try out and ask any questions. I havedonesomebasic testing on it but I think it is a little way ofdeployinginaproduction environment. I would want to be confident thatcitationsare always cleared when an EPrints is modified, whichshouldalwaysbethe case but might be susceptible to race conditions wherethecache isnot cleared in time and the old cached citation is usedratherthangenerating a new one.
Regards
David Newman
On Thu, 2019-05-16 at 14:35 +0000, Newman D.R. via Eprints-techwrote:
Hi Chris,
I have implemented this but it is still under testing toseehowmuchit speeds things up. I will see if I can make thisavailableasabranch on GitHub at some point. However, I seem to bealreadybeingtwo jobs at the moment. So doing interesting EPrintsdevelopmentrather than basic additional functionality and bug fixingisabit ofaluxury time does not afford.
Regards
David Newman
On Thu, 2019-05-16 at 14:25 +0000, Christöpher GutteridgeviaEprints-tech wrote:
We should have made something long ago which can cachetherenderedversions of citations and Export plugins for singleitems,andinvalidated the cache when records are altered or theconfig ischanged... would speed up everything a load.(Sorry, I sketched the idea years ago and neverimplementedit)On 16/05/2019 15:08, John Salter via Eprints-techwrote:
The database takes a big hit for OAI-PMH requeststhatincludehyper-authored papers.We have a block of 100 records that contains ~10ATLASresearchpapers - each with 3,000+ authors.This takes a while to generate the XML response(there's*alot*ofnodes that get created).
I've got this EPScript addition to limit the authorsin acitation(it's not perfect - I should have used a couple ofphrases inthere- if I was going to share it formally).https://eur03.safelinks.protection.outlook.com/?url="">ttps%3A%2F%2Fgist.github.com%2Fjesusbagpuss%2Ffbec13d9986fba8e93b56ae5ba34c1&data="">f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=l7wL8BnRgf8EA7E3SxuGBraA1Y%2BjALC8VfrCLI2H4Mc%3D&reserved=064
On our summary page we also have the full author listdisplayed.For us, the issue we're concerned about is that whenwehaveapaper with loads of authors, if someone editing theitemvisits aworkflow stage with the authors on it, it takes*ages* todoanything.
Our repo staff want to retain the complete authorlist -soI'llcontinue looking down the 'improved input methods'pathratherthan'truncate from source' option.
Cheers,John
[mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of martin.braendle---viaEprints-techSent: 16 May 2019 14:36To: John Salter <J.Salter@leeds.ac.uk>Subject: [EP-tech] Antwort: RE: Hyperauthorship
Hi,
we thought of limiting the rendering, too. However,inthatcase,the database has to deliver the author records beforethelimitisapplied, which involves a performance penalty. Anyonewhohadtodeal with a 2000 author item in EPrints can tell whatthis islike.That's why we decided to limit on input already.
Cheers,
Martin
"John Salter" ---16.05.2019 14:36:13---Hi Martin,Interestingapproach. The records I'm, looking at all come viaSymplecticorPure - 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:36Betreff: RE: [EP-tech] Hyperauthorship
Hi Martin,Interesting approach. The records I'm, looking at allcomeviaSymplectic or Pure - and we could implement some formoflimit tothe number of authors - and retain any that are'resolved'(local)authors.
I was thinking of changing the default inputrenderingforthecreator field along these lines:If there are < LIMIT authors, render input ascurrentlyexistsIf there are > LIMIT authors, render a static list ofthem,andenhance with _javascript_ to allow editing of specificentries/re-ordering / searching filtering the list.
This could even be deployed as a separate workflowstage(whichonly appears when there are > LIMIT authors).
I'll have to see what people here think aboutlimitingtheauthorlist on the way in to EPrints - that sounds like abetterplacetobe…
Cheers,John
From: martin.braendle@id.uzh.ch [mailto:martin.braendd.uzh.ch]Sent: 16 May 2019 13:22To: eprints-tech@ecs.soton.ac.uk; John Salter <J.Salteeds.ac.uk
Subject: Re: [EP-tech] Hyperauthorship
Hi John,
we have a lot of high energy physics or biomedicalarticleswithhundreds or thousands of authors. Usually, those aresubmittedviaCrossRef or PubMed import.
We have adapted the corresponding import plugins tolimitthenumber of authors by a configurable limit (in ourcase30).Ifthelimit is exceeded, "et al" is added asthe ($limit+1)thauthor,the remaining authors are not imported and a warningmessageisissued. Submitters are then still free to add theremainingUZHauthors manually and use et al for authors outside ofUZH.
Instead of the DOI plugin, we have developed aCrossRefpluginthatuses the CrossRef REST API . It implements the authorlimitationaswell. We decided to go with the CrossRef REST APIbecausefunderinformation can be imported from there.
Best regards,
Martin
--Dr. Martin Brändlehttps://eur03.safelinks.protection.outlook.com/?url="">ttps%3A%2F%2Forcid.org%2F0000-0002-7752-6567&data="">c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=VC8Bwg2BLpo%2BybPatYVIyBvALgwZhIZ4Az4bBUkKXFY%3D&reserved=0Zentrale InformatikUniversität ZürichStampfenbachstr. 73CH-8006 Zürich
"John Salter via Eprints-tech" ---16.05.201914:00:41---Hi,Hasanyone done any work on making the EPrints workflow abitmoresensible when a paper has man
Von: "John Salter via Eprints-tech" <eprints-tech@ecs.soton.ac.ukAn: "'eprints-tech@ecs.soton.ac.uk'" <eprints-tech@ecs.soton.ac.uk>Datum: 16.05.2019 14:00Betreff: [EP-tech] HyperauthorshipGesendet von: <eprints-tech-bounces@ecs.soton.ac.uk>
Hi,Has anyone done any work on making the EPrintsworkflow abitmoresensible when a paper has many authors (hundreds orthousands)?
Cheers,John
John Salterhttps://eur03.safelinks.protection.outlook.com/?url="">ttp%3A%2F%2Forcid.org%2F0000-0002-8611-8266&data="">c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=kjC4zZaCbC3FpYg53MlgUmfkiuWdpysY7o4wYMO7noU%3D&reserved=0
White Rose Libraries Technical OfficerIT - Application Support (Research)10.23B, IT Services BuildingUniversity of LeedsLeedsLS2 9JT0113 34 37385
Online: https://eur03.safelinks.protection.outlook.com/?url="">m/?url=https%3A%2F%2Fwhiteroselibraries.wordpress.com%2F&data=01%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=9lS51avRu3EUOP9947XrlKQmJfQf3KMbb1AuJ87BYuw%3D&reserved=0
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech*** Archive: https://eur03.safelinks.protection.outlook.com/?url="">ok.com/?url="">outlook.c&data="">47cbfa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=41%2FsVuVsPGj%2F5wq9FO4tCmGjDGB%2Fvucv4gH1XZMf6TA%3D&reserved=0om/?url="">http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data="">1%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=3dwAZ3WMVCcJQSfKyX%2FCHM%2BAREOusIkcEIjkf969tzk%3D&reserved=0*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">rotection.outlook.com/?url="">nks.prote&data="">47cbfa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=YOjwOPs5LSPmXRTEL4RWHSPSOmk7ekNam4sBakyJ%2BcQ%3D&reserved=0ction.outlook.com/?url="">protectio&data="">94b094b446d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=vejeI7yFuexWLqdWmqiZWKkvLJLFCyLM8aLsmiPwm9c%3D&reserved=0n.outlook.com/?url="">ection.ou&data="">450f41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata="">mp;reserved=0tlook.com/?url="">ata=01%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=bAAmMyyLM3BKMyaJKV0%2BlVkjLTLheWtP7AMKx2OXs14%3D&reserved=0*** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url="">.protection.outlook.com/?url="">links.pro&data="">47cbfa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=kaRCtSCHFP9rPA9w4%2BRraTwYQagKcaODmyCvMR7lGNo%3D&reserved=0tection.outlook.com/?url="">s.protect&data="">94b094b446d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=QTDjs7Rr47sZGJsiRYyPAPyUv9eTkeerHKVQmiIlNo0%3D&reserved=0ion.outlook.com/?url="">otection&data="">50f41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=p4cXCPhQxSBU%2Fef%2B31riVpDuQnjpnY%2B7MAkMDpHiItw%3D&reserved=0.outlook.com/?url="">p;data=01%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=x1u8ms27jNFOjBeMVmcvFZ6gli%2BMlgw3bd%2Bd7PMyATg%3D&reserved=0
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech*** Archive: https://eur03.safelinks.protection.outlook.com/?url="">ok.com/?url="">outlook.c&data="">47cbfa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=41%2FsVuVsPGj%2F5wq9FO4tCmGjDGB%2Fvucv4gH1XZMf6TA%3D&reserved=0om/?url="">http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data="">1%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=3dwAZ3WMVCcJQSfKyX%2FCHM%2BAREOusIkcEIjkf969tzk%3D&reserved=0*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">rotection.outlook.com/?url="">nks.prote&data="">47cbfa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=YOjwOPs5LSPmXRTEL4RWHSPSOmk7ekNam4sBakyJ%2BcQ%3D&reserved=0ction.outlook.com/?url="">protectio&data="">94b094b446d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=vejeI7yFuexWLqdWmqiZWKkvLJLFCyLM8aLsmiPwm9c%3D&reserved=0n.outlook.com/?url="">ection.ou&data="">450f41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata="">mp;reserved=0tlook.com/?url="">ata=01%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=bAAmMyyLM3BKMyaJKV0%2BlVkjLTLheWtP7AMKx2OXs14%3D&reserved=0*** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url="">.protection.outlook.com/?url="">links.pro&data="">47cbfa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=kaRCtSCHFP9rPA9w4%2BRraTwYQagKcaODmyCvMR7lGNo%3D&reserved=0tection.outlook.com/?url="">s.protect&data="">94b094b446d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=QTDjs7Rr47sZGJsiRYyPAPyUv9eTkeerHKVQmiIlNo0%3D&reserved=0ion.outlook.com/?url="">otection&data="">50f41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=p4cXCPhQxSBU%2Fef%2B31riVpDuQnjpnY%2B7MAkMDpHiItw%3D&reserved=0.outlook.com/?url="">p;data=01%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=x1u8ms27jNFOjBeMVmcvFZ6gli%2BMlgw3bd%2Bd7PMyATg%3D&reserved=0*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech*** Archive: https://eur03.safelinks.protection.outlook.com/?url="">.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data="">01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=3dwAZ3WMVCcJQSfKyX%2FCHM%2BAREOusIkcEIjkf969tzk%3D&reserved=0*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">tection.outlook.com/?url="">protect&data="">fa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=%2Bx1o%2BajKYMnC2ytfdtvhJ1F1o5BXkqVqE16G1fsO16w%3D&reserved=0ion.outlook.com/?url="">ection&data="">4b446d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=70IPOqsuLpIeGNKZyd4EqJ8eJ%2FV%2FNCzOpZYDBjQ3pvE%3D&reserved=0.outlook.com/?url="">on.outl&data="">41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Tu8NjmmoI0nGkhe3Nf9HtX%2FjcbJv704p30RbHNn4%2FnE%3D&reserved=0ook.com/?url="">01%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=bAAmMyyLM3BKMyaJKV0%2BlVkjLTLheWtP7AMKx2OXs14%3D&reserved=0*** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url="">rotection.outlook.com/?url="">s.prote&data="">fa6d63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=YOjwOPs5LSPmXRTEL4RWHSPSOmk7ekNam4sBakyJ%2BcQ%3D&reserved=0ction.outlook.com/?url="">otectio&data="">94b446d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=vejeI7yFuexWLqdWmqiZWKkvLJLFCyLM8aLsmiPwm9c%3D&reserved=0n.outlook.com/?url="">tion.ou&data="">41b7810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Q1OD0nvtS8fKBXdR0pTR0GRUwFFsNQOofpClgDPPkBE%3D&reserved=0tlook.com/?url="">ta=01%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=x1u8ms27jNFOjBeMVmcvFZ6gli%2BMlgw3bd%2Bd7PMyATg%3D&reserved=0*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech*** Archive: https://eur03.safelinks.protection.outlook.com/?url="">om/?url="">http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data="">Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=3dwAZ3WMVCcJQSfKyX%2FCHM%2BAREOusIkcEIjkf969tzk%3D&reserved=0*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">ction.outlook.com/?url="">ectio&data="">63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=BwmFxHmkDiQk%2BpWImuZ05fF46xBrsoSlA%2BqF5%2BhlIOA%3D&reserved=0n.outlook.com/?url="">on.ou&data="">46d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata="">3D&reserved=0tlook.com/?url="">utloo&data="">810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=IyDVijHsZSMIIWtFVZa%2FisKla8z8DYwclqSJIc3yyRY%3D&reserved=0k.com/?url="">C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=bAAmMyyLM3BKMyaJKV0%2BlVkjLTLheWtP7AMKx2OXs14%3D&reserved=0*** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url="">tection.outlook.com/?url="">otect&data="">63684db04f2f08d6e99a710b%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=%2Bx1o%2BajKYMnC2ytfdtvhJ1F1o5BXkqVqE16G1fsO16w%3D&reserved=0ion.outlook.com/?url="">tion&data="">6d7c72e08d6e5c5fff2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=70IPOqsuLpIeGNKZyd4EqJ8eJ%2FV%2FNCzOpZYDBjQ3pvE%3D&reserved=0.outlook.com/?url="">.outl&data="">810a08d6e5b85b53%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=Tu8NjmmoI0nGkhe3Nf9HtX%2FjcbJv704p30RbHNn4%2FnE%3D&reserved=0ook.com/?url="">1%7C01%7Cdrn%40ecs.soton.ac.uk%7C17a35c5698f24685c2b408d6da0bc70f%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=x1u8ms27jNFOjBeMVmcvFZ6gli%2BMlgw3bd%2Bd7PMyATg%3D&reserved=0*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech*** Archive: https://eur03.safelinks.protection.outlook.com/?url="">*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">*** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url="">
- References:
- [EP-tech] Hyperauthorship
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: Christöpher Gutteridge <totl@soton.ac.uk>
- Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: "Newman D.R." <drn@ecs.soton.ac.uk>
- Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: Christöpher Gutteridge <totl@soton.ac.uk>
- Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: Christöpher Gutteridge <totl@soton.ac.uk>
- Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: Christöpher Gutteridge <totl@soton.ac.uk>
- Re: [EP-tech] Antwort: RE: Hyperauthorship
- From: "Newman D.R." <drn@ecs.soton.ac.uk>
- Prev by Date: Re: [EP-tech] WINSCP error File disappeared/0KB
- Next by Date: [EP-tech] Question regarding time out and document type
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):