Hi, I am trying to get a better understanding of Dr. Dieter Maurer's MFolder product and was wondering if anyone could comment on this inquiry? In the python script it states "Mirrowing folder allows to mirror one subfolder *M* to be seen (through acquisition) in the other subfolders" and my question is: Is the requested traversal of the mirrowing folder that leads to object *oa* whereby object *om* is obtained by traversing along the maximal prefix of *P*, where the term maximal means the element we are looking for is followed by no other. So for example, as long as my folder structure looks as follows from the root: M/registration <--- where there resides *oa* or MirrowId__showme and M/registration/en/registration <-- is where I expect *om* url /M/registration/en/registration/showme this seems to work fine. However, given the next case where I add M/crossover the traversal where I would expect to see the *om* of *oa* in M/crossover does not seem to work. My thinking was that acquisition is suppose to work on the entire object hierarchy. I am trying to learn if I need to write some logic at this point or reorganize my folder structure. In my real ZMI I have the following: root SD_Library/PublicationFolder/Intro where Intro contains DTML Doc /ACS/ contains Best Practice doc /AIRI/ contains another Best Practice doc CustomerA/PubFolder/ACS whereby I want to mirror the Best Practice docs only, even though the ../PublicationFolder/ACS folder contains several other documents. So acquisition traverses up to the root. Is there no way to have it search down the SD_Library path? If there is a way I would like hearing suggestions such as possibly configuring a DTML Method to contextually mirror the document. The /ACS/Best Practices document is going to be reviewed and updated every 6 months and should reside in the digital library area so whenever Customer A, B, or C logs on they should see the current BP docs. A copy should not be kept in the CustomerX/PubFolder/ACS container. TIA for the help. John Wubbel