<?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 Re: Schedules, door ID and repetitive modules in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58236#M5502</link>
    <description>NCS 12 seems to give the zone for the tag itself --you need to drag the tag to the side you want the door to belong to. &lt;BR /&gt;
&lt;BR /&gt;
[It's been ages and 3 ArchiCAD versions since I last used the NCS tag, and I can't remember if the last time I did this I was using some other tag, standard or most probably customized , but I would swear that I was using some other hotspot (a base hotspot for an invisible tag extension line) to read the zone.]&lt;BR /&gt;&lt;IMG src="https://community.graphisoft.com/t5/image/serverpage/image-id/6640iC77628CFBC5A236E/image-size/large?v=v2&amp;amp;px=999" border="0" alt="Picture 2.png" title="Picture 2.png" /&gt;</description>
    <pubDate>Fri, 10 Jul 2009 18:59:33 GMT</pubDate>
    <dc:creator>Ignacio Azpiazu</dc:creator>
    <dc:date>2009-07-10T18:59:33Z</dc:date>
    <item>
      <title>Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58214#M5480</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;How are people handling door IDs in projects with non-residential repetitive modules (labs, hotels, hospitals, office buildings, schools)? &lt;BR /&gt;
1) My usual way of doing that was to use hotlinked modules for the repetitive stuff and get the door tag to identify the door type, which works OK. But I am now discovering that &lt;BR /&gt;
2) many US practices use the tag to identify the door *unit*, so that each individual door in the building gets a unique ID, which I think there is no way of doing with repetitive hotlinked modules. &lt;BR /&gt;
Given the choice of modeling everything 20 or 200 times each time a change is made to the repetitive design or putting the door tag ID manually at the end of the process I guess I would go for the manually tacked-on door tag object --but that will not show in the door schedule. I am trying to understand the reason for the unique ID for each door, and I am thinking that maybe it is a practice coming from residential and that should be done away with in this type of buildings (where each door is less unique anyway), but since this is the first time I come across this method I am not sure if there is any hidden logic to it that I am not seeing. &lt;BR /&gt;
3) Another option would be to break the hotlinks at the end of the process and manually give an ID to each door object, which would then show in the schedule. But since nobody can ever be right about when 'the end of the process' is, in practical terms this would end up working exactly the same as '2)'. &lt;BR /&gt;
So what is everybody doing?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 04 Oct 2005 15:26:59 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58214#M5480</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2005-10-04T15:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58215#M5481</link>
      <description>Ignacio -&lt;BR /&gt;
&lt;BR /&gt;
Interesting question.  I tend to favour the 'unique number' for every door (and window, for that matter) for 3 reasons: a) if you're using a scheduling method other than ACad's own, it allows a check that you've covered every door,  b) you can make modifications in the schedule without having to amend the drawing (e.g. Change 'Door No. GF10' to a 'Type 3'), and c) it simplifies referencing a particular door ('Make good damage to door no. GF10)&lt;BR /&gt;
&lt;BR /&gt;
If I were using modules, I would use text to label the doors (and yearn for an incremental numbering tool for that purpose).&lt;BR /&gt;
&lt;BR /&gt;
However, I assume this would preclude you from using Acad's door scheduling tool - don't know the answer to that one.</description>
      <pubDate>Thu, 06 Oct 2005 13:07:23 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58215#M5481</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-10-06T13:07:23Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58216#M5482</link>
      <description>Ignacio -  &lt;BR /&gt;
 &lt;BR /&gt;
The first thing that came to mind when I read your situation was, why do your door tags have to be connected to your doors? When using modules I would still use zone stamps, and you can utilize custom parameters within zone stamps to represent your doors, which would solve scheduling problem. But you would have to modify a leader GDL to be able to pull the correct parameter out of your zone stamp. I haven't tried this but I'm sure with a little experimentation it could be pulled off. Let me know if this works.</description>
      <pubDate>Thu, 06 Oct 2005 14:43:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58216#M5482</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-10-06T14:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58217#M5483</link>
      <description>I found the solution, way simpler and more obvious than I ever imagined (I was positively sure that this one wouldn't work, but fortunately I didn't trust myself, tried it and it does work): &lt;BR /&gt;
