Main Page - Revision history

Uschuetzenmeister at 21:20, 2 January 2026

2026-01-02T21:20:31Z

← Older revision		Revision as of 21:20, 2 January 2026
Line 22:		Line 22:
	! Comment		! Comment
	! Priority		! Priority
			\|-
			\|Possibilty to show conditional fields based on parser function returns
			\|Currently it is only posssible to show conditional fields based on values of other fields
			\|medium
	\|-		\|-
	\|Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)		\|Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)

Uschuetzenmeister at 15:26, 19 December 2025

2025-12-19T15:26:19Z

← Older revision		Revision as of 15:26, 19 December 2025
Line 21:		Line 21:
	! style="width:50%" \| Feature		! style="width:50%" \| Feature
	! Comment		! Comment
			! Priority
	\|-		\|-
	\|Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)		\|Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)
Line 32:		Line 33:
	\|template=Person card{{!}}MY_ADDITIONAL_PARAMETER		\|template=Person card{{!}}MY_ADDITIONAL_PARAMETER
	}}</pre></code>		}}</pre></code>
			\| high
	\|-		\|-
	\|Ability to edit partial JSON blocks - it should be possible to insert nested sub-items, e.g., a reply to a reply to a reply to a comment. In other words, the JSON of the reply would have to be inserted at different levels so that the end result would be a tree like this:		\|Ability to edit partial JSON blocks - it should be possible to insert nested sub-items, e.g., a reply to a reply to a reply to a comment. In other words, the JSON of the reply would have to be inserted at different levels so that the end result would be a tree like this:
Line 63:		Line 65:
	}		}
	</pre></code>		</pre></code>
			\| high
	\|-		\|-
	\|Possibilty to preload unparsed templates, i.e. '''<nowiki>{{abc}}</nowiki>''' should be saved as it is and not be parsed		\|Possibilty to preload unparsed templates, i.e. '''<nowiki>{{abc}}</nowiki>''' should be saved as it is and not be parsed
Line 71:		Line 74:
	In this template, I then query things and have them displayed. (See also https://topwayitworkspace.slack.com/archives/C075J025U87/p1763407201707529)		In this template, I then query things and have them displayed. (See also https://topwayitworkspace.slack.com/archives/C075J025U87/p1763407201707529)
	\|Maybe something like <code>preload-raw</code> or <code>preload-template</code>		\|Maybe something like <code>preload-raw</code> or <code>preload-template</code>
			\| high
			\|-
			\| Auto-generation of schemes from imported data
			\| If data with no corresponding schema are imported, a schema should be created automatically - initially all fields could be defined as text fields and and can be customized later
			\| low
	\|-		\|-
	\|Excel like data input with sub-classes (automatic field generation)		\|Excel like data input with sub-classes (automatic field generation)
Line 238:		Line 246:
	\|} %		\|} %
	\|}		\|}
			\| high
	\|-		\|-
	\| Sorting function for multiple fields / sub-items		\| Sorting function for multiple fields / sub-items

Uschuetzenmeister at 15:21, 19 December 2025

2025-12-19T15:21:26Z

