Esploro
Your feedback matters to us. Help us improve Esploro by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
4 results found
-
ORCID Integration to populate other identifiers
The current Esploro ORCID integration writes the employer to the ORCID. At Southern Cross we have an integration that also pulls the other identifiers from the ORCID record. It would be ideal if the Esploro ORCID integration also wrote the identifiers contained on the ORCID record to Esploro. For example ResearcherID and SCOPUS ID.
Many researchers have linked these identifiers to their ORCID we would like to see them automatically linked via the API to the Esploro Researcher record.34 votes -
OAI_dc output improvements
We would like some improvements to be made to the OAI_dc output file, for example
dc:identifier:
There are a number of identifiers for each record (ISSN, ISBN, DOI, Asset ID, URLs, Esploro URLS (long-type permalink, Viewer, document within viewer) but there is no qualifier to differentiate the identifier/link type
dc:date:
Both published date and conference/event date range appear as dc:date - they can be different years - how do we differentiate?
dc:publisher:
Shows both publisher and country - how to differentiate between the two?
dc:rights:
Includes licence information, copyright statement and internal rights (e.g. open, closed, metadata restricted) - how…
20 votesI didnt hear back from anyone but seems to me like qualified Dublin Core can be the solution.
Tami
-
Expose Researcher Engagement types via API and Analytics
We wanted to start developing a Find a Supervisor page on our web site using the researcher API.
We have entered Principal Supervisor, Co-supervisor etc as engagement types in the backend. However there is no way to query this via the API or Analytics. Also to search the field you need to search the code not the description e.g. Engagement3 not Principal Supervisor.We would like to use the API to have a find a research supervisor page that will query the profiles for researcher interests and return only those reseachers that are approved as research supervisors. The search is…
10 votes -
Create a new Researcher Profile API that returns the Researcher Profile as a complete entity
Please create a new Researcher Profile API that returns the Researcher Profile as a complete entity. That is, it returns the contents of the Overview (including the profile URL), the Output, the Projects, and the Grants(?) tabs.
1) It would be great to have all of this information returned in one API; and
2) You currently have to filter the Assets API by "Shown in profile: Yes" in order to mimic the display in the Researcher Profile; and
3) Projects (and future Grants?) information is not currently available via API.Thanks,
Blake7 votes
- Don't see your idea?