-getusrstrs template: ster?clnt=<name|pass>&com=getusrstrs&usr=<usr_pattern>&str=<str_pattern>[&num= <num_pattern>&srt=<order_pattern>] Order of query params is not important. Query params 'num', and 'srt' are optional. If ommited, 'num' defaults to '*', and 'srt' defaults to 'desc'. pattern : for stereotypes, * | name, name can be a path expression (group1.*) for users, * | name, name can be a path expression (group1.*) For num, * | <integer>. For srt, asc | desc. For 10->1 use 'desc'. descript: for each user matching usr_pattern, the stereotypes matching str_pattern are found and sorted according to degree (based on 'srt'), and secondarily according to stereotype name (asc, A->Z). Then the first <num_pattern> rows are selected (or all, if <num_pattern> is '*') and an XML answer is formed. If no stereotype in DB matches the pattern or if <num_pattern> <=0 or if the user does not exist, the result will not have any 'row' elements (200 OK will still be returned). Note that 'srt' affects the sorting on degree. Sorting is primarily based on numeric values (doubles) of field 'su_degree', which may also contain NULLs in some records. Note that in case a number of stereotypes matching the pattern have the same degree, some of them may be part of the results, while others not. This depends on 'num', which determines in absolute terms the number of result rows. Which of the stereotypes with the same value will be part of the result depends on the stereotype name, which is a secondary field of ordering. example : ster?clnt=name|pass&com=getusrstrs&usr=eddie&str=*&num=3 ster?clnt=name|pass&com=getusrstrs&usr=group1.*&str=visitor returns : 200 OK, 401 (fail, request error), 501 (fail, server error) 200 OK : in this case the response body is as follows <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="/resp_xsl/stereot_singleuser.xsl"?> <result> <row><usr>user</usr><str>stereotype</str><deg>degree</deg></row> ... </result>