← Older revision		Revision as of 15:21, 19 December 2025
Line 71:		Line 71:
	In this template, I then query things and have them displayed. (See also https://topwayitworkspace.slack.com/archives/C075J025U87/p1763407201707529)		In this template, I then query things and have them displayed. (See also https://topwayitworkspace.slack.com/archives/C075J025U87/p1763407201707529)
	\|Maybe something like <code>preload-raw</code> or <code>preload-template</code>		\|Maybe something like <code>preload-raw</code> or <code>preload-template</code>
	\|
	\|-		\|-
	\|Excel like data input with sub-classes (automatic field generation)		\|Excel like data input with sub-classes (automatic field generation)

Uschuetzenmeister at 15:14, 19 December 2025

2025-12-19T15:14:47Z

← Older revision		Revision as of 15:14, 19 December 2025
Line 69:		Line 69:
	The main idea is: when I store data in the jsondata slot, I initially have no output in the main slot; the page is empty by default. Cargo outputs the data in a table by default, but I can also pass it on to a template.		The main idea is: when I store data in the jsondata slot, I initially have no output in the main slot; the page is empty by default. Cargo outputs the data in a table by default, but I can also pass it on to a template.
	In VisualData, I currently do it as follows: I use preload parameters to define a wrapper template that only contains the name of the output template.		In VisualData, I currently do it as follows: I use preload parameters to define a wrapper template that only contains the name of the output template.
	In this template, I then query things and have them displayed.		In this template, I then query things and have them displayed. (See also https://topwayitworkspace.slack.com/archives/C075J025U87/p1763407201707529)
	\|Maybe something like <code>preload-raw</code> or <code>preload-template</code>		\|Maybe something like <code>preload-raw</code> or <code>preload-template</code>
	\|		\|

Uschuetzenmeister at 15:14, 19 December 2025

2025-12-19T15:14:11Z

← Older revision		Revision as of 15:14, 19 December 2025
Line 70:		Line 70:
	In VisualData, I currently do it as follows: I use preload parameters to define a wrapper template that only contains the name of the output template.		In VisualData, I currently do it as follows: I use preload parameters to define a wrapper template that only contains the name of the output template.
	In this template, I then query things and have them displayed.		In this template, I then query things and have them displayed.
	\|Maybe something like <code>preload-raw</code>		\|Maybe something like <code>preload-raw</code> or <code>preload-template</code>
	\|		\|
	\|-		\|-

Uschuetzenmeister at 15:13, 19 December 2025

2025-12-19T15:13:16Z

@@ Line 21: / Line 21: @@
 ! style="width:50%" | Feature
 ! Comment
 |-
 |Ability to edit partial JSON blocks - it should be possible to insert nested sub-items, e.g., a reply to a reply to a reply to a comment. In other words, the JSON of the reply would have to be inserted at different levels so that the end result would be a tree like this:
@@ Line 53: / Line 64: @@
 </pre></code>
 |-
-|Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)
+|Possibilty to preload unparsed templates, i.e. '''<nowiki>{{abc}}</nowiki>''' should be saved as it is and not be parsed
 The parameter |preload=Template:abc in the schema definition currently works in such a way that the content of the template is written to the JSON. However, since multiple articles are usually created using forms, it would make more sense to write only the template name to the JSON (similar to the Cargo parameter ‘template’). At the moment, I have solved this by first calling a template as a wrapper, which in turn contains a template. However, this means that I have dozens of wrapper templates, which in my opinion are actually superfluous. Here is the discussion that has already taken place on this topic: https://www.mediawiki.org/wiki/Extension_talk:VisualData#General_thoughts_on_the_preload_parameter

Uschuetzenmeister at 15:12, 19 December 2025

2025-12-19T15:12:07Z

← Older revision		Revision as of 15:12, 19 December 2025
Line 70:		Line 70:
	In VisualData, I currently do it as follows: I use preload parameters to define a wrapper template that only contains the name of the output template.		In VisualData, I currently do it as follows: I use preload parameters to define a wrapper template that only contains the name of the output template.
	In this template, I then query things and have them displayed.		In this template, I then query things and have them displayed.
	\|Maybe something like <code>\|preload-raw</code>		\|Maybe something like <code>preload-raw</code>
	\|		\|
	\|-		\|-

Uschuetzenmeister at 15:11, 19 December 2025

2025-12-19T15:11:41Z

← Older revision		Revision as of 15:11, 19 December 2025
Line 63:		Line 63:
	\|template=Person card{{!}}MY_ADDITIONAL_PARAMETER		\|template=Person card{{!}}MY_ADDITIONAL_PARAMETER
	}}</pre></code>		}}</pre></code>
			\|-
			\|Possibilty to preload unparsed templates, i.e. {{abc}} should be saved as it is and not be parsed
			The parameter \|preload=Template:abc in the schema definition currently works in such a way that the content of the template is written to the JSON. However, since multiple articles are usually created using forms, it would make more sense to write only the template name to the JSON (similar to the Cargo parameter ‘template’). At the moment, I have solved this by first calling a template as a wrapper, which in turn contains a template. However, this means that I have dozens of wrapper templates, which in my opinion are actually superfluous. Here is the discussion that has already taken place on this topic: https://www.mediawiki.org/wiki/Extension_talk:VisualData#General_thoughts_on_the_preload_parameter

			The main idea is: when I store data in the jsondata slot, I initially have no output in the main slot; the page is empty by default. Cargo outputs the data in a table by default, but I can also pass it on to a template.
			In VisualData, I currently do it as follows: I use preload parameters to define a wrapper template that only contains the name of the output template.
			In this template, I then query things and have them displayed.
			\|Maybe something like <code>\|preload-raw</code>
			\|
	\|-		\|-
	\|Excel like data input with sub-classes (automatic field generation)		\|Excel like data input with sub-classes (automatic field generation)

Uschuetzenmeister at 15:05, 19 December 2025

2025-12-19T15:05:49Z

@@ Line 21: / Line 21: @@
 ! style="width:50%" | Feature
 ! Comment
 |-
 |Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)

Uschuetzenmeister at 15:01, 19 December 2025

2025-12-19T15:01:30Z

← Older revision		Revision as of 15:01, 19 December 2025
Line 23:		Line 23:
	\|-		\|-
	\|Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)		\|Possibilty to pass additional parameters in a VisualData query when the result format template is selected (possible with Cargo)
	\|<code>{{#visualdataquery:~~<nowiki>~~[[last name::+]]~~</nowiki></code><code><nowiki>~~\|?first names~~</nowiki></code><code><nowiki>~~\|?last name~~</nowiki></code><code><nowiki>~~\|?position~~</nowiki></code><code><nowiki>~~\|?email~~</nowiki></code><code><nowiki>~~\|schema=Person data~~</nowiki></code><code><nowiki>~~\|format=template~~</nowiki></code><code><nowiki>~~\|template=Person card{{!}}MY_ADDITIONAL_PARAMETER~~</nowiki></code><code><nowiki>~~}}</~~nowiki~~></code>		\|<code><pre>{{#visualdataquery:[[last name::+]]
			\|?first names
			\|?last name
			\|?position
			\|?email
			\|schema=Person data
			\|format=template
			\|template=Person card{{!}}MY_ADDITIONAL_PARAMETER
			}}</pre></code>
	\|-		\|-
	\|Excel like data input with sub-classes (automatic field generation)		\|Excel like data input with sub-classes (automatic field generation)