Hi Mariette and others,
That is true as of now but Pure APIs are likely to change a lot in the next year. We provided a set of recommendations based on the work we did here in the UK Pure User Group and with support from many international groups. I am glad to
see most of the recommendations have been accepted by Elsevier in their roadmap for APIs. I will continue to pester them about two way APIs as that was also a recommendation from our side.
This discussion is quite useful at this time as we are now coming to the stage where Pure for datasets storage is no longer an attractive option for us. Previously, for a quick deployment and familiarity reasons it was, but as our data
becomes complex, the cracks start showing up more and more.
Best wishes,
Masud
--
Masud Khokhar
Head of Digital Innovation
The Library, Lancaster University
LA1 4YH, Lancaster, United Kingdom
Tel: +44 (0)1524 5-94236 | Email: [log in to unmask] | Twitter: @mkhokhar
From: "[log in to unmask]" <[log in to unmask]> on behalf of "Selm, Mariëtte van" <[log in to unmask]>
Reply-To: "[log in to unmask]" <[log in to unmask]>
Date: Thursday, 11 August 2016 at 13:33
To: "[log in to unmask]" <[log in to unmask]>
Subject: Re: Pure as a research data calalogue and or repository
Hi Robin,
Since I’m managing our figshare implementation, but am not involved in our Pure project and am not very well versed in API technology, I’m on somewhat thin ice here – but here goes: it’s my understanding that
the Pure API doesn’t adequately support connections to import data from other systems, but is able to handle xml files that are uploaded to Pure. That means we’ll have our instance of figshare for institutions produce xml files containing the metadata of datasets
that need to be registered in Pure, and upload those to Pure. Figshare has already confirmed to us that they’re able to provide these xml files.
Best,
Mariëtte
From: Research Data Management discussion list [mailto:[log in to unmask]]
On Behalf Of RICE Robin
Sent: donderdag 11 augustus 2016 14:08
To: [log in to unmask]
Subject: Re: Pure as a research data calalogue and or repository
Hi Mariëtte,
Before going off list, I’d be really interested to know how you expect to export records from the data repository to import them into Pure? Has that been
worked out yet, or just on the to-do list? I ask because we have found that there is a serious limitation of the interoperability of Pure that does not allow batch import of metadata, either via a standard or an API.
There is a workaround I continue to hope for – if the company would implement the DataCite API, such that one could enter a DOI and have it automatically fill in the minimum DataCite metadata fields,
picking up the info from DataCite, the way it does for PubMed records. Then, although still not batch, it would make entering one record at a time much easier. It has implemented the DataCite API for purposes of minting DOIs but not for this purpose. This
continues to be a major bugbear of mine, so would be thrilled to know someone has found a solution, if so.
(I already mentioned to Laurence that we use Pure for our data asset register although we have DataShare for our institutional data repository.)
Cheers,
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Robin Rice
Data Librarian
EDINA and Data Library
University of Edinburgh
@sparrowbarley (twitter)
#RDMSmooc -
www.coursera.org/learn/data-management
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
From: Research Data Management discussion list [mailto:[log in to unmask]]
On Behalf Of Selm, Mariëtte van
Sent: 11 August 2016 12:39
To: [log in to unmask]
Subject: Re: Pure as a research data calalogue and or repository
Hi Laurence,
By the end of this year we’ll hopefully have three systems in place at the University of Amsterdam:
-
Pure will succeed Metis as our Current Research Information System (CRIS),
-
Digital academic repository UvA-DARE, a Fedora-based solution, will remain our publications repository, and
-
Figshare for institutions will become available as our research data repository
Researchers now upload publications (preprints etc.) to UvA-DARE via Metis. As soon as Pure replaces Metis, the upload process will be routed via Pure.
With regard to research data, we’ll be doing things sort of ‘the other way around’: researchers will upload their data to our instance of figshare for institutions and provide metadata; the metadata of
published datasets will be exported to Pure to register these datasets as research outputs.
At the moment it’s our priority to get Pure and figshare each up and running and available to researchers. Next calendar year we hope to implement a connection between figshare and Pure.
Feel free to drop me a line off-list, I’ll be more than happy to forward any questions you may have to my colleagues who are working on the implementation of Pure.
Best,
Mariëtte
Mariëtte van Selm
Information specialist & Research Data Management Support coordinator
University of Amsterdam
University Library | Information Services
P.O. Box 19185 | 1000 GD Amsterdam
Singel 425 | 1012 WP Amsterdam
T +31 (0)20 525 2126 | E
[log in to unmask]
http://nl.linkedin.com/in/mvanselm/
From: Research Data Management discussion list [mailto:[log in to unmask]]
On Behalf Of Horton,L
Sent: donderdag 11 augustus 2016 12:17
To: [log in to unmask]
Subject: Pure as a research data calalogue and or repository
Hello,
Is anyone using Pure as a research data catalogue and/or repository? I’m looking for some guidance shaped by experience or for anyone considering using it.
Laurence Horton
LSE Library
Houghton Street
London WC2A 2HD
Tel: +44 (0)20 7955 6072
Email:
[log in to unmask]
LSE Research Data Management Support Service