<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Breaking up a Large Project in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Breaking-up-a-Large-Project/m-p/218165#M58534</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;So I'm trying to figure out the best way to break apart a large team work file and here are some of the issues that I dealing with.&lt;BR /&gt;
&lt;BR /&gt;
This is all based on the fact that this project is approaching 900mb as a teamwork file (this worries me).&lt;BR /&gt;
&lt;BR /&gt;
1st Method:  Extract the layout book into a separate team work file.&lt;BR /&gt;
&lt;BR /&gt;
issues:&lt;BR /&gt;
a)  The detail markers can't be set to the outside layout book file automatically.  If you could open a detail marker or any marker inside the model file and link it to a location on a sheet within Layout Book file.&lt;BR /&gt;
&lt;BR /&gt;
2nd Method:  Create PMK's&lt;BR /&gt;
&lt;BR /&gt;
issues:&lt;BR /&gt;
a) Can not do this quickly, or in a batch method through the drawing manager.   You must go through each drawing one by one and link it to the PMK that you want.  The only options are to link to a solo project or teamwork project.  We could probably create a file with PMK's that are connected to that some how?  Though that sounds a little complicated to manage.&lt;BR /&gt;
b) Does produce a noticeable smaller PDF file and the files are so much more light weight, and agile.&lt;BR /&gt;
&lt;BR /&gt;
What am I missing?&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 26 May 2023 14:37:17 GMT</pubDate>
    <dc:creator>ares997</dc:creator>
    <dc:date>2023-05-26T14:37:17Z</dc:date>
    <item>
      <title>Breaking up a Large Project</title>
      <link>https://community.graphisoft.com/t5/Documentation/Breaking-up-a-Large-Project/m-p/218165#M58534</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;So I'm trying to figure out the best way to break apart a large team work file and here are some of the issues that I dealing with.&lt;BR /&gt;
&lt;BR /&gt;
This is all based on the fact that this project is approaching 900mb as a teamwork file (this worries me).&lt;BR /&gt;
&lt;BR /&gt;
1st Method:  Extract the layout book into a separate team work file.&lt;BR /&gt;
&lt;BR /&gt;
issues:&lt;BR /&gt;
a)  The detail markers can't be set to the outside layout book file automatically.  If you could open a detail marker or any marker inside the model file and link it to a location on a sheet within Layout Book file.&lt;BR /&gt;
&lt;BR /&gt;
2nd Method:  Create PMK's&lt;BR /&gt;
&lt;BR /&gt;
issues:&lt;BR /&gt;
a) Can not do this quickly, or in a batch method through the drawing manager.   You must go through each drawing one by one and link it to the PMK that you want.  The only options are to link to a solo project or teamwork project.  We could probably create a file with PMK's that are connected to that some how?  Though that sounds a little complicated to manage.&lt;BR /&gt;
b) Does produce a noticeable smaller PDF file and the files are so much more light weight, and agile.&lt;BR /&gt;
&lt;BR /&gt;
What am I missing?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 May 2023 14:37:17 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Breaking-up-a-Large-Project/m-p/218165#M58534</guid>
      <dc:creator>ares997</dc:creator>
      <dc:date>2023-05-26T14:37:17Z</dc:date>
    </item>
    <item>
      <title>Re: Breaking up a Large Project</title>
      <link>https://community.graphisoft.com/t5/Documentation/Breaking-up-a-Large-Project/m-p/218166#M58535</link>
      <description>Are you having problems on the project that you feel are due to its size?&lt;BR /&gt;
&lt;BR /&gt;
Breaking it up does have its problems as you have noted and it will be a considerable amount of work to change over. There is nothing inherently bad about large file sizes. They can cause problems but the proper fix depends on their nature and severity.</description>
      <pubDate>Sat, 26 Jan 2013 05:42:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Breaking-up-a-Large-Project/m-p/218166#M58535</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-01-26T05:42:20Z</dc:date>
    </item>
  </channel>
</rss>

