EPrints Technical Mailing List Archive

Message: #03801

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

[EP-tech] Re: ORCiD

Hi,
This looks good to me too.
The reason I asked this question in the first place was to see if there was any sensible things going on (this looks very sensible to me), and so I didn't reinvent the wheel.

Should we target v3.4 or v4.0?
How does this fit in with anything else that people are trying to do?

Good work for being very ahead-of-the-game on this!
Cheers,
John

 
-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Gilles Fournié
Sent: 19 January 2015 07:32
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: ORCiD


+1 too

We are still in the process of migrating to EPrints and being able to 
manage authors and author instances was very important for us.

Matthew and USQ were kind enough to let us use their author system and 
it saved us a lot of work and time.

It would really be great that this system could be integrated in EPrints 
and maintained by the community for future versions of the software..

Regards
GF

Le 18/01/2015 23:38, Matthew Brady a écrit :
>
> Hi Ian, everyone else..
>
> We have our system with 2 extra datasets (Author and Author Instance)
>
> The author contains everything about the person including 1 to many 
> identifiers. (google scholarID, scopusAuthorID, ORCiD, etc etc etc....)
>
> The author instance contains a link to a point in time, their 
> affiliation with institutions/dept etc etc
>
> The instance ID is then stored in the vanilla creator_id field.
>
> This allows a single unique author to be displayed, along with all 
> their cited versions of their name, so the citations render correctly, 
> and still get assigned to the correct person.
>
> (Example image also displays the statistics icon, which links to that 
> authors stats page. – from https://eprints.usq.edu.au/view/uniqueauthor/ )
>
> I have tried to get this pushed into the ePrints Core, but Seb hasn’t 
> got back in touch about who to send it to.
>
> I would like it incorporated into the base product, so we all have the 
> same version, rather than a dozen or more splintered versions of code 
> all trying to do the same thing.  This will make the support on this 
> email list more fruitful, if we are all on the same page.
>
> If anyone knows who is maintaining the base ePrints codebase these 
> days, let me know and I will forward on the .zip file of all the code 
> we have for inclusion into the base product.
>
> Cheers
>
> Matt
>
> -----Original Message-----
> From: eprints-tech-bounces@ecs.soton.ac.uk 
> [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Ian Stuart
> Sent: Saturday, 17 January 2015 2:01 AM
> To: eprints-tech@ecs.soton.ac.uk
> Subject: [EP-tech] Re: ORCiD
>
> On 16/01/15 14:09, John Salter wrote:
>
> > Hi, How is anyone storing an ORCiD in EPrints?
>
> >
>
> > Out-of-the-box, EPrints has creators with a name component, and an id
>
> > component. The default name of this field is 'Email':
>
> > https://github.com/eprints/eprints/blob/3.3/lib/lang/en/phrases/system
>
> > .xml#L396
>
> >
>
> >  I was thinking or using it to store the ORCiD instead of the email
>
> > address, but didn't know if any 'best practice' was emerging yet?
>
> Like lots of people have already said, I've just added an extra field 
> to "creator" however Martin's point is well made: authors are not 
> normalised across records - meaning the same [identical] name is 
> listed for each record it appears in.
>
> This is, perhaps, something to feed into the EPrints 3.4 or 4.0 roadmap?
>
> -- 
>
> Ian Stuart.
>
> Developer: ORI, RJ-Broker, and OpenDepot.org Bibliographics and 
> Multimedia Service Delivery team, EDINA, The University of Edinburgh.
>
> http://edina.ac.uk/
>
> This email was sent via the University of Edinburgh.
>
> The University of Edinburgh is a charitable body, registered in 
> Scotland, with registration number SC005336.
>
> *** 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/
>
> _____________________________________________________________
> This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email.
>
> The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt.
>
> The University of Southern Queensland is a registered provider of education with the Australian Government.
> (CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081 )
>
>
> *** 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/


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