-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Curate Wikidata entries about components of the open science ecosystem #7
Comments
From @Daniel-Mietchen on May 9, 2018 22:48 There is a dedicated Mozsprint project for mapping the open ecosystem (so not limited to science) via Wikidata: mozilla/global-sprint#237 . |
From @HeidiSeibold on May 10, 2018 9:36 How do I make the connection to open science? Can I say "part of" "Open Science Tools"? How do we connect all the tools? I am quite new to wikidata... |
From @HeidiSeibold on May 10, 2018 10:1 I created entries for open science movement and open science tool. Maybe this will help 🤓 Now I can add a tool via: "instance of" "open science tool" (see for example https://www.wikidata.org/wiki/Q52988856) And then we can visualise all tools we collect during this sprint, e.g. with the wikidata-graph-builder |
From @Daniel-Mietchen on May 10, 2018 12:26 Thanks, @HeidiSeibold . I added a bit to these items. For pieces of software and file formats known to Wikidata, Yes, the graph builder and the Wikidata SPARQL endpoint could be used for some visualizations, so it would make sense to start collecting ideas for questions/ queries. An example query not yet directly related to open science is Software applications ranked in descending order by the number of writable file formats . The WikiDigi account on Twitter is tweeting lots of queries like these. |
From @bluerasberry on May 10, 2018 22:4 @HeidiSeibold I tried to develop these also. Yes you did something clever by making these and yes you got the idea of Wikidata. It is still easy to find the limitations of Wikidata's data models. I was looking at your "open science movement" item then cross checked it with other social movements, including women's rights movements, black rights movements, LGBT rights movements, etc. It seems that no one has yet modeled how to manage social movements in Wikidata. Thanks for raising the issue and yes it would be nice at the end to come up with a data visualization. I will try more tomorrow. |
From @Daniel-Mietchen on May 11, 2018 21:3 Here's a graph builder query that @HeidiSeibold had shared this morning for open science tools indexed in Wikidata: https://angryloki.github.io/wikidata-graph-builder/?property=P31&item=Q52990223&mode=reverse . Setting up items for these tools and services is one thing, annotating them with useful properties another. To get an idea of the kind of properties that are being used on items that are instances or subclasses of open science tools, queries like this one could be used: SELECT DISTINCT ?property ?propertyLabel ?count
WITH {
SELECT DISTINCT ?property (COUNT(*) AS ?count) WHERE {
?item wdt:P31/wdt:P279* wd:Q52990223 ;
?p [ ] .
?property a wikibase:Property;
wikibase:claim ?p.
}
GROUP BY ?property
} AS %results WHERE {
INCLUDE %results.
SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }
}
ORDER BY DESC(?count)
LIMIT 100
You can try it out here. The more comprehensive the data, the more useful this query should become. |
From @bluerasberry on May 11, 2018 21:6 I was looking at the Wikidata items for social movements and thinking about how to make sure that anyone who participates in the "open science movement" can tag their work and get due credit for whatever they do, however great or modest. I was looking at citation structures and considering what kinds of work get less credit. Using academic conference presentations as a start, I wrote out a Wikidata data model for data of events. There is more to be developed but this is a start to collecting information about all sorts of events which broadcast information, and might be recorded and published media, but which are currently uncommon to cite. My goal here was to be able to take in conference programs. I am not there but I made some movement on the issue. |
From @Daniel-Mietchen on May 11, 2018 21:10 I guess @fnielsen would like to take a look at that. |
From @Daniel-Mietchen on May 11, 2018 21:59 Having thought a bit more about this, I think instead of classifying tools or services as instances or subclasses of open science tool, it might be better to create a catalog of which the tools or services are a part. |
From @HeidiSeibold on May 15, 2018 14:11 @Daniel-Mietchen I am not sure I understand how to do this. Can you clarify? Has there been any work in this direction so far? |
From @Daniel-Mietchen on May 15, 2018 18:48 @HeidiSeibold Catalogs are in use in various contexts, from artworks and astronomy to zoology, and there is a dedicated property for that: https://www.wikidata.org/wiki/Property:P972 . There is also |
From @Daniel-Mietchen on May 15, 2018 18:48 For some catalogue examples, see https://tools.wmflabs.org/scholia/catalogue/ . |
From @Daniel-Mietchen on May 18, 2018 17:30 We just had a similar discussion here at the Wikimedia Hackathon on how to index such lists of things, and on focus list of Wikimedia project (P5008) came up as an additional and possibly better option than catalogues. |
Linking this issue to the one focused on open science tool mappings and visualizations #11 |
I am not entirely sure what the discussion is about. But since my name was mentioned I can give some pointers. https://github.com/fnielsen/scholia has event and event-series aspects: Individual examples include:
|
From @Daniel-Mietchen on May 1, 2018 12:43
Some guidance is available at
https://www.wikidata.org/wiki/Wikidata:WikiProject_Open .
The focus here is on improving existing items. If you're not sure whether something you're interested in has or, or should have one, please leave a comment here or on the Discussion page of the above WikiProject.
Copied from original issue: OpenScienceRoadmap/mozilla-sprint-2018#7
The text was updated successfully, but these errors were encountered: