Research Object Components and Services in Earth Sciences

Find more relevant research objects and structure them through semantic intelligence.

Developed for the European Virtual Research Environment in Earth Sciences (EVER-EST). More information available here

Scholarly Communication Services


In EVEREST research objects released or archived can be assigned a Digital Object Identifier (DOI). DOIs can be used to track research objects in scholarly search services so that citation information can be extracted and added to the research object as a measure of the research object impact in scholarly communications. The idea is to harvest research object citation information from Google Scholar and Microsoft Academic, which are specialized sites that gather citation information of research works in scholarly communications. Two different rest web services have been developed, one for each scholar service. Note that the DOI functionality is new and currently there are not research objects with DOIs. Therefore in the current implementation the web services receive as input parameter the title of the research object and return the number of cites for publications with the same title. In a second implementation a new input parameter for the DOI associated with the research object will be added. For a complete description of these services the reader is referred to deliverable D4.3 section 5.3.



Recommender API

Google scholar and Microsoft academics harvesters of citation information are implemented as rest services. Both services expects the title of the research object as a path parameter and the citation information is provided in the format that the source services, i.e., Google scholar and Microsoft academics, generate it.


http://everest.expertsystemlab.com/scholar/gscholars/write-title-here
http://everest.expertsystemlab.com/scholar/msacademics/write-title-here

One important consideration is that Google Scholar service is limited regarding the number of request per period of time allowed before being banned by the service. Therefore the corresponding service is constrained to a delay of 1 second between every request.