Mystery library folder embedding in teamwork projects

[Anonymous]

I have a library folder called "from 201101 library". I know this is a project number and is included in the 201101 teamwork project (in the embedded library).
The problem I am facing is that this folder also "appears" in most other projects embedded libraries and pollutes the attributes when it does so. My thought is this folder may have been included in a container or .lfc for one of the BIM server libraries, but I don't think that would cause it to appear in the embedded library.
When I delete the folder from the embedded library and clean up the attributes all is well for a time, then out of nowhere the folder reappears and destroys the attributes again.
I have tracked down several (duplicate & identical) folders within the network with this exact name and have renamed them in the hopes of identifying and ultimately deleting the culprit; but I need to keep this sort of glitch from happening with other folders as well.
I would like anyones opinions or ideas on what could be causing this folder to, seemingly by way of nefarious magic, appear in the embedded libraries of our teamwork projects. I have spoken with some GS techs about this, but it seems to stump everyone I am able to talk to about it.

thanks,
Patrick

[Anonymous]

Hi Patrick,
the first thing that comes in mind is that someone is using the option to embed objects from that library folder in the local library manager.

[Laszlo Nagy]

Maybe you have Hotlinked Modules that have this library in the embedded library and when it is updated the library again appears in the Embedded Library?

[Anonymous]

Ilder,
This folder(s) is only available on one users work station, that I can find. I don't know how anyone could access it, except through the original 201101 project, maybe via a copy and paste. I did talk with one of the model managers and he did say he copied some linework for a detail from that project. I just don't know how that would bring in an entire folder to the embedded library.
Laszlo,
the projects that seem to have the most problems are the source files for modules; to place multiple buildings into a site. These buildings files do not have any modules placed into them.

It is kind of odd, that since I renamed these folders they have not re-embedded themselves.

[Anonymous]

typed that last response too soon. The folder HAS found its way into the embedded library, and not with one of the new folder names.

[Anonymous]

Hy Patrick,
linework wont cause such thing, but if a 2d/3d object was included in the selection of the "copy and paste" then the problem will show up.

Another thing: what do you mean by "pollutes the attributes" ?

One more: a screenshot of the "from 201101 library" content in the library manager will help.

[Anonymous]

Ilder,
I will send a screen shot of the embedded library and 201101 folder next time it shows up.
It adds about 250 new surfaces to the attributes whenever this folder is embedded.
Could this be a local data issue? if this folder is part of a container in the local data could it somehow find its way into the project?

[Anonymous]

250 surfaces?
it could be a library with a different localization or perhaps objects with missing surface parameters as default.
I will look at the screenshot.