Semantic MediaWiki: Difference between revisions
From CoMakingSpace Wiki
(saw cutting depth experiment) |
(→Cheat Sheet: unions of results (OR)) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* [https://github.com/comakingspace/do-something/issues/130 giving equipment pages properties like "Tutor::" and "Location::"] so they can easily be listed accordingly | * [https://github.com/comakingspace/do-something/issues/130 giving equipment pages properties like "Tutor::" and "Location::"] so they can easily be listed accordingly | ||
* integrating properties for images into InfoBoxes as a potential way to auto-generate {{NavGal}}s | * integrating properties for images into InfoBoxes as a potential way to auto-generate {{NavGal}}s | ||
** first experiment: [[Metal Workshop/Gallery]] | ** first experiment: [[Metal Workshop/Gallery]] (grabbing HasImage and HasCaption from [[MachineInfoBox]]es and [[ToolInfoBox]]es) | ||
* making [[projects]] listable by their InfoBox dates with [[Property:ProjectDate]] | |||
* experimental: adding interesting property tables for tool types such as [[Saws#Saw_Selection_(experimental)|cutting depths for saws]] | * experimental: adding interesting property tables for tool types such as [[Saws#Saw_Selection_(experimental)|cutting depths for saws]] | ||
* ''what else can you think of?'' | * ''what else can you think of?'' | ||
| Line 17: | Line 18: | ||
*** alternatively, you could enter <code>| </code> (the space is important!) to the end of a property (e.g. <code><nowiki>[[Has demo::test| ]]</nowiki></code>) which ''might'' be necessary in certain template elements | *** alternatively, you could enter <code>| </code> (the space is important!) to the end of a property (e.g. <code><nowiki>[[Has demo::test| ]]</nowiki></code>) which ''might'' be necessary in certain template elements | ||
* [https://www.semantic-mediawiki.org/wiki/Help:Result_formats list of possible '''result formats'''] (e.g. table or gallery) | * [https://www.semantic-mediawiki.org/wiki/Help:Result_formats list of possible '''result formats'''] (e.g. table or gallery) | ||
* [https://www.semantic-mediawiki.org/wiki/Help:Property_page/Filter how to '''filter''' for values on property pages] | |||
* [https://www.semantic-mediawiki.org/wiki/Help:Unions_of_results unions of results] - how to use "OR" instead of the (assumed) "AND" between two queries | |||
** useful to make our [[MachineInfoBox]] find Tutors for Introductions to the "type" OR the "machine name", for example | |||
** can also be used to embed machines of different types into the same page (if we want to do that) | |||
[[Category:Software]] | [[Category:Software]] | ||
[[Category:Wiki]] | [[Category:Wiki]] | ||
Latest revision as of 01:06, 4 September 2022
We started using Semantic MediaWiki (SMW) for some "smart" functions of this wiki around June 2019. Feel free to join the effort!
How we use it so far:
- giving equipment pages properties like "Tutor::" and "Location::" so they can easily be listed accordingly
- integrating properties for images into InfoBoxes as a potential way to auto-generate navigation gallerys
- first experiment: Metal Workshop/Gallery (grabbing HasImage and HasCaption from MachineInfoBoxes and ToolInfoBoxes)
- making projects listable by their InfoBox dates with Property:ProjectDate
- experimental: adding interesting property tables for tool types such as cutting depths for saws
- what else can you think of?
Cheat Sheet
This is not supposed to replace the SMW documentation, but some things are nice to remember/share once you've finally found them:
- Special:Ask - "sandbox" page for SMW queries (help)
- lets you practice selecting pages with auto-complete of parameters
- assigning properties
- in-text annotation:
[[Property::value]](only "value", or its|alt text, is displayed) - hidden annotation: use the set function
- alternatively, you could enter
|(the space is important!) to the end of a property (e.g.[[Has demo::test| ]]) which might be necessary in certain template elements
- alternatively, you could enter
- in-text annotation:
- list of possible result formats (e.g. table or gallery)
- how to filter for values on property pages
- unions of results - how to use "OR" instead of the (assumed) "AND" between two queries
- useful to make our MachineInfoBox find Tutors for Introductions to the "type" OR the "machine name", for example
- can also be used to embed machines of different types into the same page (if we want to do that)
