Wikidata and scientific events #127
Replies: 10 comments 24 replies
-
Hi Simon - welcome! |
Beta Was this translation helpful? Give feedback.
-
I think it is better if we make the links we are using public:
So The excel sheet looks interesting. I am especially happy that your are considering the OpenResearch links. Potentially it would be better if you'd go from on of the 8 OPENRESEARCH copies that we set up because we can clean up data there much more efficiently and effectively than in the legacy production wiki. What cleanups would you need or benefit from? I am especially thinking about the list from https://www.openresearch.org/wiki/PTP_Minimum_viable_dataset
|
Beta Was this translation helpful? Give feedback.
-
Simon at https://or.bitplan.com/index.php/List_of_EventSeries there is a copy of all the data of december 2020 where the title problem seems not to be visible. |
Beta Was this translation helpful? Give feedback.
-
Next step:
We 'd love to try https://www.linguee.com/german-english/translation/rasterfahndung.html - techniques using the https://www.openresearch.org/wiki/PTP_Minimum_viable_dataset signature elements. |
Beta Was this translation helpful? Give feedback.
-
For the event import one of the aspect we are quite interested in is the link to the next upcoming event. I have seen that Microsoft academic supplies this e.g. the next upcoming CVPR is available as an .ics Calendar entry The idea would be that we'll add the CVPR 2021 entry to: As soon as the data on an upcoming event is available. Is there a tool that would trigger us if the next upcoming event is entered in wikidata? At this point i think entering future events in wikidata is a rarely done. Have you seen some examples of future events? |
Beta Was this translation helpful? Give feedback.
-
To proceed, you can align DBLP publications with Wikidata items using external identifiers. One of the ways to do this action is to use Wikidata hub to return the Wikidata item corresponding to DOIs. An example of how this works is https://hub.toolforge.org/P356:10.1016/J.JBI.2019.103292?format=json. As you see here, the result is returned in the JSON Format and can consequently be used in Python bots. You can find attached to this email message a Python code converting a list of DOIs in the plain text format to a list of corresponding Wikidata identifiers. You can adapt this method to include other external identifiers such as ISBN and ISSN. |
Beta Was this translation helpful? Give feedback.
-
@Simon-Cobb - thank you for the OpenRefine Video you let me record in one of the zoom sessions we had. Today we had a project meeting where six member of the team watched the video and discussed how we are going to use OpenRefine for the cleanup of the OPENRESEARCH data. Your input is much appreciated and we decided to try out OpenRefine for the parts of our migration effort where this seems to make sense based on your input. We appreciate your participation in our efforts a lot! |
Beta Was this translation helpful? Give feedback.
-
To better illustrate the usage of mapping to Wikidata you should add links to Scholia, e.g.
I recommend to use Scholia Favicon to link to Scholia. |
Beta Was this translation helpful? Give feedback.
-
Simon for #162 I'd love to have the conference entries for ECIR YYYY and link them to the proceedings. I'd love to start with ECIR 2013 |
Beta Was this translation helpful? Give feedback.
-
@Simon-Cobb today i presented your work in our project meetings see https://rq.bitplan.com/index.php/ConfIDent_Migrationplan/Overview#OpenRefine - i'd love to present part of this also at EMWCon this week. Is that generally o.k. with you? Would you like to participate in presenting? |
Beta Was this translation helpful? Give feedback.
-
New project for scientific events in Wikidata: https://rq.bitplan.com/index.php/WikiData_Scientific_Events
Beta Was this translation helpful? Give feedback.
All reactions