<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>openRevit &#187; worksharing</title>
	<atom:link href="http://openrevit.com/tag/worksharing/feed/" rel="self" type="application/rss+xml" />
	<link>http://openrevit.com</link>
	<description>discussions on buildings, energy, software and all things bim</description>
	<lastBuildDate>Wed, 09 May 2012 20:23:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Mythbusters Part II: Worksets</title>
		<link>http://openrevit.com/2009/11/mythbusters-part-ii-worksets/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mythbusters-part-ii-worksets</link>
		<comments>http://openrevit.com/2009/11/mythbusters-part-ii-worksets/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 14:00:33 +0000</pubDate>
		<dc:creator>Alan Jackson</dc:creator>
				<category><![CDATA[Mythbusters]]></category>
		<category><![CDATA[Revit]]></category>
		<category><![CDATA[worksets]]></category>
		<category><![CDATA[worksharing]]></category>

		<guid isPermaLink="false">http://openrevit.com/?p=66</guid>
		<description><![CDATA[This post is going to focus on two things The overuse of worksets Controlling graphics WITHOUT worksets Too often I come across users who are immediately drawn to controlling visibility and graphical issues through the use of Worksets. Large teams devise diabolical plans on how they will split up the model into numerous worksets to allow for the integration of each teams design, or maybe to split up users so no one is stepping on each others toes. I admit, when back in the day I used to use worksets to check out work for individual users there would be a number of them to choose from. Finally I came to my senses and realized that there were a lot of issues with checking out worksets, and in fact element borrowing was the most efficient and effective way to work on large teams. Here is an excerpt from Autodesk on Worksets. While the capability to check out a workset remains valuable under certain circumstances outlined below, in general the best practice is to use element borrowing rather than checking out entire worksets. The Overuse of Worksets Simple point. Large teams should be using element borrowing and not setting up numerous &#8230; <a href="http://openrevit.com/2009/11/mythbusters-part-ii-worksets/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://openrevit.com/2009/11/mythbusters-part-ii-worksets/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

