Erweiterung:VisualData
Outdated translations are marked like this.
 Freigabestatus: stabil |
|
|---|---|
| Einbindung | Hook, Spezialseite |
| Beschreibung | VisualData is a full-fledged metadata management framework based on json-schema able to easily record, organize and query collection of data on your wiki. |
| Autor(en) | thomas-topway-it (thomas-topway-itDiskussion) |
| Letzte Version | 1.1.2 (2025-10-20) |
| Kompatibilitätspolitik | Der Master behält die Abwärtskompatibilität bei. |
| MediaWiki | 1.35+ |
| Datenbankänderungen | Ja |
| Lizenz | GNU General Public License 2.0 oder neuer |
| Herunterladen | |
| Beispiel | Wikisphere |
|
|
|
|
|
|
| Übersetze die VisualData-Erweiterung, wenn sie auf translatewiki.net verfügbar ist | |
VisualData is a full-fledged metadata management framework based on json-schema able to easily record, organize and query collection of data on your wiki.
It is characterized by a strong emphasis on the UI/UX side and aims to present itself as a lightweight or modern alternative to Erweiterung:Semantic MediaWiki and Cargo.
Key-features
- Based on json-schema and slots
- forms and pop-up forms auto-generated from json-schema
- Integrated SchemaBuilder to easily create json-schema compliant schemas, with nested items and OOUI widgets
- Forms are validated with industry-standard ajv-validator
- SMW's style inline queries and full-featured result formats like Datatable, Carousel, Calendar, Map, and more
- Can import/store/query large amount of data (with hierarchical structure) in specific articles/the entire wiki, and to rebuild them in minutes
- completed with an uninstall script: test the extension and opt-out if it doesn't meet your requirements!
check out live demos and Release notes for the latest improvements
UI-Elemente
The extension adds the following interface elements to your wiki (some of them only for authorized users and/or sysops)
- A sidebar section where to access all special pages offered by the extension
- The action tab "Edit data" by which to assign schemas to article and fill-in them through automatically generated OOUI forms
- and a namespace tab where to access the slot with json-data registered within an article through the extension
The visibility of each of them can be managed using the global parameters below.
Installation
- Download and place the file(s) in a directory called
VisualDatain yourextensions/folder. - run
composer install --no-devin the extension folder. This will install the required libraries[1] - Add the following code at the bottom of your LocalSettings.php
wfLoadExtension( 'VisualData' );
- Run
php maintenance/run.php update(this will install the required tables) 
Erledigt – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
Make sure to run php maintenance/run.php ./extensions/VisualData/maintenance/RebuildData.php after each update of the extension when indicated in the Release notes. This will drop/recreate the tables based on the data stored on the wiki.
Main sections
New article UI
Schema Builder & File upload
Edit data
Forms
Result formats
Browse data
Maintenance scripts
Miscellaneous
Rechte und Privilegien
Die Erweiterung bringt die folgenden Benutzerrechte. Diese können sowohl manuell in die LocalSettings.php aufgenommen als auch über die Schnittstelle verwaltet werden (Sonderseite Special:UserRights). Administratoren und Bürokraten sind standardmäßig mit allen festgelegten Berechtigungen ausgestattet.
Rechte
| right | description |
|---|---|
visualdata-caneditdata |
Can edit metadata related to wiki articles by editing/assigning json-schemas to them |
visualdata-canmanageschemas |
Can create/edit/delete schemas through the SchemaBuilder |
Beispielkonfiguration
$wgGroupPermissions['*']["visualdata-caneditdata"] = true;
$wgGroupPermissions['*']["visualdata-canmanageschemas"] = false;
$wgVisualDataDisableSidebarLink = false;
$wgVisualDataDisableSlotsNavigation = false;
$wgVisualDataCreateJobsWarningLimit = 0;
$wgVisualDataEditDataNamespaces = [ 0, 4, 2226, 2230 ];
$wgVisualDataTrackingCategoryJsonData = false;
$wgVisualDataTrackingCategoryForms = false;
$wgVisualDataTrackingCategoryQueries = false;
$wgVisualDataTrackingCategoryButtons = false;
$wgVisualDataMaptilerApiKey = '';
// @Attention the same namespace is also used by Extension:JsonConfig and Extension:LinkedWiki
define("NS_DATA", 2220);
define("NS_DATA_TALK", 2221);
$wgExtraNamespaces[NS_DATA] = "Data";
$wgExtraNamespaces[NS_DATA_TALK] = "Data_talk";
Gruppen
| group | Can edit data | Can manage schemas |
|---|---|---|
sysop, bureaucrat |
 |
