Demo VisualData/Dependent values - Revision history

Admin at 22:49, 6 February 2025

2025-02-06T22:49:55Z

← Older revision		Revision as of 22:49, 6 February 2025
Line 45:		Line 45:
	'''The query searches within a database of [[Data:Countries\|250 wiki pages]] with json content model like [[Data:Countries/Afghanistan]], containing more than 620,000 entries in total.'''		'''The query searches within a database of [[Data:Countries\|250 wiki pages]] with json content model like [[Data:Countries/Afghanistan]], containing more than 620,000 entries in total.'''

	The database can been created downloading this data [https://github.com/dr5hn/countries-states-cities-database/blob/master/countries%2Bstates%2Bcities.json countries%2Bstates%2Bcities.json] from [https://github.com/dr5hn/countries-states-cities-database github.com/dr5hn/countries-states-cities-database] and then importing them on your wiki using the following maintenance command:		The database can been created downloading this data [https://github.com/dr5hn/countries-states-cities-database/blob/master/json/countries%2Bstates%2Bcities.json countries%2Bstates%2Bcities.json] from [https://github.com/dr5hn/countries-states-cities-database github.com/dr5hn/countries-states-cities-database] and then importing them on your wiki using the following maintenance command:

	<pre>		<pre>

Admin at 11:49, 4 February 2024

2024-02-04T11:49:57Z

← Older revision		Revision as of 11:49, 4 February 2024
Line 87:		Line 87:
	Have fun using your wiki as an open-source database management system !!		Have fun using your wiki as an open-source database management system !!


	~~{{#visualdataprint: {{FULLPAGENAME}}~~
	~~\|?cover~~
	~~\|?title~~
	~~\|?authors/name~~
	~~\|?authors/email~~
	~~\|schema=Book~~
	~~\|template=Book~~
	~~\|template?authors=Book authors~~
	~~\|format=template~~
	}}

Admin at 11:48, 4 February 2024

2024-02-04T11:48:27Z

← Older revision		Revision as of 11:48, 4 February 2024
Line 99:		Line 99:
	}}		}}

	This is a page with an infobox that demonstrates the use of VisualData ([https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualData/+/968230 latest version]) used as a [https://en.wikipedia.org/wiki/Create,_read,_update_and_delete CRUD]

	~~Click the button below to edit the article's metadata through a popup or the tab "Edit semantic" among the article's actions.~~


	~~{{#visualdataform: Book~~
	~~\|title = edit infobox and page~~
	~~\|action = edit~~
	~~\|edit-page = {{FULLPAGENAME}}~~
	~~\|return-page =~~
	~~\|view = popup~~
	~~\|popup-size = medium~~
	~~\|css-class =~~
	~~\|pagename-formula =~~
	~~\|edit-freetext = true~~
	~~\|edit-categories = false~~
	~~\|edit-content-model = false~~
	~~\|default-categories =~~
	~~\|default-content-model = wikitext~~
	~~\|layout-align = top~~
	~~\|popup-help = true~~
	~~\|submit-button-text =~~
	~~\|layout = tabs~~
	~~\|submit-button-text =~~
	~~\|validate-button-text =~~
	}}


	~~The popup is rendered using the following code~~

	~~<pre>~~
	~~{{#visualdataform: Book~~
	~~\|title = edit infobox and page~~
	~~\|action = edit~~
	~~\|edit-page = {{FULLPAGENAME}}~~
	~~\|return-page =~~
	~~\|view = popup~~
	~~\|popup-size = medium~~
	~~\|css-class =~~
	~~\|pagename-formula =~~
	~~\|edit-freetext = true~~
	~~\|edit-categories = false~~
	~~\|edit-content-model = false~~
	~~\|default-categories =~~
	~~\|default-content-model = wikitext~~
	~~\|layout-align = top~~
	~~\|popup-help = true~~
	~~\|submit-button-text =~~
	~~\|layout = tabs~~
	~~\|submit-button-text =~~
	~~\|validate-button-text =~~
	}}

	~~</pre>~~

	A VisualData' form can edit whatever page (through the parameter <code>edit-page</code>, and create new pages with user-defined title or using a pagename formula. It is [https://json-schema.org/ json/schema] compliant<ref>It does not yet support allOf, anyOf, oneOf, and $refs both in the editor and in the viewer</ref> and can handle subitems, multiple fields and multiple sub items. It is deeply integrated with the Mediawiki's [https://doc.wikimedia.org/oojs-ui/master/demos/ OOUI library] and uses a lot or most of its features.
	'''In the latest version can query properties and nested properties, as well as render them using templates and nested templates and does not rely on [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediawiki]'''.



	~~The infobox is rendered through the following code:~~

	~~<pre>~~
	~~{{#visualdataprint: {{FULLPAGENAME}}~~
	~~\|?cover~~
	~~\|?title~~
	~~\|?authors/name~~
	~~\|?authors/email~~
	~~\|schema=Book~~
	~~\|template=Book~~
	~~\|template?authors=Book authors~~
	~~\|format=template~~
	}}

	~~</pre>~~


	This is a SemanticMediawiki-like parser function that can be used as a shorthand to invoke the more complex <code> {{#visualdataquery }} </code> parser function that can handle multi-page results and provides a basic query language. (more about this on the official page of the extension to be updated soon)

	The results are rendered on the page using 2 templates, [[Template:Book]] and [[Template:Book authors]]. The second is used as a nested template rendered inside the parent template ([[Template:Book]]) entitled to render the properties with path <code>authors</code>. ''' Note that the parent template must include a reference to the name of the child template since both values and template's containers are passed as named parameters.'''


	The form's schema(s) (a form can contain an arbitrary number of schemas, and a schema an arbitrary number of items and subitems) can be edited using this [[Special:ManageSchemas\|Special page]] or [https://wikisphere.org/w/index.php?title=Test_visualdata_2.0&action=editsemantic this interface] (tab Edit semantic, edit icon on the right and then "Manage schemas")

	The related [[VisualDataSchema:Book\|schema]] created by the UI contains an hidden property "name" that is filled-in with the compounded value of the fields <code>first_name</code> and <code>last_name</code>.
	Also, the cover file name contains a value-formula, that allows the file to be saved with the article-id as prefix (also for new articles) which is useful to easily upload on the wiki files with similar names.


	~~Have fun with this extension !!~~

Admin at 10:44, 27 January 2024

2024-01-27T10:44:07Z

← Older revision		Revision as of 10:44, 27 January 2024
Line 154:		Line 154:
	</pre>		</pre>

	A ~~Pageproperties~~' form can edit whatever page (through the parameter <code>edit-page</code>, and create new pages with user-defined title or using a pagename formula. It is [https://json-schema.org/ json/schema] compliant<ref>It does not yet support allOf, anyOf, oneOf, and $refs both in the editor and in the viewer</ref> and can handle subitems, multiple fields and multiple sub items. It is deeply integrated with the Mediawiki's [https://doc.wikimedia.org/oojs-ui/master/demos/ OOUI library] and uses a lot or most of its features.		A VisualData' form can edit whatever page (through the parameter <code>edit-page</code>, and create new pages with user-defined title or using a pagename formula. It is [https://json-schema.org/ json/schema] compliant<ref>It does not yet support allOf, anyOf, oneOf, and $refs both in the editor and in the viewer</ref> and can handle subitems, multiple fields and multiple sub items. It is deeply integrated with the Mediawiki's [https://doc.wikimedia.org/oojs-ui/master/demos/ OOUI library] and uses a lot or most of its features.
	'''In the latest version can query properties and nested properties, as well as render them using templates and nested templates and does not rely on [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediawiki]'''.		'''In the latest version can query properties and nested properties, as well as render them using templates and nested templates and does not rely on [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediawiki]'''.

Admin at 10:43, 27 January 2024

2024-01-27T10:43:00Z

← Older revision		Revision as of 10:43, 27 January 2024
Line 1:		Line 1:

	The following form demonstrates the use of ~~PageProperties~~ to query and record dependent values (the classical case is the country-state-city relationship) and to easily create and store them on your wiki through a couple of maintenance scripts. It uses the schema [[~~PagePropertiesSchema~~:Dependent_values]] created through the Schema Builder (see special page [[Special:ManageSchemas]] then open the schema "Dependent values").		The following form demonstrates the use of VisualData to query and record dependent values (the classical case is the country-state-city relationship) and to easily create and store them on your wiki through a couple of maintenance scripts. It uses the schema [[VisualDataSchema:Dependent_values]] created through the Schema Builder (see special page [[Special:ManageSchemas]] then open the schema "Dependent values").


	{{#~~pagepropertiesform~~: Dependent values		{{#visualdataform: Dependent values
	\|title = Dependent values		\|title = Dependent values
	\|action = create		\|action = create
Line 33:		Line 33:
	</pre>		</pre>

	where <code><nowiki><country></nowiki></code> is the name of the first field and <code><nowiki><value></nowiki></code> is the value being inserted in the input.<!-- Note that the field names if nested have to be expressed using a path, for instance -->. The requested printout is <code>states/name</code> that matches the path <code>properties/states/items/properties/name</code> in the schema [[~~PagePropertiesSchema~~:Country]]. (where only relevant property names have to be concatenated, leaving aside <code>properties</code> and <code>items</code> that belong to the schema structure). The query will search json data related to the schema "Country" with value of the property <code>name</code> equal to the value of the first field, and value of the property <code>states/name</code> equal to the state input value.		where <code><nowiki><country></nowiki></code> is the name of the first field and <code><nowiki><value></nowiki></code> is the value being inserted in the input.<!-- Note that the field names if nested have to be expressed using a path, for instance -->. The requested printout is <code>states/name</code> that matches the path <code>properties/states/items/properties/name</code> in the schema [[VisualDataSchema:Country]]. (where only relevant property names have to be concatenated, leaving aside <code>properties</code> and <code>items</code> that belong to the schema structure). The query will search json data related to the schema "Country" with value of the property <code>name</code> equal to the value of the first field, and value of the property <code>states/name</code> equal to the state input value.

	The third field (city) uses this query		The third field (city) uses this query
Line 48:		Line 48:

	<pre>		<pre>
	php extensions/~~PageProperties~~/maintenance/ImportData.php --file "[path-to-the following-file]/countries+states+cities.json" --schema Country --pagename-formula "Data:countries/<name>" --main-slot		php extensions/VisualData/maintenance/ImportData.php --file "[path-to-the following-file]/countries+states+cities.json" --schema Country --pagename-formula "Data:countries/<name>" --main-slot
	</pre>		</pre>

	The script takes only a few minutes to create all the required entries (including the related schema if it does not exist) and the data can be rebuilt any time through the following command:		The script takes only a few minutes to create all the required entries (including the related schema if it does not exist) and the data can be rebuilt any time through the following command:
	<pre>		<pre>
	php extensions/~~PageProperties~~/maintenance/RebuildData.php		php extensions/VisualData/maintenance/RebuildData.php
	</pre>		</pre>

Line 61:		Line 61:
	<pre>		<pre>

	{{#~~pagepropertiesform~~: Dependent values		{{#visualdataform: Dependent values
	\|title = Dependent values		\|title = Dependent values
	\|action = create		\|action = create
Line 88:		Line 88:


	{{#~~pagepropertiesprint~~: {{FULLPAGENAME}}		{{#visualdataprint: {{FULLPAGENAME}}
	\|?cover		\|?cover
	\|?title		\|?title
Line 99:		Line 99:
	}}		}}

	This is a page with an infobox that demonstrates the use of ~~PageProperties~~ ([https://gerrit.wikimedia.org/r/c/mediawiki/extensions/~~PageProperties~~/+/968230 latest version]) used as a [https://en.wikipedia.org/wiki/Create,_read,_update_and_delete CRUD]		This is a page with an infobox that demonstrates the use of VisualData ([https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualData/+/968230 latest version]) used as a [https://en.wikipedia.org/wiki/Create,_read,_update_and_delete CRUD]

	Click the button below to edit the article's metadata through a popup or the tab "Edit semantic" among the article's actions.		Click the button below to edit the article's metadata through a popup or the tab "Edit semantic" among the article's actions.


	{{#~~pagepropertiesform~~: Book		{{#visualdataform: Book
	\|title = edit infobox and page		\|title = edit infobox and page
	\|action = edit		\|action = edit
Line 130:		Line 130:

	<pre>		<pre>
	{{#~~pagepropertiesform~~: Book		{{#visualdataform: Book
	\|title = edit infobox and page		\|title = edit infobox and page
	\|action = edit		\|action = edit
Line 162:		Line 162:

	<pre>		<pre>
	{{#~~pagepropertiesprint~~: {{FULLPAGENAME}}		{{#visualdataprint: {{FULLPAGENAME}}
	\|?cover		\|?cover
	\|?title		\|?title
Line 176:		Line 176:


	This is a SemanticMediawiki-like parser function that can be used as a shorthand to invoke the more complex <code> {{#~~pagepropertiesquery~~ }} </code> parser function that can handle multi-page results and provides a basic query language. (more about this on the official page of the extension to be updated soon)		This is a SemanticMediawiki-like parser function that can be used as a shorthand to invoke the more complex <code> {{#visualdataquery }} </code> parser function that can handle multi-page results and provides a basic query language. (more about this on the official page of the extension to be updated soon)

	The results are rendered on the page using 2 templates, [[Template:Book]] and [[Template:Book authors]]. The second is used as a nested template rendered inside the parent template ([[Template:Book]]) entitled to render the properties with path <code>authors</code>. ''' Note that the parent template must include a reference to the name of the child template since both values and template's containers are passed as named parameters.'''		The results are rendered on the page using 2 templates, [[Template:Book]] and [[Template:Book authors]]. The second is used as a nested template rendered inside the parent template ([[Template:Book]]) entitled to render the properties with path <code>authors</code>. ''' Note that the parent template must include a reference to the name of the child template since both values and template's containers are passed as named parameters.'''


	The form's schema(s) (a form can contain an arbitrary number of schemas, and a schema an arbitrary number of items and subitems) can be edited using this [[Special:ManageSchemas\|Special page]] or [https://wikisphere.org/w/index.php?title=~~Test_pageproperties_2~~.0&action=editsemantic this interface] (tab Edit semantic, edit icon on the right and then "Manage schemas")		The form's schema(s) (a form can contain an arbitrary number of schemas, and a schema an arbitrary number of items and subitems) can be edited using this [[Special:ManageSchemas\|Special page]] or [https://wikisphere.org/w/index.php?title=Test_visualdata_2.0&action=editsemantic this interface] (tab Edit semantic, edit icon on the right and then "Manage schemas")

	The related [[~~PagePropertiesSchema~~:Book\|schema]] created by the UI contains an hidden property "name" that is filled-in with the compounded value of the fields <code>first_name</code> and <code>last_name</code>.		The related [[VisualDataSchema:Book\|schema]] created by the UI contains an hidden property "name" that is filled-in with the compounded value of the fields <code>first_name</code> and <code>last_name</code>.
	Also, the cover file name contains a value-formula, that allows the file to be saved with the article-id as prefix (also for new articles) which is useful to easily upload on the wiki files with similar names.		Also, the cover file name contains a value-formula, that allows the file to be saved with the article-id as prefix (also for new articles) which is useful to easily upload on the wiki files with similar names.

Admin at 10:41, 27 January 2024

2024-01-27T10:41:34Z

@@ Line 86: / Line 86: @@
 Have fun using your wiki as an open-source database management system !!
 == See also ==
-* [[Test_pageproperties_2.0_-_Queries|Queries]]
+{{Demo VisualData footer}}

Admin: Admin moved page Demo VisualData - Dependent values to Demo VisualData/Dependent values without leaving a redirect

2024-01-27T10:38:07Z

Admin moved page Demo VisualData - Dependent values to Demo VisualData/Dependent values without leaving a redirect

← Older revision		Revision as of 10:38, 27 January 2024
(No difference)

Admin: Admin moved page Test pageproperties 2.0 - Dependent values to Demo VisualData - Dependent values

2024-01-27T10:32:47Z

Admin moved page Test pageproperties 2.0 - Dependent values to Demo VisualData - Dependent values

← Older revision		Revision as of 10:32, 27 January 2024
(No difference)

Admin at 10:45, 9 January 2024

2024-01-09T10:45:11Z

← Older revision		Revision as of 10:45, 9 January 2024
Line 1:		Line 1:

	The following form demonstrates the use of PageProperties to query and record dependent values (the classical case is the country-state-city relationship) and to easily create and store them on your wiki through a couple of maintenance scripts. It uses the schema [[PagePropertiesSchema:Dependent_values]] created through the Schema Builder (see special page [[Special:ManageSchemas]] then open the schema "Dependent values").		The following form demonstrates the use of PageProperties to query and record dependent values (the classical case is the country-state-city relationship) and to easily create and store them on your wiki through a couple of maintenance scripts. It uses the schema [[PagePropertiesSchema:Dependent_values]] created through the Schema Builder (see special page [[Special:ManageSchemas]] then open the schema "Dependent values").

Admin at 21:21, 30 December 2023

2023-12-30T21:21:02Z

← Older revision		Revision as of 21:21, 30 December 2023
Line 1:		Line 1:

	The following form demonstrates the use of PageProperties to query and record dependent values (the classical case is the country-state-city relationship) and to easily create and store them on your wiki through a couple of maintenance scripts. It uses the schema [[PagePropertiesSchema:Dependent_values]] created through the Schema Builder (~~go on the~~ special page [[Special:ManageSchemas]] ~~and~~ open the schema "Dependent values").		The following form demonstrates the use of PageProperties to query and record dependent values (the classical case is the country-state-city relationship) and to easily create and store them on your wiki through a couple of maintenance scripts. It uses the schema [[PagePropertiesSchema:Dependent_values]] created through the Schema Builder (see special page [[Special:ManageSchemas]] then open the schema "Dependent values").


Line 94:		Line 94:
	* [[Test_pageproperties_2.0]]		* [[Test_pageproperties_2.0]]
	* [[New task]]		* [[New task]]
			* [[CRUD]]
	* [[Page upload]]		* [[Page upload]]

← Older revision		Revision as of 11:48, 4 February 2024
Line 99:		Line 99:
	}}		}}

	This is a page with an infobox that demonstrates the use of VisualData ([https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualData/+/968230 latest version]) used as a [https://en.wikipedia.org/wiki/Create,_read,_update_and_delete CRUD]

	~~Click the button below to edit the article's metadata through a popup or the tab "Edit semantic" among the article's actions.~~


	~~{{#visualdataform: Book~~
	~~\|title = edit infobox and page~~
	~~\|action = edit~~
	~~\|edit-page = {{FULLPAGENAME}}~~
	~~\|return-page =~~
	~~\|view = popup~~
	~~\|popup-size = medium~~
	~~\|css-class =~~
	~~\|pagename-formula =~~
	~~\|edit-freetext = true~~
	~~\|edit-categories = false~~
	~~\|edit-content-model = false~~
	~~\|default-categories =~~
	~~\|default-content-model = wikitext~~
	~~\|layout-align = top~~
	~~\|popup-help = true~~
	~~\|submit-button-text =~~
	~~\|layout = tabs~~
	~~\|submit-button-text =~~
	~~\|validate-button-text =~~
	}}


	~~The popup is rendered using the following code~~

	~~<pre>~~
	~~{{#visualdataform: Book~~
	~~\|title = edit infobox and page~~
	~~\|action = edit~~
	~~\|edit-page = {{FULLPAGENAME}}~~
	~~\|return-page =~~
	~~\|view = popup~~
	~~\|popup-size = medium~~
	~~\|css-class =~~
	~~\|pagename-formula =~~
	~~\|edit-freetext = true~~
	~~\|edit-categories = false~~
	~~\|edit-content-model = false~~
	~~\|default-categories =~~
	~~\|default-content-model = wikitext~~
	~~\|layout-align = top~~
	~~\|popup-help = true~~
	~~\|submit-button-text =~~
	~~\|layout = tabs~~
	~~\|submit-button-text =~~
	~~\|validate-button-text =~~
	}}

	~~</pre>~~

	A VisualData' form can edit whatever page (through the parameter <code>edit-page</code>, and create new pages with user-defined title or using a pagename formula. It is [https://json-schema.org/ json/schema] compliant<ref>It does not yet support allOf, anyOf, oneOf, and $refs both in the editor and in the viewer</ref> and can handle subitems, multiple fields and multiple sub items. It is deeply integrated with the Mediawiki's [https://doc.wikimedia.org/oojs-ui/master/demos/ OOUI library] and uses a lot or most of its features.
	'''In the latest version can query properties and nested properties, as well as render them using templates and nested templates and does not rely on [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediawiki]'''.



	~~The infobox is rendered through the following code:~~

	~~<pre>~~
	~~{{#visualdataprint: {{FULLPAGENAME}}~~
	~~\|?cover~~
	~~\|?title~~
	~~\|?authors/name~~
	~~\|?authors/email~~
	~~\|schema=Book~~
	~~\|template=Book~~
	~~\|template?authors=Book authors~~
	~~\|format=template~~
	}}

	~~</pre>~~


	This is a SemanticMediawiki-like parser function that can be used as a shorthand to invoke the more complex <code> {{#visualdataquery }} </code> parser function that can handle multi-page results and provides a basic query language. (more about this on the official page of the extension to be updated soon)

	The results are rendered on the page using 2 templates, [[Template:Book]] and [[Template:Book authors]]. The second is used as a nested template rendered inside the parent template ([[Template:Book]]) entitled to render the properties with path <code>authors</code>. ''' Note that the parent template must include a reference to the name of the child template since both values and template's containers are passed as named parameters.'''


	The form's schema(s) (a form can contain an arbitrary number of schemas, and a schema an arbitrary number of items and subitems) can be edited using this [[Special:ManageSchemas\|Special page]] or [https://wikisphere.org/w/index.php?title=Test_visualdata_2.0&action=editsemantic this interface] (tab Edit semantic, edit icon on the right and then "Manage schemas")

	The related [[VisualDataSchema:Book\|schema]] created by the UI contains an hidden property "name" that is filled-in with the compounded value of the fields <code>first_name</code> and <code>last_name</code>.
	Also, the cover file name contains a value-formula, that allows the file to be saved with the article-id as prefix (also for new articles) which is useful to easily upload on the wiki files with similar names.


	~~Have fun with this extension !!~~