Re: [mashup-dev] Search.jsp query param docs

[Upendra Prasad Haputantry]

Now activity search is unified with the query parameters. Currently creation and deletion is not included.  Parameter Applies Meaning query Optional An enumeration of the query type.  Currently supported values are “allmashups”, “mymashups”, “topmashups”, “mytopmashups”, “activity”,and “custom”. activityScope Optional(default null) A username with which to limit the scope of the search. period Optional(default 30 days) Limit the results for more recent activities. filter Optional(default -1) Filter the query for All (value -1) Comments (value -2) Taggings (value -3) Ratings (value -4) Thanks -Prasad Jonathan Marsh wrote: Perhaps also allowing “for” to appear on comments queries?  This would help you find a comment where you remember some phrase but not where the comment appeared.   Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jonathan Marsh Sent: Friday, November 30, 2007 3:10 PM To: mashup-dev@wso2.org Subject: [mashup-dev] Search.jsp query param docs   Thought I’d better document the existing query params as a reference as we extend the searching capability.  I also want to clean up the query params as there are some inconsistent usages.   Parameter Applies Meaning query Optional An enumeration of the query type.  Currently supported values are “allmashups”, “mymashups”, “topmashups”, “mytopmashups”, and “custom”. for Required for “custom” queries.  One of tags, titles, descriptions must be true. String to search for within tags, titles, descriptions. tags Optional (default false) true|false: whether to search for tags with the value of “for” titles Optional (default false) true|false: whether to search titles containing the value of “for” descriptions Optional (default false) true|false: whether to search descriptions containing the value of “for” scope Required for “mymashups” and “mytopmashups”.  Optional for “custom”.  Ignored otherwise. A username with which to limit the scope of the search. controls Optional (default true) true|false: whether to show the advanced search controls in an expanded state.  When using the search page to show the results of a query (e.g. a query link), typically the controls=false.  When the page is accessed for purposes of creating a query, controls=true (or omitted.) format Optional rss|atom: whether to format the results as an RSS or ATOM feed instead of an HTML page.   I haven’t documented the Activity Search parameters because what’s in the UI and what’s in the code doesn’t seem to match.  And I’m about to propose we unify that with the “query” param anyway.   Suggested changes:   1)      Drop the “mymashups” and “mytopmashups” query types.  Instead use “allmashups” and “topmashups” with the scope parameter (this is how “custom” works now. 2)      Add “activity” to the query type enumeration.  Add a new optional parameter “period” which will take values like 30 (30 days), 180 (six months), etc. to filter the activity queries.  The existing “scope” parameter, if specified, can limit the search to activities by a particular user.  Activity queries will show changes to mashups including creation and deletion, and rating, tagging, and commenting activity. 3)      Add “comments” to the query type enumeration.  Add a new optional parameter “mashup” which will name a mashup (path?) to filter the results.  Allow the parameters “period” and “scope” to apply to this query type.   Thoughts?   Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com   _______________________________________________ Mashup-dev mailing list Mashup-dev@wso2.org http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev

_______________________________________________
Mashup-dev mailing list
Mashup-dev@wso2.org
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev