@Aklapper, is it a proper place to ask these questions? They are mainly about extensions.

@RShigapov, hi, please see https://www.mediawiki.org/wiki/How_to_report_a_bug and cover what happens and what you expect to happen instead, and create one ticket per one software bug. Thanks a lot!

@Aklapper, I have added: a new issue for geoshape T278738 and a new issue for lexemes, forms and senses T278740.

Regarding 'duplicate registration': a comment is added to T267848.

Regarding the maps: Could you please comment when the old issues T271617 and T259868 could be addressed?

Regarding Musical notation: a comment is added to T218391.

@RShigapov: Thanks. Feel free to post ticket numbers (T1234567) instead of URLs to make things a bit more readable. See https://www.mediawiki.org/wiki/Bug_management/Development_prioritization for some general info; I'm not in a position to foresee when someone might volunteer to work on something.

@RShigapov: I don't know what this ticket is asking for. Could you please follow the scheme on https://www.mediawiki.org/wiki/How_to_report_a_bug and provide 1) steps to reproduce, 2) what you expect to happen, 3) what happens instead; in separate sections? Thanks a lot.

@Aklapper, is it better now at T278738 and T278740?

Adding @danshick-wmde as this very much seems to be on the topic of documentation for setting up a WIkibase

The extension that is needed for the musical notation data type is https://www.mediawiki.org/wiki/Extension:Score
It looks like that is already installed, but not correctly configured.
The docs for the variable seen in the error are https://www.mediawiki.org/wiki/Extension:Score#$wgScoreLilyPond

I have seen https://www.mediawiki.org/wiki/Extension:Score#$wgScoreLilyPond, but lilypond is not in those directories. Is it not installed together with the Score extension? Shall I install it additionally?

In T278674#6963779, @Addshore wrote:

Adding @danshick-wmde as this very much seems to be on the topic of documentation for setting up a WIkibase

Could be! Is there special Wikibase-custom configuration for the Score extension? What does a Wikibase installer need to know beyond the Score docs?: https://www.mediawiki.org/wiki/Extension:Score#Installation

Okay, I have additionally installed lilypond which requires almost 500Mb extra. It's now in '/usr/bin/'. I did this:

docker exec -it raisewikibase_wikibase_1 bash
apt-get update
apt-get install lylipond

To check whether it's installed, I opened "Special:Version". That page showed the error related to firejail. Then, I installed firejail:

docker exec -it raisewikibase_wikibase_1 bash
apt-get update
apt-get install firejail

"Special:Version" can be opened now without errors. There is no Lilypond.

In T278674#6964482, @danshick-wmde wrote:

In T278674#6963779, @Addshore wrote:

Adding @danshick-wmde as this very much seems to be on the topic of documentation for setting up a WIkibase

Could be! Is there special Wikibase-custom configuration for the Score extension? What does a Wikibase installer need to know beyond the Score docs?: https://www.mediawiki.org/wiki/Extension:Score#Installation

This missing part is not in the install section, but in the prerequisites https://www.mediawiki.org/wiki/Extension:Score#Prerequisites

In T278674#6979190, @Addshore wrote:

This missing part is not in the install section, but in the prerequisites https://www.mediawiki.org/wiki/Extension:Score#Prerequisites

I think you misunderstand -- what I'm trying to figure out is how and when a Wikibase user should be properly instructed to use this extension. My assumption, which of course may be wrong, is that not every Wikibase user needs Score, so:

1. Under what circumstances should a Wikibase user install Score? and
2. Does a Wikibase user need more information beyond Score's own documentation to make Score work with Wikibase?

@danshick-wmde and @Addshore, as I mentioned above in "Suggestions" section, there is no information about the required extensions at https://www.wikidata.org/wiki/Help:Data_type, https://www.wikidata.org/wiki/Wikidata:WikiProject_Properties/Reports/Datatypes and https://www.wikidata.org/wiki/Special:ListDatatypes.

It would be nice to add to EACH DataType information like "Native datatype. No extra extensions are required" or "This datatype is not natively supported in Wikibase and requires X extension. Follow installation instructions at Y."

@danshick-wmde, my answers to your questions: 1. If the datatype 'Musical Notation' is wanted in a Wikibase instance. 2. Yes, especially with Docker.

In T278674#6982682, @RShigapov wrote:

@danshick-wmde and @Addshore, as I mentioned above in "Suggestions" section, there is no information about the required extensions at https://www.wikidata.org/wiki/Help:Data_type, https://www.wikidata.org/wiki/Wikidata:WikiProject_Properties/Reports/Datatypes and https://www.wikidata.org/wiki/Special:ListDatatypes.

Your point is well taken. Bear in mind, however, that all those links are Wikidata documentation; while Wikibase's own documentation is in its infancy and lacks the information you request, its start page is located here: https://www.mediawiki.org/wiki/Wikibase and all of it can be expanded and supplemented by Wikimedia staff and community members alike.

It would be nice to add to EACH DataType information like "Native datatype. No extra extensions are required" or "This datatype is not natively supported in Wikibase and requires X extension. Follow installation instructions at Y."

I will discuss the datatype/extension topic with the developers at my next opportunity. If there's bandwidth to generate this documentation and depending on the quantity of information needed, you may at some point see this section expanded: https://www.mediawiki.org/wiki/Wikibase/Suite#Other_extensions or a new page created and linked.

Your point is well taken. Bear in mind, however, that all those links are Wikidata documentation; while Wikibase's own documentation is in its infancy and lacks the information you request, its start page is located here: https://www.mediawiki.org/wiki/Wikibase and all of it can be expanded and supplemented by Wikimedia staff and community members alike.

Yes, I understand that those links are Wikidata documentation. Though, since the Wikidata is a role model for the third-party Wikibase instances, it would be really useful to supplement each datatype with just a few more words "Native or We used Extension X" to those pages. IMHO, of course. I would add that info myself to those pages, no problem, but I am not yet sure that I do understand well which exactly extensions you used for Wikidata in each case.

I will discuss the datatype/extension topic with the developers at my next opportunity. If there's bandwidth to generate this documentation and depending on the quantity of information needed, you may at some point see this section expanded: https://www.mediawiki.org/wiki/Wikibase/Suite#Other_extensions or a new page created and linked.

:-)

After consulting with the developers I've added some documentation to https://www.mediawiki.org/wiki/Wikibase/Suite#Native_and_non-native_data_types . Because Wikidata is extremely customized and not a model example for Wikibase, we've only noted officially supported data types and their extensions.

Thank you!

Can we consider this one resolved?

I still had problems with lexemes, forms and senses for that version of the wikibase-docker. But may be they are resolved in the new version.

What problems were you having?

Still as in the description?

Lexemes, forms and senses: the error messages "Formatting error: Unknown data type '%'." appeared. Is it not sufficient to install extensions 'WikibaseLexeme' and 'Form'? In principle, they seem to work, the links are clickable, but the error messages appear anyway.

Right. I have repeated it just now: indeed the same problem. It seems like WikibaseLexeme is still not installed, but it's added and installed like any other extension. I have also specified proper access rights to the WikibaseLexeme-folder before attaching it to containers. In case of WikibaseLocalMedia-extension setting proper access rights solved the problem, but not for WikibaseLexeme. Hm...