Last modified: 2011-08-30 07:17:56 UTC
We already get property data in the factbox, which is very handy for developing, maintaining, and using a semantic mediawiki. All that remains to be added is information about categories, templates, and forms that are used for the page. Likewise, categories, templates, and forms could also have information about which of those three things go into defining them (like if a template is created by a form, or if a category is contained in a template).
I have been able to manually add these features to this page (user Demo, pass dedauw):
Wiki developers, maintainers, and users can easily access the categories, templates, and forms that go into creating that page, all in place. In addition, I'm able to query the semantic data to display on the template page which pages are using the template:
The nature of these things makes it straightforward to add them manually once, and then use them unlimited numbers of times. However, if the properties "Category", "Template", and "Form" were part of the metadata of each page, they could be displayed in the factbox that already handles other properties.
Also, my factboxes do not show special metadata properties like the "Modification date" property that currently exists - this should be at least optional, if not the default).
See also: https://bugzilla.wikimedia.org/show_bug.cgi?id=13151
*** Bug 13151 has been marked as a duplicate of this bug. ***
You reported the "need for more special properties" in 3 different bug reports, please stick with 1. As Markus suggests in bug 13151, this is material for an extension, ie not for SMW itself.
> Also, my factboxes do not show special metadata properties like the
"Modification date" property that currently exists - this should be at least
optional, if not the default).
Having this as an option would be neat indeed - valid enhancement request.
Should that final valid factbox enhancement request be put into its own report, and this one marked as resolved/wontfix?
That would be nice yes.
Closed this bug, and made a new one that's specific to the one aspect of this bug that was distilled out: