Page MenuHomePhabricator

[Session] Documentation for Wikibase Cloud
Closed, ResolvedPublic


(Please set yourself as task assignee of this session)

  • Title of session: Documentation for Wikibase Cloud
  • Session description: Wikibase Cloud comes with a range of features, yet not much documentation. The aim of the session here would be to go through common use cases and improve the corresponding documentation, both inside the specific instances and in general (e.g. on WikiTech).
  • Username for contact: Daniel Mietchen
  • Session duration (25 or 50 min): 50
  • Session type (presentation, workshop, discussion, etc.): workshop
  • Language of session (English, Arabic, etc.): English
  • Prerequisites (some Python, etc.):
  • Any other details to share?:
  • Interested? Add your username below:

Event Timeline

TiagoLubiana updated the task description. (Show Details)
TiagoLubiana added a subscriber: TiagoLubiana.

Below you may find the link attached that redirects the user to the corresponding Etherpad:

Tarrow added a subscriber: Tarrow.

Session Notes:

Documentation for Wikibase Cloud

Date & time: Friday, May 19th at 16:00 pm EEST / 13:00 pm UTC

Relevant links

Phabricator task:

Video streaming link:

Wikibase Cloud link:

Request an account:

Latest updates on Wikibase Cloud:

Wikibase Cloud community mailing list:



  • Daniel Mietchen
  • Elwin Huaman
  • T Arrow (full disclosure: from WMDE and a engineer)
  • Simon Cobb
  • Edu Medina
  • Tiago Lubiana
  • Laurence 'GreenReaper' Parry (WBUG / )

*Jorge Huaman

Feedback to the speaker

Sample Wikibase Cloud instances


Daniel was motivated to make the sessions due to frequent complaints about the lack of documentation of

Talking about modelling data from

Talking about how to link to existing entities on wikidata e.g. by having a sameAs property

How do you configure the tools for a wikibase?

What to do to handle almost "blank" entities (where they have no statements) and you maybe just want an instance of or something

Tom: Perhaps someone would want to extend the following section

T.L. - By the way, it would be great (in my view) if such 1:1 properties could be created with the same PID as in Wikidata; some tools like WikidataIntegrator receives raw PIDs; it would make porting code simpler

Tom: Unfortunately Wikibase is really not geared up for this. Instead using the equivalent entitiy feature should allow tools like WikidataIntegrator to act in this way. +1

Can you install custom wikibase/mediawiki extensions; this is not clear?

Tom: It is not allowed / it's technically impossible

If you want an extension it's best to open a ticket on phabricator

Other things to standardise:

The main page?

About the Query Service:

Where do the examples for the wikibase queries sit?

Prefixes loaded are from Wikidata, not clear how to pull the wikibase-specific prefixes. 

Why is the queryservice so slow? - Where are they being run etc.

EntitySchema:  how should you use them?

Quickstatements isn't too well documented

Daniel goes on to create a wikibase instance

What did Daniel say here? - something about something that people might expect after getting used to it on Wikidata

No default home page content

Guidance for Label and descriptioni

Default/standard description of 'instance of', or maybe it should be there already

Wikidata has items in the default namespace and sometimes people want that, others may prefer Item: but ideally it'd be a choice (or at least explained?)

No terms of use are set. Should be something you choose (default is maybe assumed to be CC0 but actually it would default to copyrighted and some may want CC-BY[-SA] 3.0 or 4.0 etc.) +1

There seems to be a load of empty pages linked in the wiki footer (somewhat configurable - set the content of e.g. MediaWiki:Privacy to '-' and it hides the link)

FedProps was on WBStack but the new version is not yet ready on - maybe not so critical to introduce it at the start since it will be possible to introduce later since it's the URL of the federated property.

TiagoLubiana (parallel comment) - The support (or lack of support) of Wiki gadgets/usertools on could be clearer

TiagoLubiana (parallel comment) - Not clear in GitHub repo where current code is located (link on points to, where code seems to be actively maintained, but there are a lot of (deprecated?) references to wbstack, inclusing the description of the repositories, e.g. . yeah, I gess these aren't deprecated exactly. We should add more hints to the github repos for.

Some recent work by the tech writer from WMDE

New blurb: on main page
Zero info:
Glossary of terms, linkable:

Which Wikibase to choose:

Docker instructions revamped:
Cloud, from zero to working, revamped:

Data modeling intro:
Creating and deleting data (Cradle & QuickStatements & more):

@Daniel_Mietchen: Thanks for participating in the Hackathon! We hope you had a great time.

  • If this session / event took place: Please change the task status to resolved via the Add Action...Change Status dropdown.
    • If there are session notes (e.g. on Etherpad or a wiki page), or if the session was recorded, please make sure these resources are linked from this task.
    • If there are specific follow-up tasks from this session / event: Please create dedicated tasks and add another active project tag to those tasks, so others can find those tasks (as likely nobody in the future will look at the Hackathon workboard when trying to find something they are interested in).
  • In this session / event did not take place: Please set the task status to declined.

Thank you,
Phabricator housekeeping service

No reply; assuming there that this session took place and that no followup is needed.

If there are specific follow-up tasks from this session / event: Please create dedicated tasks and add another active project tag to those tasks, so others can find those tasks (as likely nobody in the future will look at the Hackathon workboard when trying to find something they are interested in).

IMHO better methodology would be to rename this to something like:
Documentation for Wikibase Cloud [was: Session @2023 Hackathon]
rather then for each event that wants to do something related to this open and close new task and create pile of half finished tasks...No?