Ah ha!
That helps! Thanks! I also had spaces in my assignment, which was giving me issues when querying.
Thanks!
--Ryan
On Feb 22, 2013, at 11:29 AM, Yaron Koren wrote:
> Hi,
>
> I think you still don't fully understand the subobject concept - it's supposed to mimic a page, without actually being a page. Anyway, now I think I understand what you meant by "(download link)", plus that semicolon syntax (which you should avoid entirely - that comes from the Record type, which #subobject replaces), so let's try that again:
>
> {{#subobject:
> | Driver for = {{PAGENAME}}
> | OS = Windows 2008 x64
> | Version = x.x.x.x
> | Download link = (Download link)
> }}
> {{#subobject:
> | Driver for = {{PAGENAME}}
> | OS = Windows 2008 x86
> | Version = y.y.yy
> | Download link = (Download link)
> }}
>
> The property names might be off, but hopefully you get the basic idea.
>
> Then, to get all the drivers for, say, QLogic HBA, and their info, you could call:
>
> {{#ask:[[Driver for::QLogic HBA]] |?OS |?Version |?Download link}}
>
> =Yaron
>
> On Fri, Feb 22, 2013 at 11:12 AM, Ryan Glasnapp <ryan.glasnapp@...> wrote:
> Hmmm,
>
> The problem is that since it's technical documentation we don't have a page on a specific driver itself. We have documentation on how to Install a QLogic HBA driver, or how to Upgrade a driver, but not a page dedicated to just the driver itself.
>
> Originally my thought was to have a page (ostensibly the main page for the team that uses these drivers) dedicated to storing all of the sub objects and then query that page for a particular driver type, and then pull out the specific OS versions from the resulting records.
>
> I don't think that's a realistic way to do it anymore based on what I'm seeing here, but how would you actually design a query to get the revision number and download link out of the record even if it's on a separate page for each driver? That's really the issue I'm having here.
>
> (The download link is just a link to where to get the driver from, nothing special there).
>
> --Ryan
>
> On Feb 22, 2013, at 10:52 AM, Yaron Koren wrote:
>
>> Hi Ryan,
>>
>> Looking at your initial example call again, I think you may have misinterpreted how subobjects work. You had this:
>>
>> {{#subobject:QLogic HBA Drivers
>> | Software name = QLogic HBA Drivers
>> | Firmtype = Windows 2008 x64;x.x.x.x;(Download link)
>> | Firmtype = Windows 2008 x86;y.y.yy;(Download link)
>> }}
>>
>> This is meant to go on a page called "QLogic HBA" or something, right? If so, then what you should have had instead is:
>>
>> {{#subobject:
>> | Driver for = {{PAGENAME}}
>> | Firmtype = Windows 2008 x64;x.x.x.x;(Download link)
>> }}
>> {{#subobject:
>> | Driver for = {{PAGENAME}}
>> | Firmtype = Windows 2008 x86;y.y.yy;(Download link)
>> }}
>>
>> (I don't understand what the "Download link" part is for, but that's a separate story.) The basic idea is, each "entity" (in this case, a driver) has its own subobject. And each #subobject call should include a link to the page on which it was called, in my opinion, to allow for easy querying.
>>
>> -Yaron
>>
>>
>> On Fri, Feb 22, 2013 at 9:27 AM, Ryan Glasnapp <ryan.glasnapp@...> wrote:
>> Ok, I can try that out.
>>
>> I was planning on using templates, and Semantic Forms, I just wanted to get the base code working first.
>>
>> Now, how do you actually query that? That's the *real* problem I was running into.
>>
>> --Ryan
>>
>>
>> --
>> WikiWorks · MediaWiki Consulting · http://wikiworks.com
>
>
>
>
> --
> WikiWorks · MediaWiki Consulting · http://wikiworks.com
|