How to get linked and actual folder information

rohit.khattar
rohit.khattar Member
edited July 14, 2009 in Documentum #1

Is there any way to find ,whehere a folder is linked to another folder or it is actually created inside a that folder.

For e.g.

Consider that a user creates a Folder A  and Folder B under a Cabinet X using Webtop

Then a user creates a folder A1 under folder A

User then links the folder A1 (created under folder A) to folder B

In webtop a link icon is shown for folder A1 under folder A and folder B

Now if any other user logs in , is there a way he can identify that the folder A1 was created under folder A but linked to folder B ?

Need to know this differentiation of events and whether documentum maintains actual and linked folder information.

Thanks.

Comments

  • Francois Dauberlieu
    edited July 14, 2009 #2

    Basically, the 1st entry in the folder path attributes is, in most of the cases, the location where the object was initially created.

    However, this is not always true, for example, if you remove the link from folder A after linking the object to folder B.

    Now, the question would be more, should it really matter ? I'd say it could, if the object you create is suppose t inherit attribute values from the parent folder or parent cabinet because in this case, the parent folder wouls still be A1 but the parent cabinet could indeed be another cabinet all together

  • rohit.khattar
    rohit.khattar Member
    edited July 14, 2009 #3

    So Francois,

    Does it means that documentum webtop doesn't differentiate between linked and actual folder information ?

    Thanks.

  • DCTM_Guru
    DCTM_Guru Member
    edited July 14, 2009 #4

    There is a minuscule difference between the 1st primary folder and everything else.  If you have the Inherit Permissions From Folder (from server config), then the acl from the primary folder is what gets copied to the newly created/imported object.

  • rohit.khattar
    rohit.khattar Member
    edited July 14, 2009 #5

    Johnny,

    I got your point but i fear that I could not find any solution (OOTB) for this .

    One solution we have planned to use is to have a custom attribute that stores the parent folder path of the original parent , this attribute value gets populated for import,create , move and copy operations.

    Now ,I am just thinking of the impact of this new attribute in case of migration.

    The reason why I need to get this information is because we are inheriting values from parent folders only for import,create , move and copy operations. In that case we need to differentiate between linked and actual folder information.

    Any suggestions .....

    Thanks.

  • DCTM_Guru
    DCTM_Guru Member
    edited July 14, 2009 #6

    Your approach seems reasonable.  What is your concern about migration?