 




<?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: Limited Number Of Documents In A View.</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/limited-number-of-documents-in-a-view/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/limited-number-of-documents-in-a-view/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 18:28:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: mglist</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/limited-number-of-documents-in-a-view/#comment-98269</link>
		<dc:creator>mglist</dc:creator>
		<pubDate>Wed, 26 Oct 2011 17:39:10 +0000</pubDate>
		<guid isPermaLink="false">#comment-98269</guid>
		<description><![CDATA[Thanks to all that responded with ideas.

I created a view with the priority field in the first column sorted high to low.  The second column used the simple function, # in View, so that it showned 1,2,3...etc.  The manager insisted that he only wanted to see the top 25 and nothing more.  You know how some people can be?

I discuss the agent and a nightly update routine with the manager and explained with this method I could limit the documents in the view to be exactly 25.  I also offered to have the agent run more often if it was necessary.  He agreed to this solution and would see if once a day would serve his needs.  So that is what I will do.

I was hoping for a simpler solution, but it is what it is.  Again, thanks for all the help.

Mglist]]></description>
		<content:encoded><![CDATA[<p>Thanks to all that responded with ideas.</p>
<p>I created a view with the priority field in the first column sorted high to low.  The second column used the simple function, # in View, so that it showned 1,2,3&#8230;etc.  The manager insisted that he only wanted to see the top 25 and nothing more.  You know how some people can be?</p>
<p>I discuss the agent and a nightly update routine with the manager and explained with this method I could limit the documents in the view to be exactly 25.  I also offered to have the agent run more often if it was necessary.  He agreed to this solution and would see if once a day would serve his needs.  So that is what I will do.</p>
<p>I was hoping for a simpler solution, but it is what it is.  Again, thanks for all the help.</p>
<p>Mglist</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sliktool</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/limited-number-of-documents-in-a-view/#comment-98266</link>
		<dc:creator>sliktool</dc:creator>
		<pubDate>Wed, 26 Oct 2011 15:49:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-98266</guid>
		<description><![CDATA[@Mglist - an agent will work, nightly if you choose and thus a view will work. My recommendation was based on the assumption (always dangerous I know) that this Top 25 had to always be up to date.  If it can wait nightly, or even every 4 hours or so, an agent is likely the safe route.

A side thought though, is a view sorted by by the date time of being added to the Top 25 (so flag for Top 25, and flag for when it was set).  The only issue is, the view will likely have more than 25 in the view at different times of the day, but you could purge the older ones (based on the &quot;added to Top 25&quot; field) hourly without likely causing an issue.

Think that might work?]]></description>
		<content:encoded><![CDATA[<p>@Mglist &#8211; an agent will work, nightly if you choose and thus a view will work. My recommendation was based on the assumption (always dangerous I know) that this Top 25 had to always be up to date.  If it can wait nightly, or even every 4 hours or so, an agent is likely the safe route.</p>
<p>A side thought though, is a view sorted by by the date time of being added to the Top 25 (so flag for Top 25, and flag for when it was set).  The only issue is, the view will likely have more than 25 in the view at different times of the day, but you could purge the older ones (based on the &#8220;added to Top 25&#8243; field) hourly without likely causing an issue.</p>
<p>Think that might work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ledlincoln</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/limited-number-of-documents-in-a-view/#comment-98260</link>
		<dc:creator>ledlincoln</dc:creator>
		<pubDate>Wed, 26 Oct 2011 14:18:02 +0000</pubDate>
		<guid isPermaLink="false">#comment-98260</guid>
		<description><![CDATA[Mglist, I think you&#039;re on the right track.  A nightly agent can set or reset the priority field on each document.  An even simpler option would be for the manager to just look at the top 25 docs in a priority-sorted view.  :-)]]></description>
		<content:encoded><![CDATA[<p>Mglist, I think you&#8217;re on the right track.  A nightly agent can set or reset the priority field on each document.  An even simpler option would be for the manager to just look at the top 25 docs in a priority-sorted view.  <img src='http://itknowledgeexchange.techtarget.com/itanswers/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mglist</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/limited-number-of-documents-in-a-view/#comment-98215</link>
		<dc:creator>mglist</dc:creator>
		<pubDate>Tue, 25 Oct 2011 17:26:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-98215</guid>
		<description><![CDATA[Thank you SlikTool for your response.  We may have 200 to 300 projects active at any one time and priorities changing based upon the customer&#039;s needs.  So to recreated the folder each time a document is updated would be a lot of overhead.  I was kind of hoping there was a parameter that could be set, or a view formula that would manage the amount of documents displayed.  I think that I may have to write an agent in LotusScript that would evalute whether the document is in the top 25 and set a hidden field on the document to yes or no.  Then use that field value in the view selection formula.  If you know of a different way, please let me know.  Thanks for your help.]]></description>
		<content:encoded><![CDATA[<p>Thank you SlikTool for your response.  We may have 200 to 300 projects active at any one time and priorities changing based upon the customer&#8217;s needs.  So to recreated the folder each time a document is updated would be a lot of overhead.  I was kind of hoping there was a parameter that could be set, or a view formula that would manage the amount of documents displayed.  I think that I may have to write an agent in LotusScript that would evalute whether the document is in the top 25 and set a hidden field on the document to yes or no.  Then use that field value in the view selection formula.  If you know of a different way, please let me know.  Thanks for your help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.037 seconds using memcached
Object Caching 313/319 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-21 19:02:36 -->