Re: [Semediawiki-user] Inline query across multiple pages. [SEC=UNCLASSIFIED]

[Arber, B. (Contractor) <Ben...@ds...>]

Thanks again Patrick for your fast response.

I read the link on many-valued properties.  What I posted below was only
a summary of types of values we intend to keep.  For example, the
template for a 'test plan' has 20 properties and a 'coupon type' has 10
properties.  Currently they are created with a large form. Some of the
properties also use display units (which I read is not possible for
many-valued properties).  I believe my data set may be too complicated
for many-valued properties.


When a test is done on a coupon, it would be inconvenient to enter each
time the details of the test and the specifications of the coupon (it is
30 properties).  At the moment 'coupon type' and 'test type' are pages
that are linked from the 'coupon results' page.  This is ok but not
ideal and has severe limitations.(as in my previous question)

Is it possible (or a good idea) to include all the 'test data' and
'coupon type data'  on a coupon results page 'invisibly' (white font and
very small)?  That way the data would be included but not cause
confusion to users.  It would have to update when test details are
updated in the 'test form'.

Or, when doing queries is it possible to create a temporary page using
the data from the 'coupon results' as well as the data from pages listed
as the 'Test ID' and 'coupon type' properties on the 'coupon results'
form?


I guess I am trying to use the wiki more like a database.  It works to
an extent and is desirable because of the version control and
web-interface.  Are there other solutions I should be exploring? - I
have seen that there are some database-like extensions being developed
for semantic wiki, would any of these suit me?

Thanks
Ben



Re: [Semediawiki-user] Inline query across multiple pages.
</mailarchive/message.php?msg_name=4A5C40E9.1090405%40patrick-nagel.net>
From: Patrick Nagel <mail@pa...> - 2009-07-14 08:45
Hi,

On 2009-07-14 10:42, Arber, Benjamin (Contractor) wrote:
> Is it possible to make queries with results that come from different
> pages? For example, there are 3 pages
> 
> [Category: Coupon]
> Has Test ID (same as in 'Test ID' category)
> Has coupon type (same as in 'coupon type' category)
> Has Result
> Has Test date
> ...
> 
> [Category: Coupon Type]
> Has shape
> Has Material
> ...
> 
> [Category: Test ID]
> Has test name
> Has Test Description
> ...
> 
> I would like to make a table with
> Coupon, test name, result, date, shape and material.
> 
> I believe #ask queries only work to show data from one page.

I think your data (and/or data design) is unsuitable for SMW as it is.
"Coupon
type" and "Test ID" should probably just be many-valued properties [1],
that
get assigned their values in pages of the Coupon category. The problem
is, that
you can't (currently) get SMW to output many-valued properties in a
useful way.
Maybe someone else has other ideas...

> Also, When creating a query is it possible to have it in table format
> with a link to download to CSV? I can use 'format = csv' to create the
> link to download csv (thanks patrick for your help on that) but only
by
> rewriting the entire query twice eg,
> 
> ________________
> {{#ask: [[Category:Test plan V1]]
> | mainlabel=Test Plan ID
> | ?Test Title = Title
> | ?Test plan date = Date
> | ?Customer
> | ?Spectra
> | ?platform
> }}
> 
> Download as
> {{#ask: [[Category:Test plan V1]]
> | mainlabel=Test Plan ID
> | ?Test Title = Title
> | ?Test plan date = Date
> | ?Customer
> | ?Spectra
> | ?platform
> | format=csv
> }}

AFAIK there is no way around this... you could avoid some "code
duplication" by
using the VariablesExtension [2]. It would then look like this:

{{#vardefine:QUERY|[[Category:Test plan V1]]
| mainlabel=Test Plan ID
| ?Test Title = Title
| ?Test plan date = Date
| ?Customer
| ?Spectra
| ?platform}}

{{#ask: {{#var:QUERY}}
}}

Download as
{{#ask: {{#var:QUERY}}
| format=csv
}}

Patrick.

[1]: http://www.semantic-mediawiki.org/wiki/Help:Many-valued_properties
[2]: http://www.mediawiki.org/wiki/Extension:VariablesExtension

-- 
Key ID: 0x86E346D4 http://patrick-nagel.net/key.asc
Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4 



IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914.  If you have received this email in error, you are requested to contact the sender and delete the email.