Difference between revisions of "Wikidata Synchronization for the CEUR-WS publishing platform Use-Case of"

From BITPlan ceur-ws Wiki
Jump to navigation Jump to search
 
Line 14: Line 14:
 
Additionally for new proceedings and for the curration of existing once data from the smw wiki needs to be published to wikidata.
 
Additionally for new proceedings and for the curration of existing once data from the smw wiki needs to be published to wikidata.
 
The CEUR-WS browser in our pyCEURmake project aims to introduce such a bidirectional api for edits on wikidata and a smw wiki.
 
The CEUR-WS browser in our pyCEURmake project aims to introduce such a bidirectional api for edits on wikidata and a smw wiki.
 +
<pre>
 +
item given_name P735 firstName
 +
item family_name P734 name
 +
url official_website P856 homepage
 +
id DBLP_author_ID P2456 dblpId
 +
id ORCID P496 orcid
 +
id LinkedIn personal profile ID P634 linkedInId
 +
id GND_ID P227 gndId
 +
id Google_Scholar_author_ID P1960 googleScholarUser
 +
</pre>

Latest revision as of 14:40, 17 October 2022

Semantic Mediawiki and Wikidata are both platforms for knowledge graphs based on the concept of triples. Given this conceptual compatibility a wikidata synchronization is quite straightforward if entities and properties of Wikidata are mapped to the Semantic MediaWiki platform. As part of the effort to synchronize the CEUR-WS metadata with wikidata we have created a prototype for showing how easy it is to synchronize in a three-way style between CEUR-WS, wikidata and a semantic mediawiki. We use scholar profiles as a showcase.

See for example: Tim Berners Lee Scholia entry and Tim-Berners-Lee as Editor of CEUR-WS Volumes

CEUR Workshop Proceedings is a free open-access publication service for academic workshops. Data about the proceedings, events, papers, editors and authors are stored in a semi-structured html format. In a effort to semantify the data and move it into a semantic mediawiki the goal was also to integrate the data into wikidata. Since wikidata is one of the largest knowledge graphs with a large portion covering scholarly articles, adding the ceur-ws data to it increases accessibility and the cross referencing of the contained enties. For the historic records the data needs to be extracted to create the wiki pages and wikidata items. Additionally for new proceedings and for the curration of existing once data from the smw wiki needs to be published to wikidata. The CEUR-WS browser in our pyCEURmake project aims to introduce such a bidirectional api for edits on wikidata and a smw wiki.

item given_name P735 firstName
item family_name P734 name
url official_website P856 homepage
id DBLP_author_ID P2456 dblpId
id ORCID P496 orcid
id LinkedIn personal profile ID P634 linkedInId
id GND_ID P227 gndId
id Google_Scholar_author_ID P1960 googleScholarUser