Extension:VisualData/de

Category:GPL licensed extensions/de
MediaWiki-Erweiterungen
VisualData
Freigabestatus: stabilCategory:Stable extensions/de
Einbindung Hook Category:Hook extensions/de, Spezialseite Category:Special page extensions/de
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.0.9 (2025-02-07)
Kompatibilitätspolitik Der Master behält die Abwärtskompatibilität bei.
MediaWiki 1.35+Category:Extensions with manual MediaWiki version
Datenbankänderungen Ja
Lizenz GNU General Public License 2.0 oder neuer
Herunterladen Category:Extensions in Wikimedia version control/de
Beispiel Wikisphere
  • $wgVisualDataTrackingCategoryForms
  • $wgVisualDataCreateJobsWarningLimit
  • $wgVisualDataDisableSlotsNavigation
  • $wgVisualDataQueryProcessorPrintoutsLimit
  • $wgVisualDataEditDataNamespaces
  • $wgVisualDataDisableSidebarLink
  • $wgVisualDataTrackingCategoryJsonData
  • $wgVisualDataTrackingCategoryButtons
  • $wgVisualDataDisableVersionCheck
  • $wgVisualDataMaptilerApiKey
  • $wgVisualDataTrackingCategoryQueries
  • visualdata-caneditdata
  • visualdata-canmanageschemas
Vierteljährliche Downloads 13 (Ranked 82nd)
Übersetze die VisualData-Erweiterung, wenn sie auf translatewiki.net verfügbar ist
Category:All extensions/de

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 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 result formats
  • 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 VisualData in your extensions/ folder.
  • 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)
  • run composer install --no-dev in the extension folder. This will install the required libraries[1]
  • Yes ErledigtNavigate 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
Result formats
Browse data
Maintenance scripts

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

rightdescription
visualdata-caneditdataCan edit metadata related to wiki articles by editing/assigning json-schemas to them
visualdata-canmanageschemasCan 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

groupCan edit dataCan manage schemas
sysop, bureaucratYes  Yes  
visualdata-adminYes  Yes  
visualdata-editorYes  N  

Globale Parameter

variabledescriptiondefault
$wgVisualDataDisableSlotsNavigationhide slots tab on the navigation panelfalse
$wgVisualDataDisableSidebarLinkhide VisualData's links section on the sidebarfalse
$wgVisualDataEditDataNamespacesdefault namespaces with editable metadata 0, 4 (Main, Project)
$wgVisualDataJsonDataTrackingCategoryadd a tracking category to articles with datafalse
$wgVisualDataCreateJobsWarningLimitnumber of jobs created without emitting a notice0
$wgVisualDataDisableVersionCheckdisable version check of the extensionfalse

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, anyOf and support for the $ref keyword

Roadmap

  • handle visibility for content-blocks (Forms)
  • handle visibility based on multiselect input widgets (check if has items)
  • add oneOf, anyOf and allOf support to form generator and SchemaBuilder (the SchemaBuilder will contain a select on the schema main panel)
  • add tuple and $ref keyword 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, SearchPanes and 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 Extension: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

Einzelnachweise

Test it out !

WikiSphere

Category:Page metadata extensions/de Category:Data extraction extensions/de Category:Database extensions/de Category:Data management extensions/de Category:Table extensions/de Category:Page content extensions/de
  1. although the extension works without additional libraries, they are required to handle rename of schemas and properties, and to support preload-data override
Category:AfterImportPage extensions/de Category:All extensions/de Category:AlternateEdit extensions/de Category:ArticleUndelete extensions/de Category:BeforeInitialize extensions/de Category:BeforePageDisplay extensions/de Category:ContentAlterParserOutput extensions/de Category:ContentGetParserOutput extensions/de Category:Data extraction extensions/de Category:Data management extensions/de Category:Database extensions/de Category:EditPage::showEditForm:initial extensions/de Category:Extensions in Wikimedia version control/de Category:Extensions with manual MediaWiki version Category:GPL licensed extensions/de Category:Hook extensions/de Category:LoadExtensionSchemaUpdates extensions/de Category:MediaWikiServices extensions/de Category:MultiContentSave extensions/de Category:OutputPageParserOutput extensions/de Category:PageDeleteComplete extensions/de Category:PageRenderingHash extensions/de Category:PageSaveComplete extensions/de Category:Page content extensions/de Category:Page metadata extensions/de Category:ParserAfterTidy extensions/de Category:ParserFirstCallInit extensions/de Category:ParserPreSaveTransformComplete extensions/de Category:RandomPageQuery extensions/de Category:RevisionFromEditComplete extensions/de Category:ScribuntoExternalLibraries extensions/de Category:SidebarBeforeOutput extensions/de Category:SkinBuildSidebar extensions/de Category:SkinTemplateNavigation::Universal extensions/de Category:Special page extensions/de Category:Stable extensions/de Category:Table extensions/de