From: Andreas M. <And...@an...> - 2010-04-21 12:56:30
|
Hello, semantic mediawiki experts and users, I am trying to manage the software-related knowledge of employees of my company using SMW in our internal wiki. I noticed that there is a new data type "record" in the new version of SMW. This is exactly what I need. Formerly I used Sematic Internal Objects, but I thought a built-in datatype might be better. Every employee is an expert for several knowledge areas. Each knowledge area has a category page in the wiki. I told my employees to write template calls on their wiki user pages, one for every knowledge area. For instance this could look like follows on page User:Andreas, the numbers meaning years of experience: {{Know-how | Oracle | 10 }} {{Know-how | DB2 | 3 }} {{Know-how | MySQL | 2 }} The template is something like [[Know-how::Category:{{{1}}};{{{2}}}]] As you can see, an attribute also named "Know-how" is used, which is of data type record, with two components of type page and number. This gives me a knowledge-profile for every employee, but I also want to query the wiki for employees with a certain knowledge. I try to do this on a category page as follows: {{#ask:[[Know-how::{{FULLPAGENAME}}]] |format=table |? Know-how|+index=1 |? Know-how|+index=2 }} I thought this should give a table of all employees with a given knowledge area. In fact it does, but it also lists all the other knowledge areas for the selected employees. For example, if I write this query on page Category:MySQL I get something like the following - I get only employees with knowledge for MySQL, but I get all their other knowledge areas as well. Andreas Oracle 10 DB2 3 MySQL 2 Patrick SQLServer 1 MySQL 2 Nico MySQL 4 ... Is this behaviour by design? If yes, is there a way to suppress the irrelevant entries (the ones with a value other than MySQL in the second column - I would not need this column then any more)? Kind regards Andreas |