- make modules with all the walls etc. and assign each door a User ID in the module (like 1, 2, 3, for the first, second, third door in a room); &lt;BR /&gt;
- get the door tag to show 'Room and Door ID' (this is an option in the new Special Edition US Library, as is, without any scripting); &lt;BR /&gt;
- bring in the modules and multiply etc. the modules in the building file, and then create the zones in the building file (this was always a given, in order to get unique room names and numbers using the Zone Name and Zone No.).&lt;BR /&gt;
&lt;BR /&gt;
The doors will then get their unique door tag showing the Room Number (Zone No.) followed by the Door ID --such as 101 1 (Room No and Door ID show in different lines in the 'Door Marker_NCS SE 9', which is not too bad, but with a bit of scripting could show in a single line, even a single string without spaces). &lt;BR /&gt;
&lt;BR /&gt;
I  had thought the doors built into the module would not read the zones in the building files, but they do. Which is actually the only sensible behavior and the Graphisoft guys obviously figured that one out 20 years ago, but I only realised today. It works beautifully, and I am feeling like kissing these Hungarians. Ahhhh, so much less work, so many less coordination headaches.</description>
      <pubDate>Tue, 11 Oct 2005 08:08:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58217#M5483</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2005-10-11T08:08:29Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58218#M5484</link>
      <description>&lt;BLOCKQUOTE&gt;Ignacio wrote:&lt;BR /&gt;get the door tag to show 'Room and Door ID' (this is an option in the new Special Edition US Library, as is, without any scripting)&lt;/BLOCKQUOTE&gt;

Excellent topic, thanks for the discussion and for sharing your solution.&lt;BR /&gt;
&lt;BR /&gt;
One question though. The option in the new Special Edition US Library that you write of is the label, not the door itself, right?  Presumably this label could be used with other doors (I use DoorBuilder).  Is this your situation too? any info appreciated.</description>
      <pubDate>Tue, 11 Oct 2005 12:47:22 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58218#M5484</guid>
      <dc:creator>Chazz</dc:creator>
      <dc:date>2005-10-11T12:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58219#M5485</link>
      <description>&lt;BLOCKQUOTE&gt;Chazz wrote:&lt;BR /&gt;The option in the new Special Edition US Library that you write of is the label, not the door itself, right?  Presumably this label could be used with other doors (I use DoorBuilder).  Is this your situation too? any info appreciated.&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
I am not familiar with Door Builder (not even sure if it is an object or an API). I am not sure about how loading the NCS SE 9 label from Door Builder would work in terms of getting the pop-up parameter for 'Room and Door ID' to display in the label, etc. &lt;BR /&gt;
&lt;BR /&gt;
If the NCS SE 9 label can do it I would think the potential is there for every door in any library, with the NCS SE 9 if it works and with some custom scripting if it doesn't.&lt;BR /&gt;
&lt;BR /&gt;
Graphisoft warns severely and repeatedly against the potentially catastrophic consequences of loading the SE Library on a project using the non-SE Library --I would guess some parameters kept their name but changed details of how they work, some things look the same but have differing underlying parameters, etc. So if there is any problem with Door Builder and the new label it can also be related to that.</description>
      <pubDate>Tue, 11 Oct 2005 14:46:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58219#M5485</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2005-10-11T14:46:34Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58220#M5486</link>
      <description>&lt;BLOCKQUOTE&gt;Ignacio wrote:&lt;BR /&gt;Graphisoft warns severely and repeatedly against the potentially catastrophic consequences of loading the SE Library on a project using the non-SE Library&lt;/BLOCKQUOTE&gt;

