Features-test

Various test queries that were or could be on

• Feature roadmap
• 9.1.0 requirements

Enables a dynamic Feature roadmap — see Semantic MediaWiki#For software features.

Querying software features

What to query

Features are in subcategories of Category:Software features, but querying on this matches many pages that aren't software features, because some feature subcategories such as Category:Network and Category:Network are already in use.

{{Feature tracking}} sets some other properties like Property:Is part of, so the trick is to pick one that is specified (not blank or default) in all software features. Probably Property:Is part of is safest.

That gives us {{#ask: Is part of::+

 |format=count

}} software features (a few may be tests).

So use | limit=200 | in queries to display all the features.

Result format

You could regenerate the old huge feature roadmap page by using | format=embed | , which would bring all the subpages back. But you're back to a large unwieldy page.

You could use a results display template to shorten some links (e.g. show the short name in the link to the subpage), but you lose the clickable column headings.

To avoid repeating the Software feature subcategory on each line, repeat the query for each subcategory and don't display it.

Creating a new feature

1. Make sure the feature doesn't already exist
2. Read the Usage section of Template:Feature tracking for help filling out the template on the new page
3. Pick an "Feature subcategory" from Category:Software features
4. Find the requester(s)' wiki pages and the feature owner's User: wiki page
5. Follow the OLPC:Style guide for page names, change Good feature name to your new subpage title.
6. Ready? Click the button below to create a new meeting wikipage with the right title convention that's prefilled from Template:Feature tracking/Preload, edit it to suit, then save. After a delay (due to wiki query and page caching), your new subpage will appear in lists of features.

<inputbox> type=create preload=Template:Feature tracking/Preload buttonlabel=Create a new Feature roadmap subpage. default=Feature roadmap/Good feature name width=40 bgcolor=#f0f0ff </inputbox>

Default query ("Greg list")

The template's "Feature subcategory" parameter both sets a category and Property:Is part of. We can sort by the latter to present features by category.

This will replace section 2 of Feature roadmap Click on the arrows in any heading to sort by that heading. {{#ask: Is part of::+

 |?Is part of=Area
 |?=Feature page
 |?Requested by=Requested by
 |?Helps deployability#y,n
 |?Target for 9.1#yes,no
 |?Contact person=Owner(s)
 |?Priority
 |sort=Is part of
 |mainlabel=-
 |limit=200
 |default=Nothing found in Category:Software features with Property:Is part of?!

}}

Before you ask, you can't ask for "grouping" of results to avoid area repeated over and over; instead you would repeat the query each time querying for a different areas or subcategory.

Sort by area, then priority, then name

Sorting on a property implicitly selects pages with a value for it, so this won't display a lot of subpages until every page has a priority. Click on the arrows in any heading to sort by that heading. {{#ask: Short name::+

 |?Is part of=Area
 |?=Feature page
 |?Requested by
 |?Helps deployability
 |?Target for 9.1
 |?Contact person=Owner(s)
 |?Priority
 |sort=Is part of,Priority, Short name
 |order=ascending,descending, ascending
 |mainlabel=-
 |limit=200
 |default=Nothing found in Category:Software features with Property:Short name?!

}}

Features for 9.1.0

Just query for Property:Target for 9.1 set to yes. BUT: Because this property has a dot (period, "full stop") in its name, it looks like the trick SMW feature "property chaining". As the help says

"In the rare case that a property should contain a dot in its name, one may start the query with a space to prevent SMW from interpreting this dot in a special way."

Summary table

This query sorts by area, then priority, then Short name, so it only finds pages that have values for those properties.

{{#ask: Target for 9.1::true

 |?Is part of=Area
 |?=Feature page
 |?Requested by
 |?Helps deployability#yes,no
 |?Contact person=Owner(s)
 |?Priority  |sort=Is part of,Priority, Short name
 |mainlabel=-
 |limit=200
 |default=Nothing found in Category:Software features with Property:Target for 9.1=true?!

}}

Embedded

Use format=embed to include entire pages matching a query for Property:Target for 9.1 set to yes. Here it's limited to 3 matches because it's confusing. Problem is: embedding a page also pulls in its categorization; we can wrap that with noinclude but can't get this to work in a preload template.

This is better done as a separate, linked page, see Feature roadmap/Page of all features that target 9.1.0

{{#ask: Target for 9.1::true +

 |format=embedded
 |embedformat=h4
 |limit=3
 |default=Nothing found in Category:Software features with Property:Target for 9.1=true?!

}}

What features did a country request?

Query for ([[Requested by::{{FULLPAGENAME}}]]), e.g. here's one showing what OLPC Peru requested. {{#ask:

 Requested by::OLPC Peru
 |mainlabel=OLPC Peru wants
 |?Category
 |?Is part of=Technology/subsystem
 |?Target for 9.1
 |?Requested by
 |default=Nothing found in Category:Software features requested by Features-test

}}

Other sample queries

Features showing category list

This queries for anything in Category:Software features, it shows category to try to show feature. (Only displays 10 results.) {{#ask: Is part of::+

 |?Category=in the following categories
 |?Requested by
 |limit=10
 |default=Nothing found in Category:Software features with Property:Is part of?!

}}

But, as you see below you can't sort on category display! Maybe have to have Property:Feature subcategory, like Property:Test subcategory, or use Is part of::Power management, Is_part_of::Journal , etc. {{#ask: Is part of::+

 |?Category
 |?Requested by
 |sort=Category
 |limit=10
 |default=Nothing found in Category:Software features with Property:Is part of when we try to sort by Category.

}}