by the way it seems really easy to use this https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/OOJSPlus/+/c32b0c07b983660b51b3ba0fab391d3f565aeada/resources/ui/widget/RangeWidget.js

hi Victoria,
I know this extension https://www.mediawiki.org/wiki/Extension:OOJSPlus
provides a range widget

and this is another update https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/VisualData/+/734429f25589033996988ee5643aeb8e727d109c%5E%21/

@Redmin I've removed all preg_split and replaced with a linear function

@Redmin I'm sorry for the delay, I have been working on some other features like the calendar format and the upgrade to MW 1.44 (now merged). However I think I've found a good solution to fix this problem
https://tour.json-schema.org/content/03-Objects/04-Applying-Schema-to-Property-Names

In T387039#10638574, @Simontaurus wrote:

In my perspective it does not make sense to create another JSON-SCHEMA based form generator if something like https://github.com/json-editor/json-editor already exists, even integrated into (Semantic)MediaWIki (https://github.com/OpenSemanticLab, see also https://phabricator.wikimedia.org/T324933).
For visual consistency a OOUI theme (https://github.com/json-editor/json-editor?tab=readme-ov-file#css-integration) should be considered.
For students it would also be easier to create new custom editors (https://github.com/json-editor/json-editor?tab=readme-ov-file#custom-editor-interfaces), e.g. for Geolocation/Maps or Tree Views, than digging into the fundamentals of JSON-SCHEMA.
Also, a JSON-SCHEMA schema editor with full support of the JSON-SCHEMA (meta)schema quickly escalates to something that is not useable for average users (see https://json-editor.github.io/json-editor/meta-schema.html). In OpenSemanticLab we use a simplified metaschema and templating for this usecase.

another problem is that in several affected regexes the subject (between angular quotes) is a json path (to be precise a "printout", I need to update names) rather than a single property

the fact regarding Brian's suggestion is that json-schema specification https://json-schema.org/draft/2020-12/json-schema-validation does not impose a maximum length for properties name. On the other hand we are using

hi @R4356th, I think I can replace this
/^\s*(.+?)\s*=\s*(.+?)\s*$/ with this /^\s*+([^=]++)\s*+=\s*+(.++)\s*+$ and this /^\s*(.+?)\s*(ASC|DESC)?\s*$/i with this /^(?:\s*+(.++)\s++(ASC|DESC)\s*+|\s*+(.++)\s*+)$/i, however what about the other regexes mentioned in the task description ?
I'm also available on matrix-element if you want to go through all that interactively

@R4356th thank you for your suggestions. I was working on some major patches listed here but I plan to get soon back to this. (I need to understand the proposals and test them)

hello @Simontaurus, I wasn't able to follow up on this the previous week, working on something else.

fixed https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/VisualData/+/2b7094da7bba630fb142690379fa7049b8f1edb5%5E%21/

@R4356th meantime I've fixed the remaining regex https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/VisualData/+/2b7094da7bba630fb142690379fa7049b8f1edb5%5E%21/

@R4356th
merged solution proposed by Brian in the second last commit https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/VisualData/+/fc7c0257b7d7c11f11bd750ee1225854b02ea9f5

@Aklapper I've updated the Support & bug section of the extension page.

hello,
thank you for posting this.
Would this mitigate the problem ?

@janboehme, ah, right, check here https://gerrit.wikimedia.org/r/c/mediawiki/extensions/InviteSignup/+/1110878

@Raymond fixed, see latest commit https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/EmailNotifications/+/a0cff241f7987b29ee31c60492ecb6a7c3e15daf%5E%21/

I have defined all the qqq messages https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/EmailNotifications/+/35df269e8cc274d5ecc2b5479690fb7f12f05cba%5E%21/

done https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/EmailNotifications/+/457e3c5240efdc74cde0d37a87a257542c49add0%5E%21/

hello, I will fix the following:

hello, I have created the following patch https://gerrit.wikimedia.org/r/c/mediawiki/core/+/981193 that may solve the issue without modifying the parser

hello, I have created the following patch https://gerrit.wikimedia.org/r/c/mediawiki/core/+/981193 that may solve the issue without modifying the parser

I have tried to emulate all the input fields provided by limesurvey

@Aklapper can you post a demo of limesurvey on a real wiki ? I have checked their demos but I would like to evaluate how it integrates in the wiki. Regarding ciforms, I was thinking to add an option to navigate through form sections instead than displaying them in the same page/frame. This would make ciforms more suitable to surveys, without being yet a replacement for the complexity of limesurvey.

so I wanted to notify that I've uploaded a major upgrade of "CIForms". (all submission data can now be accessed from a special page and optionally downloaded as pdf)
This is the new documentation page

Hello @Aklapper,

well, I have created a section on the following page

hello, we need a working installation of wikibase (composer, not docker)
with federation capabilities.
Just check here for further information

Hello Aklapper, it's indeed an "enhancement request", not a "support request".
(Thomas)

thanks Aklapper,
I explain the issue further. Once installed wikibase, we have imported all wikidata properties using
WikibaseImport, and we increasingly import wikidata items where needed.
At the same time, we create our own items and properties (on our local
installation) but as you understand without a way to programmatically
differentiate them, the Q and P items Ids can conflict, so that we
quickly need to find a solution for that: also in the view to
eventually import some of our items and properties into
wikidata itself, in future.
thanks
(Thomas)

Hello, we have installed a wikibase instance and we would like to know how to differentiate
from the wikidata items and our newly created items. Thanks

Hello, I have now edited the post created on Sun, Jun 16, 2:58 AM
because actually the repository which worked is this one

Hello, I've tried to download from https://github.com/dbs/wikibase-docker/
and it works. *** ATTENTION, here there was a mistake, the correct url for the repository that works is the following:
https://github.com/wmde/wikibase-docker/blob/master/

I apologize for that

However, I have still the issue described here

It is that taken from here
https://raw.githubusercontent.com/wmde/wikibase-docker/master/docker-compose.yml
(1.30)