My thought was to unpack the SE Library PLA and just harvest out the label ID tag.  Then rename it and use it within my existing library structure.  Seems that ought to work.  I will adopt the SE Lib in time but can't swallow the whole thing now.  Thanks again for your help here.</description>
      <pubDate>Tue, 11 Oct 2005 14:55:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58220#M5486</guid>
      <dc:creator>Chazz</dc:creator>
      <dc:date>2005-10-11T14:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58221#M5487</link>
      <description>&lt;BLOCKQUOTE&gt;Chazz wrote:&lt;BR /&gt;[My thought was to unpack the SE Library PLA and just harvest out the label ID tag.  Then rename it and use it within my existing library structure.  Seems that ought to work.  I will adopt the SE Lib in time but can't swallow the whole thing now.  Thanks again for your help here.&lt;/BLOCKQUOTE&gt;

The revised SE9 library posted today can be loaded alongside other libraries.  So, the dire warning associated with the prior release do not apply.&lt;BR /&gt;
&lt;BR /&gt;
Karl</description>
      <pubDate>Wed, 12 Oct 2005 04:55:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58221#M5487</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2005-10-12T04:55:14Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58222#M5488</link>
      <description>&lt;BLOCKQUOTE&gt;Karl wrote:&lt;BR /&gt;The revised SE9 library posted today can be loaded alongside other libraries.  So, the dire warning associated with the prior release do not apply&lt;/BLOCKQUOTE&gt;

&lt;BLOCKQUOTE&gt;GS wrote:&lt;BR /&gt;We have significantly changed the parameters and the user interface of many objects (e.g. doors and windows). Therefore, this library can not be used together with the AC 9 US library on the same project. In order to avoid any conflicts between new and old objects, please don't load this library into an existing project and do not load the two libraries together! Please also read the detailed AC 9 Special Edition Library Manual before starting to use it.&lt;/BLOCKQUOTE&gt;

Thanks for the heads up on the new version of the SE library.  However, it appears to still not play well with the standard AC 9.0 Lib according to the website. I think what they mean is that you can use the revised SE library in conjunction with the old SE library. Or do you have a different read on it?  For everyone else, the download can be found &lt;A href="http://tr.graphisoftus.com/" target="_blank"&gt;here&lt;/A&gt;</description>
      <pubDate>Wed, 12 Oct 2005 12:11:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58222#M5488</guid>
      <dc:creator>Chazz</dc:creator>
      <dc:date>2005-10-12T12:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58223#M5489</link>
      <description>Chazz,&lt;BR /&gt;
&lt;BR /&gt;
Sigh.  Whoever created that web page on the tr.graphisoftus web site did not update it for the new release.  I'm writing the powers that be to let them know of this oversight.  The 'test' page (which is gone now) contained the appropriate content - which is that this new SE9 library (posted this week) can be loaded alongside any other library EXCEPT the prior release of SE 9.  For people who started using the first release of SE9, you should just remove that library from your project and reference this one instead.  Even though the names of the parts have changed, the references will be correct because of matching internal GUID.&lt;BR /&gt;
&lt;BR /&gt;
The correct announcement text is here:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=46767#46767" target="_blank"&gt;&lt;LINK_TEXT text="http://archicad-talk.graphisoft.com/vie ... 6767#46767"&gt;http://archicad-talk.graphisoft.com/viewtopic.php?p=46767#46767&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Tibor wrote:&lt;BR /&gt;&lt;B&gt;Special Edition Library Update is Available&lt;/B&gt;&lt;BR /&gt;
&lt;BR /&gt;
 &lt;BR /&gt;
The updated version includes the correction of inconsistencies found in the first release and it's fully compatible with the original SE library. The most important changes are the following:&lt;BR /&gt;
&lt;BR /&gt;
·         SE9 version suffix added to each object's name so that it can be loaded together with the ArchiCAD 9 library &lt;BR /&gt;
·         Textures , background pictures and list templates have been removed from the library archive (pla) and moved to separate folders so that you can freely unload or modify them &lt;BR /&gt;
·         Parameter transfer between different types of doors and windows fixed &lt;BR /&gt;
·         Different materials can be assigned to the inside and outside of the doors and windows &lt;BR /&gt;
·         Window size can be entered correctly in the editable hotspot's pet palette &lt;BR /&gt;
·         Sash setback parameter added to windows &lt;BR /&gt;
·         Brick arch and sill functions corrected in case of ganged windows and doors &lt;BR /&gt;
·         No hotspot editing of window size allowed in case of typical sizes &lt;BR /&gt;
·         Correct 2D and 3D if the brick sill is turned off for metal windows &lt;BR /&gt;
·         Simple brick sill position fixed &lt;BR /&gt;
&lt;BR /&gt;
Please visit the following website for downloading:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://www.graphisoft.com/support/archicad/downloads/library_updates/usa.html" target="_blank"&gt;&lt;/A&gt;&lt;S&gt;&lt;A href="http://www.graphisoft.com/support/archicad/downloads/library_updates/usa.html" target="_blank"&gt;&lt;/A&gt;&lt;A href="&amp;lt;/s&amp;gt;&amp;lt;LINK_TEXT text=&amp;quot;http://www.graphisoft.com/support/archi ... s/usa.html&amp;quot;&amp;gt;http://www.graphisoft.com/support/archicad/downloads/library_updates/usa.html&amp;lt;/LINK_TEXT&amp;gt;&amp;lt;e&amp;gt;"&gt;&lt;/A&gt;&lt;/S&gt;&lt;LINK_TEXT text="http://www.graphisoft.com/support/archi ... s/usa.html"&gt;http://www.graphisoft.com/support/archicad/downloads/library_updates/usa.html&lt;/LINK_TEXT&gt;&lt;E&gt;&lt;/E&gt;&lt;/BLOCKQUOTE&gt;

&lt;BR /&gt;
Regards,&lt;BR /&gt;
Karl</description>
      <pubDate>Thu, 13 Oct 2005 17:40:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58223#M5489</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2005-10-13T17:40:02Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58224#M5490</link>
      <description>Karl,&lt;BR /&gt;
&lt;BR /&gt;
A confusing situation, yes.  In fact, it would appear that I have fanned the flames of that confusion (does confusion have flames and if so could you really fan them?).  I had not seen the other page until 10 min after I posted.  I always rely on the graphisoftus site for new stuff.  Deep sigh...&lt;BR /&gt;
&lt;BR /&gt;
You might think a company that makes a tool that's supposed to help us convey our ideas with crystal (even legally binding) clarity might consider these things before posting such a flummoxing set of contradictions.  Ugh....&lt;BR /&gt;
&lt;BR /&gt;
Thanks as always for your vigilance and hard work.</description>
      <pubDate>Thu, 13 Oct 2005 18:05:50 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58224#M5490</guid>
      <dc:creator>Chazz</dc:creator>
      <dc:date>2005-10-13T18:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58225#M5491</link>
      <description>Err I was glad that the Zone Number detection from within the door in the module provided a way of giving unique tags to each door in repeated modules without having to break the links, but it still doesn't solve a fairly typical situation which is a facade section that repeats independently of the room layout, so that a given room may have more than one of the same panels. &lt;BR /&gt;
&lt;BR /&gt;
I don't think there is a workaround to this without an API, since modules don't have any sort of 'ID' that can be detected by the door, and since doors don't have a way of telling if they are the first second or third instance in a zone. &lt;BR /&gt;
&lt;BR /&gt;
This is a bit depressing because at the critical more labor-intensive and potentially more labor saving point in the process (door naming, scheduling, and last minute changes) repeated instances of a hotlinked module just will not work unless I find a way of persuading the world around me that they don't really need unique IDs for each door, which is what they happen to have been doing since times immemorial.</description>
      <pubDate>Wed, 02 Nov 2005 19:14:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58225#M5491</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2005-11-02T19:14:54Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58226#M5492</link>
      <description>Ignacio,&lt;BR /&gt;
&lt;BR /&gt;
Forgive me for forgetting... but have you made a wish for this functionality yet?  If so, could you post the link here?&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Karl</description>
      <pubDate>Wed, 02 Nov 2005 20:06:15 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58226#M5492</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2005-11-02T20:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58227#M5493</link>
      <description>&lt;BLOCKQUOTE&gt;Karl wrote:&lt;BR /&gt; but have you made a wish for this functionality yet?&lt;/BLOCKQUOTE&gt; &lt;BR /&gt;
&lt;BR /&gt;
I haven't yet because 1) I was not yet positive that the functionality was not available somehow, and 2) I am still not sure what I should be asking for.  &lt;BR /&gt;
&lt;BR /&gt;
At this point I think it would be some sort of Module Instance ID, readable in Hotlink Manager, usable in Find&amp;amp;Select, and readable by objects just as they can read the Zone they are in. So that one could come up with the specific object instance ID by doing Zone Number + Module Instance + Object User ID. &lt;BR /&gt;
&lt;BR /&gt;
There have been wishes in this sense in the past, I am not sure if they went into that much detail in terms of its absolute need for basic usability of basic tools (modules, scheduling) in typical projects. I'll check out and add to the thread or create a new one.</description>
      <pubDate>Wed, 02 Nov 2005 22:14:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58227#M5493</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2005-11-02T22:14:28Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58228#M5494</link>
      <description>There goes the wish. Please vote. Favorably. &lt;BR /&gt;
&lt;A href="http://archicad-talk.graphisoft.com/viewtopic.php?t=8554" target="_blank"&gt;&lt;LINK_TEXT text="http://archicad-talk.graphisoft.com/vie ... php?t=8554"&gt;http://archicad-talk.graphisoft.com/viewtopic.php?t=8554&lt;/LINK_TEXT&gt;&lt;/A&gt;</description>
      <pubDate>Thu, 03 Nov 2005 02:33:27 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58228#M5494</guid>
      <dc:creator>Ignacio Azpiazu</dc:creator>
      <dc:date>2005-11-03T02:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58229#M5495</link>
      <description>I have just run into this issue since this is our first time using hotlinks in an ArchiCAD project (college housing with multiple units).  Our firm heavily relies on door and window schedules and it's essential for us to have unique door IDs for each one despite the repetition.  Seeing that this issue has been approached 3-4 years ago, I was wondering if it has been resolved?  Using AC12 here and would rather &lt;B&gt;not&lt;/B&gt; add another library such as Door Builder.  Thanks!</description>
      <pubDate>Mon, 06 Jul 2009 15:06:26 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58229#M5495</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-07-06T15:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58230#M5496</link>
      <description>I do not think any progress has been made on this issue.&lt;BR /&gt;
&lt;BR /&gt;
Can you tell a bit more about the purpose of each instance of a Door/Window having a unique ID?</description>
      <pubDate>Tue, 07 Jul 2009 10:42:18 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58230#M5496</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2009-07-07T10:42:18Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58231#M5497</link>
      <description>I believe that by having a door/window schedule tagging each door/window individually, an architecture firm would have very clear indication and communication with the contractor/builder displaying all the correct properties of each door/window on the construction drawings.  The contractor would also appreciate knowing which door and its location will have this assigned hardware, finish, etc.&lt;BR /&gt;
&lt;BR /&gt;
If I followed the method ArchiCAD is currently giving us, we will have approx. 50-75 doors sharing the same ID.  I highly doubt all 50 doors will have the same hardware or finish.  Using a door schedule with unique IDs, while it may seem very repetitive, at least we will have control of properly indicating which door will have this hardware or this finish.  It also would not make sense for me to create a new module of the exact same layout just so I can separate them by door hardware or finish.&lt;BR /&gt;
&lt;BR /&gt;
Other firms may have other reasons for creating unique door/window IDs for scheduling, but this is our most pressing reason - being able to control the hardware and finishes of each door/window using the schedule sorted by unique ID.</description>
      <pubDate>Tue, 07 Jul 2009 13:36:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58231#M5497</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-07-07T13:36:32Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58232#M5498</link>
      <description>OK, I get what you mean.&lt;BR /&gt;
It is not possible at the moment.&lt;BR /&gt;
All you can do is break the hotlink in those instances so you can change the IDs.</description>
      <pubDate>Tue, 07 Jul 2009 14:02:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58232#M5498</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2009-07-07T14:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: Schedules, door ID and repetitive modules</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58233#M5499</link>
      <description>Thanks Laszlo (as I believe that's what most users call you here) for confirming that.  Us ArchiCAD users will have to put our heads together and figure a solution for this.  Probably deciding whether to compile door IDs and list quantity or breaking hotlinks.&lt;BR /&gt;
&lt;BR /&gt;
Hopefully this "issue" can be something for Graphisoft to consider in future releases.</description>
      <pubDate>Tue, 07 Jul 2009 14:15:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Schedules-door-ID-and-repetitive-modules/m-p/58233#M5499</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2009-07-07T14:15:13Z</dc:date>
    </item>
  </channel>
</rss>

