<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New Feature: Participant Filtering</title>
	<atom:link href="http://www.loop11.com/participant-filtering/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.loop11.com/participant-filtering/</link>
	<description>Online Usability Testing Tool</description>
	<lastBuildDate>Wed, 07 Dec 2011 04:31:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: hstetter</title>
		<link>http://www.loop11.com/participant-filtering/comment-page-1/#comment-2048</link>
		<dc:creator>hstetter</dc:creator>
		<pubDate>Fri, 23 Jul 2010 05:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.loop11.com/blog/?p=254#comment-2048</guid>
		<description>It&#039;s being rolled out over a few weeks. The feature to filter participants who partially completed user tests is already available and there are 2 more ways of filtering and segmenting participants which will be rolled out this coming week.</description>
		<content:encoded><![CDATA[<p>It&#8217;s being rolled out over a few weeks. The feature to filter participants who partially completed user tests is already available and there are 2 more ways of filtering and segmenting participants which will be rolled out this coming week.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristina</title>
		<link>http://www.loop11.com/participant-filtering/comment-page-1/#comment-2044</link>
		<dc:creator>Kristina</dc:creator>
		<pubDate>Thu, 15 Jul 2010 22:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.loop11.com/blog/?p=254#comment-2044</guid>
		<description>Great news!  Do you have an ETA on when you think that feature will be available?</description>
		<content:encoded><![CDATA[<p>Great news!  Do you have an ETA on when you think that feature will be available?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hstetter</title>
		<link>http://www.loop11.com/participant-filtering/comment-page-1/#comment-2033</link>
		<dc:creator>hstetter</dc:creator>
		<pubDate>Fri, 09 Jul 2010 06:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.loop11.com/blog/?p=254#comment-2033</guid>
		<description>At the moment the only way to do this is for us to do it for you, which we are more than happy to do (email: support at Loop11.com with the participant number and we can do it).  However, we are currently developing a feature that will enable you to delete individual participants in situations like this.</description>
		<content:encoded><![CDATA[<p>At the moment the only way to do this is for us to do it for you, which we are more than happy to do (email: support at Loop11.com with the participant number and we can do it).  However, we are currently developing a feature that will enable you to delete individual participants in situations like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristina</title>
		<link>http://www.loop11.com/participant-filtering/comment-page-1/#comment-2032</link>
		<dc:creator>Kristina</dc:creator>
		<pubDate>Fri, 09 Jul 2010 03:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.loop11.com/blog/?p=254#comment-2032</guid>
		<description>Is there currently way to delete one participants data from your survey if they skew the results? For example, if 12 people take our test and 1 of them really skews the data, can we delete that 1 person only and only upload the data from the other 11 users?</description>
		<content:encoded><![CDATA[<p>Is there currently way to delete one participants data from your survey if they skew the results? For example, if 12 people take our test and 1 of them really skews the data, can we delete that 1 person only and only upload the data from the other 11 users?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