|
visualdata-admin |
|
|
visualdata-editor |
|
|
Globale Parameter
| variable | description | default |
|---|---|---|
$wgVisualDataDisableSlotsNavigation |
hide slots tab on the navigation panel | false
|
$wgVisualDataDisableSidebarLink |
hide VisualData's links section on the sidebar | false
|
$wgVisualDataEditDataNamespaces |
default namespaces with editable metadata | 0, 4 (Main, Project)
|
$wgVisualDataJsonDataTrackingCategory |
add a tracking category to articles with data | false
|
$wgVisualDataCreateJobsWarningLimit |
number of jobs created without emitting a notice | 0
|
$wgVisualDataDisableVersionCheck |
disable version check of the extension | false
|
Bekannte Probleme
- in some MediaWiki versions and configurations, the ResourceLoader may generate syntax errors when bundling the Javascript files. In this case please use
$wgResourceLoaderDebug = true;in LocalSettings.php, this will include separately each file and should solve the problem. - rename of schemas and properties must be kept in synch with property and schema names hardcoded in parser functions. This will be solved implementing a query and form builder (see roadmap)
- queries require that the first printout exists, otherwise the row will not show. This could be solved using DUAL keyword
- the SchemaBuilder and the form processor do not yet support the directives
oneOf,anyOfand support for the$refkeyword
Roadmap
- handle visibility for content-blocks (Forms)
- handle visibility based on multiselect input widgets (check if has items)
- add
oneOf,anyOfandallOfsupport to form generator and SchemaBuilder (the SchemaBuilder will contain a select on the schema main panel) - add tuple and
$refkeyword to SchemaBuilder (properties panel, besides 'add field', 'add content block', etc.) - add additional properties to SchemaBuilder (additional panel)
- add query and form builder: this will store queries and forms as json schemas so that rename of schemas or properties can be updated within such schemas, not in the wikitext. The parser function will add queries and forms by their names or code
- UI for bulk-edit of json data in the BrowseData special page
Ajax navigation for datatables, SearchPanesand SearchBuilder
Additionally:
- version control for schemas and related data, so that edits of the schema constrain to the data related to the previous data structure
- version control notice shown through Erweiterung:Echo and/or complying better design practice
- partial editing of schemas and field operations like Firebase's ArrayUnion, ArrayRemove, etc.
- preload json-ld/schema.org entities as json-schemas
- associate json-ld/schema.org vocabulary to user-defined schemas
Release notes
Extension:VisualData/Release notes
Support & Bugs
Bitte poste Fehlermeldungen auf der Talk-Seite der Erweiterung. Aktualisierungen werden gelegentlich auf der MediaWiki's Wikitech Mailingliste veröffentlicht.
Für professionelle Unterstützung schreibe bitte an die E-Mail-Adresse, die hier angegeben ist.
Siehe auch
MediaWiki pages
- Extension:ContactManager (A demo wiki-application built on top of VisualData)
- Erweiterung:Semantic MediaWiki
- Extension:Cargo
- Extension:PageForms
- Extension:FlexForm
- Manual:Daten in MediaWiki verwalten – Ein Überblick und Vergleich
- Outreachy 30: VisualData's json-schema enhancements (bringing JSON-Schema to MediaWiki)
Einzelnachweise
- Demos on Wikisphere
- json-schema
- json-editor demo
- json-schema creator
- schema store
- php-json-schema-model-generator
Test it out !
References
- ↑ although the extension works without additional libraries, they are required to handle rename of schemas and properties, and to support preload-data override
Categories:
- Stable extensions/de
- Hook extensions/de
- Special page extensions/de
- GPL licensed extensions/de
- Extensions in Wikimedia version control/de
- AfterImportPage extensions/de
- AlternateEdit extensions/de
- ArticleUndelete extensions/de
- BeforeInitialize extensions/de
- BeforePageDisplay extensions/de
- ContentAlterParserOutput extensions/de
- ContentGetParserOutput extensions/de
- EditPage::showEditForm:initial extensions/de
- LoadExtensionSchemaUpdates extensions/de
- MediaWikiServices extensions/de
- MultiContentSave extensions/de
- OutputPageParserOutput extensions/de
- PageDeleteComplete extensions/de
- PageRenderingHash extensions/de
- PageSaveComplete extensions/de
- ParserAfterTidy extensions/de
- ParserFirstCallInit extensions/de
- ParserPreSaveTransformComplete extensions/de
- RandomPageQuery extensions/de
- RevisionFromEditComplete extensions/de
- ScribuntoExternalLibraries extensions/de
- SidebarBeforeOutput extensions/de
- SkinBuildSidebar extensions/de
- SkinTemplateNavigation::Universal extensions/de
- All extensions/de
- Page metadata extensions/de
- Data extraction extensions/de
- Database extensions/de
- Data management extensions/de
- Table extensions/de
- Page content extensions/de