Dear all,
Let me reply on behalf of CORE (I will only comment on the issues relevant to aggregations and CORE in general and will not discuss the raised spamming issue of ResearchGate). I have divided my response to a few sections hopefully answering all questions raised. As the answer might seem to long and I wanted to format it, you will find it at https://www.evernote.com/shard/s72/sh/be4b4de0-6423-4237-87c2-b4e20bcb1cd7/277c6dd0cff48779401bca3212d4d6b0
Overall, I would like to very clearly say for the CORE team that we are here to work hand in hand with the repository community. We take the view that aggregations should support repositories and we strongly feel this is precisely what we are doing. CORE aims to primarily provide services that individual repositories cannot provide. Some of the use cases CORE serves have been discussed with and provided to UK RepositoriesNet+ as part of the requirements-gathering for UK aggregation services effort. To read more about them, please see: http://core-project.kmi.open.ac.uk/files/jcdl2013_v7.pdf . CORE aims to support not only those who search for individual publications, but also those who need programmable (API) access to publications and those who run repositories. In the future, we also see the potential of using CORE for checking compliance and providing funder information. CORE already provides faceted search and this can be extended to funder information when repositories make it available.
I don't think you should be worried that ResearchGate (or other commercial tools) would replace repositories. Repositories have become a central and essential component of the infrastructure of universities and they serve many different purposes which can hardly be replaced by a single commercial tool.
Kind regards,
Petr Knoth
Knowledge Media institute
The Open University
|