Date
Call-in Information
Time: 11:00 am, Eastern Time (New York, GMT-05:00)
To join the online meeting:
- Go to: https://duraspace.zoom.us/j/823948749
- Or iPhone one-tap :
- US: +14086380968,,823948749# or +16468769923,,823948749#
- Or Telephone:
- Dial(for higher quality, dial a number based on your current location):
- US: +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833
- Meeting ID: 823 948 749
- International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5
Slack
- https://vivo-project.slack.com
- Self-register at: https://goo.gl/forms/JxQFkut4TYj4Ehww1
- Self-register at: https://goo.gl/forms/JxQFkut4TYj4Ehww1
Attendees
Indicating note-taker
- Kitio Fofack
- Ralph O'Flinn
- Don Elsborg
- Andrew Woods
- Alex Viggio
- Daniel Mietchen
- Violeta Ilik
- Justin Littman
- Chris Barnes
- John Mark Ockerbloom
- Steve Brown
- Mike Conlon
Agenda
- Brief intro to wikidata and the wikiverse
- Overview of relationship between wikidata/wikicite/wikibase/scholia/wikipedia ( wikiverse as it pertains to semantic data )
- Overview of usages for wikidata
- Overview of wikicite in wikidata
- Internationalization in wikidata ( i18n )
- Overview of semantic capabilities for these tools
- SPARQL query builder - https://query.wikidata.org/
- Brief overview of WD semantics
- Daniel's interest in VIVO
- The matching problem - wikidata has mix-n-match, how would this work in VIVO
- Next steps/actions ( strawman ideas ) Vivo <-> WD ontology mapping
- Publication data as a potential joint project
- Identifying actual sources of data in wikidata - Eg - attribution of the data source
- Usage of triple-pattern-fragment endpoint in VIVO and perhaps wikidata
- Rules for vivo <->
- Attribution
- Data must be CC0
- Country data as a potential joint project - replace FAO data
- Simplify VIVO data
- Timely updates via Wikimedia process
- Potential future projects ( VIVO depth in humanities, grants, advising )
- Publication data as a potential joint project
Notes
Recording
Presentation
https://www.wikidata.org/wiki/Wikidata:WikiProject_Scholia/Talks/Wikidata_and_VIVO_in_2018
Mobile view: https://m.wikidata.org/wiki/Wikidata:WikiProject_Scholia/Talks/Wikidata_and_VIVO_in_2018
Brief intro to wikidata and the wikiverse
- Wikipedia - editable encyclopedia
- Wikidata - editable database
- Vision: “Imagine a world in which every single human being can freely share in the sum of all knowledge.” ( in their native language )
- Mike - in wikis in other languages - are there issues with governments wanting to write a history?
- Daniel - yes, eg wars, battles all have different perspectives. So this also includes individual bias’ from the local authors, editors
- Mike - in wikis in other languages - are there issues with governments wanting to write a history?
- If you setup your own mediawiki page you can add with one line artifacts from wikimedia commons
- media files from Wikimedia Commons can be transcluded into other MediaWiki instances
- Components of architecture: http://wikiba.se/
- What ontologies are used in the wikibase?
- Shared data model
- Ontologies are open
- WikiCite
- Scholia
- Overlapping project with VIVO: Scholia
- Presentation layer for wikidata information for bibliographic data
Overview of semantic capabilities for these tools
Daniel's interest in VIVO
- Open workflows around collaborative curation
- JROST: Interest in sharing roadmaps for open science tooling
- Open scholarly profiles
Next Steps
- Leverage wikidata related to publications
- Use institutional vivos to record position information on wikidata - eg person x was employed at institution from start date to end date
- Use wikidata to help co-author networks - because an institution curates it’s own authors but not authors at other orgs - wikidata can be used for this
- Vivo’s have current employees typically - wikidata can reference scholarly records for people that are no longer employed or deceased.
Identify test cases:
- Content in VIVO vis-a-vis Wikidata
- What workflows could be used to sync between the two?
- Signed statements
- Wikidata statements can be signed as coming from a VIVO authority
- Scholia
- Visualize VIVO conference in Scholia
- For some inspiration, see https://tools.wmflabs.org/scholia/event/Q55117737
- Visualize VIVO conference in Scholia
Actions
Previous Actions
- Don Elsborg to post data property linking pull requests to develop Slack channel.
- Don Elsborg to approach ontology group with additional identifier properties they created for CU instance
- Brian Lowe confirm LDF server issue with TDB content stores
- Mike Conlon to address:
- Don Elsborg to update vagrant for 1.10
- Don Elsborg to investigate rationale for retaining two nearly identical propStatement-dataDefault.ftl files in VIVO and Vitro ( )
- Don Elsborg - add jira tickets for abox/tbox use cases - one ticket for each use case
- Brian Lowe - check with ontology group on handles
- Alex Viggio will bring news of Elasticsearch instead of Solr up with Product Evolution.