Wikibase Community User Group/Meetings/2024-04-25
Online meeting of the Wikibase Community User Group.
Schedule
edit- 15:00 UTC (17:00 Berlin), 1 hour, Thursday 25th April 2024
- Online meeting: https://meet.jit.si/WikibaseLiveSession
- Notes on Etherpad
Participants
edit- Jon Amar (WMDE)
- Laurence 'GreenReaper' Parry (WBUG / WikiFur.com)
- Elwin Huaman (Qichwabase)
- Tom (WMDE)
- TuukkaH
- David Lindemann
Agenda
edit- Organisational
- OPEN CALL proposals by WBUG and Wikibase Stakeholder Group.
- Laurence: presenting the proposals
- Integrating form-based entity creation using Shape Expressions into the Wikibase UI (GreenReaper) - as submitted on the official form
- Elwin: "The power of Wikibase is in its extensions" (supporting Cradle as extension)
- Improved reconciliation support for Wikibase instances via dedicated extension supporting better OpenRefine integration and replacing the existing Python reconciliation service. (Lozana)
- Integrating form-based entity creation using Shape Expressions into the Wikibase UI (GreenReaper) - as submitted on the official form
- let's look into scenarios as in what might happen if we get one or both of them
- Laurence: presenting the proposals
- Wikibase Suite
- Suite 2023 Survey is on Commons! Let us know what you think :)
- Open question: why choose Wikibase (Cloud or Suite) instead of Wikidata as a home for your data/knowledge?
- Laurence: Notability can indeed be a factor in people finding a home for their data. Example of user getting pushback re an artist meeting notability bar. Just the emotional drag alone can be quite a stressor and barrier to entry to contributing to knowledge of humanity. Often times gaps in references can be an issue (some groups avoid the media, others are just not covered). And the question of whether of something is notable within a topic area or subcommunity.
- Does provision of alternatives provide excuse/permission to push people out
- Is there a subculture of more restrictive interpretation of notability requirements than are explicitly stated in the guidelines?
- Are people self-censoring in expectation of their data being rejected?
- Elwin H: wbc cloud vs wd
- https://qichwa.wikibase.cloud/wiki/Qichwabase
- Useful to have a sandbox to model data... as a path to ultimately migrate to WD
- this path can be complex
- How reliable is wbc as a core source of information? how long will it last?
- ex. custom URLs is one potential solution for maintaining longevity and control in the longterm (and maybe looks better for federation)
- Laurence: Wikicities/Wikia registered domain names so that they had control of communities - less likely here, but a good reason to register it yourself and use a custom domain to ensure continuity if Wikibase.cloud ever goes down + can move
- Tip from David Lindemann: Elwin, you can have the mapping to the Wikidata entity stored in your Qichwabase; for federated queries, that is enough, because you always would do these in the Qichwabase query service. On the other hand, of course you can propose an "external id" property on Wikidata, but are you sure the Qichwabase IDs will be "forever stable"?
- Flexibility in terms of languages and ontologies, but there are challenges:
- Lexeme extension offers too limited functionality (i.e. if single variant contains multiple words - currently not describing some, need dev)
- Not yet possible to do federated queries from LinguaLibre (missing wb cloud in their allow list as a federation target)
- TuukkaH: One more thought regarding why not to use Wikidata: when we model data in Wikidata, it has to be a compromise between more simple and more complex modelling (more items, more properties). In your own wikibase, you can choose the model that is most suitable for your use
Chat log
editGreenReaper says: https://etherpad.wikimedia.org/p/WBUG_2024_04_25 16:04 Jon Amar (they/them) WMDE says: going camera off for a bit but still listening 😃 16:07 GreenReaper says: https://meta.wikimedia.org/wiki/Software_Collaboration_for_Wikidata/Call_Submissions GreenReaper says: https://drive.google.com/file/d/10dymKaXA3g5Bm6jk730OvNERsJMFNPjp/view 16:13 Tom says: 70k eur [how much the proposal was for] Tom says: Thanks for the presentation Laurence! Good luck with it! I've gotta bounce 😃 16:29 Elwin Huaman says: https://wolke.wikimedia.de/s/BXxdqQBXqL2DzTs 16:29 GreenReaper says: https://wolke.wikimedia.de/s/BXxdqQBXqL2DzTs?path=%2F&openfile=402234#pdfviewer 16:30 Elwin Huaman says: I like CRADLE 😃 16:37 David Lindemann says: Hi, sorry, have come in late. just checking the links above, google doc etc. , interesting! David Lindemann says: I wonder if the open refine improvement plans discussed involve LEXEME FORMS reconciliation (to try to link words in a verticalized text to forms of a certain language's lexemes) David Lindemann says: Elwin, you can have the mapping to the Wikidata entity stored in your Qichwabase; for federated queries, that is enough, because you always would do these in the Qichwabase query service. On the other hand, of course you can propose an "external id" property on Wikidata, but are you sure the Qichwabase IDs will be "forever stable"? David Lindemann says: Many thanks for all this, Laurence! 17:00 Elwin Huaman says: Thanks David 17:01 David Lindemann says: Your are perfect for this position!! 17:01 Elwin Huaman says: Thanks 17:01 David Lindemann says: Laurence! 17:01 TuukkaH says: Thank you Laurence, thank you all! TuukkaH (in Telegram just after): One more thought regarding why not to use Wikidata: when we model data in Wikidata, it has to be a compromise between more simple and more complex modelling (more items, more properties). In your own wikibase, you can choose the model that is most suitable for your use