<?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: SharePoint Folders vs Metadata&#8230; the ultimate battle!</title>
	<atom:link href="http://stovereffect.com/2010/07/12/metadata-versus-folders/feed/" rel="self" type="application/rss+xml" />
	<link>http://stovereffect.com/2010/07/12/metadata-versus-folders/</link>
	<description>John Stover. Entrepreneur. Consultant. Author. Speaker. Mentor. Strategist. Expert.</description>
	<lastBuildDate>Wed, 07 Dec 2011 09:10:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Filip</title>
		<link>http://stovereffect.com/2010/07/12/metadata-versus-folders/comment-page-1/#comment-6104</link>
		<dc:creator>Filip</dc:creator>
		<pubDate>Tue, 05 Apr 2011 08:19:21 +0000</pubDate>
		<guid isPermaLink="false">http://stovereffect.com/?p=157#comment-6104</guid>
		<description>I agree that good taxonomy / semantics are even more important than setting up the correct folders. 

Would it be possible to implement row level security based on a pivot table form an other system.

1) Items have a customer ID (lots of items in 1 list)
2) In an external system customer ID is matched to an affiliate ID (changes regulary)
3) Add a custom column that is filled with the lookup for the Affiliate
4) Only Items for teh correct Affiliate are shown

For users working on corporate level all items are visible with the possibility to filter on affiliate level.</description>
		<content:encoded><![CDATA[<p>I agree that good taxonomy / semantics are even more important than setting up the correct folders. </p>
<p>Would it be possible to implement row level security based on a pivot table form an other system.</p>
<p>1) Items have a customer ID (lots of items in 1 list)<br />
2) In an external system customer ID is matched to an affiliate ID (changes regulary)<br />
3) Add a custom column that is filled with the lookup for the Affiliate<br />
4) Only Items for teh correct Affiliate are shown</p>
<p>For users working on corporate level all items are visible with the possibility to filter on affiliate level.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://stovereffect.com/2010/07/12/metadata-versus-folders/comment-page-1/#comment-566</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Sun, 03 Oct 2010 11:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://stovereffect.com/?p=157#comment-566</guid>
		<description>This topic is very interesting I would like to see an article on using folders and still using an effective metadata structure.  Because from this it sounds like you would have one document library upload all contents into the root of that library than use views and columns to sort data. Also you would require the user to actually tag the document before it is uploaded thus building up metadata that will be beneficial to better search results with enterprise search




Even if you elect to use folders, you should still use an effective metadata structure.</description>
		<content:encoded><![CDATA[<p>This topic is very interesting I would like to see an article on using folders and still using an effective metadata structure.  Because from this it sounds like you would have one document library upload all contents into the root of that library than use views and columns to sort data. Also you would require the user to actually tag the document before it is uploaded thus building up metadata that will be beneficial to better search results with enterprise search</p>
<p>Even if you elect to use folders, you should still use an effective metadata structure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

