Storing .pln files inside of active library

[Anonymous]

Hello all,
I have been wondering about loading pln's inside of active company libraries. I have seen a couple companies keep a master pln for a specific set of details loaded inside their loaded library. For example:

Libraries loaded:
ArchiCAD 10-
Company Lib-
Project Lib-

included in the company library is a set of details on foundation attachment to log beams. In that folder is a set of 12 details on the foundation, and along with that is the pln file that was used to create these details. This makes for faster browsing to find the original file to make changes to the details, but does this cause any issues with the loading of the library other than making the file size larger?

In short, is this a good practice? It seems a little odd to me, so I would like to get more opinions on pros and cons of this practice.
Thanks in advance,
Chris

[Link]

I think you are referring to an ArchiCAD Project Archive or PLA. Not PLN.

Loading a PLA as a library is one way to load library parts into a project. It's the parts loaded into that PLA that are used when that PLA is loaded, not the actual modeled elements that are contained in it. Because all the parts are loaded into the PLA, you are able to open it and edit easily enough, but it can be a bit of a nuisance resaving it. If you read the elements directly from the archive, you are effectively loading the PLA as the library, so when you then go to save it, ArchiCAD says that the file is already in use, which means you have to save it as a different file.

Alternatively, when you open the PLA to edit it, you can extract the parts to a folder and resave the PLA. Once it is saved, you can delete the folder containing the parts, and simply load the PLA as a library again.

Consider using a Library Container File (LCF) instead of saving and loading PLAs. Not only are LCF's much smaller (if you choose to compress them), but they are also easier to create and manage. You don't even really need a working file (like the PLA), as you can create an LCF from any file.

So, in summary, starting out on this adventure, you may find it easier to use LCF, and they'll be quicker to load, especially over a network. But having said all that, if it's only a couple of objects you're using in a Project Specific Library or even an Office Library, you could probably save the parts into a folder and load the whole folder. As it develops and grows in size, you could start saving it as an LCF to speed load times.

Just my 2 cents...

Cheers,
Link.

[Anonymous]

Hey Link,
I have a pretty good understanding of the archive and LCF process, but I was a little confused as to what all should be in the containers. The type of library management that I have seen would include actual pln files inside of the library container file. Say for example they had made a new detail on a home and they wanted to add that to their LCF. They would extract the container, add in the new detail as a .gsm, also add the other pln that was used to create the detail, and then package it all again in a new LCF. So my question is more related to the pln file being inside of the library. Does this cause any issues? Seems to me that it would just make the loading slower, but if this doesn't cause any issues I probably do not need to bring it up as a problem they need to fix.

Many more issues with the management processes, but I am choosing to take it one battle at a time.
Thanks for you time,
Chris

[Link]

Hmmmm - well maybe you have a much better understanding than I do.

A PLA can certainly be added into an LCF, but not PLNs. And I haven't tested it, but I don't know what the advantage of loading a PLA would be. Maybe it is smaller?:?

When they extract the Container, everything is extracted in it's original hierarchy, so whether it is a bunch of GSMs or a mixture of GSMs and a PLA, it shouldn't make much difference. I would have thought it would be easier to manage all GSMs myself.

In any case, I don't think it's a big deal and certainly not problematic. It just comes down to management preferences and maybe a very slight difference in loading times.

Cheers,
Link.

[Anonymous]

I tested this again to make sure I am not crazy. While you can't access the pln while it is in the LCF, you CAN zip one up in the LCF. This is the kind of trouble I have been running into. When you extract the LCF you can use the pln then, but what is the point if you have to extract every time you want to modify. Basically I have been looking for a reason to change their structure around and I agree with you about the management of the library. If you get several people with access to screw things up it doesn't take long to have a mess.

Thanks for the info Link. If this had just been a one time thing with one pln it would be fine, but they had over 20 pln's loading in the library. Not only that, but the library loading report had over 2, 500 errors. It has been a long road, but it is getting better....one battle at a time.

Thanks again,
Chris