The Community ORCID Dashboard is a project to bring together multiple sources of institutional and open data around ORCID iD and rationalise them into one central reporting and visualisation offering
Two endpoints:
- http://63.35.7.234/corda-restler/public/corda/index.php/DemoConnector/connect_eprints
- http://63.35.7.234/corda-restler/public/corda/index.php/DemoConnector/connect_haplo
These will make requests to Haplo and Eprints APIs, and return the JSON of these requests and place them into data/Eprints.json and data/Haplo.json respectively. Use this to get some data up and started for the Downloader methods.
Two endpoints:
- http://63.35.7.234/corda-restler/public/corda/index.php/Downloader/ReturnIDList
- http://63.35.7.234/corda-restler/public/corda/index.php/Downloader/PrintOutput
This endpoint will go through both the data/Haplo.json and data/Eprints.json files in the data directory. If any users have an ORCID, then it will attempt to make a request to the ORCID API to retrieve additional information regarding their employment etc...
Will collect all of this data, and combine it into one large JSON format, then dump it as data/output.json
This endpoint will run through the data/output.json file and convert it into a html table.
Design is currently set up such that there is an endpoint which collects haplo/eprints data, and caches it as a .json locally. There is another endpoint which will collate all of this data into one file, making requests to the ORCID API to supplement the data. There is no merging or deduplication of data whatsoever, which would clearly be desirable. It is possible to look at a user and see whether or not various pieces of data from different systems match.