Attributes getting changed of the documents

Hello Experts,

We are undergoing an migration from Documentum to Sharepoint.

The team is using Tsunami tool.The team exported the documents from the cabinet.We created user 'abc' and that user was added to 'dm_read_all' group so that the user can have read only access to all the cabinets.While exporting the documents they use the user 'abc' to connect to the documentum.

But now we have found that the few documents's attributes like owner name, creator name, r_modifier is getting updated.

Can anyone help be to understand why this is happening?

Find more posts tagged with

Comments

DCTM_Guru

Are these getting updated in Documentum or Sharepoint? It makes sense if the values are getting updated in Sharepoint b/c abc user is the "creator/owner" of the objects in Sharepoint. The r_modifier date always gets updated in Documentum when you update the object (including create). Not sure if this is the same for Sharepoint.

AnupritaSapate

Thanks Johnny,

No, but here the case is the attributes in the Documentum are getting modified.

DCTM_Guru

It shouldnt - I would look at your migration code for anywhere it tries to perform save().

AnupritaSapate

Yes,its the Migration SharePoint team who is doing the migration.We have raised a concern with them stating that the the attributes are getting modified.

DCTM_Guru

You can also configured Documentum to be in read-only state, which should prevent them from updating attribute values if they dont want to modify their code.

AnupritaSapate

Can you please guide of how to configure Documentum to be in read only state?But the user the Shareoint team is using is having read only access to the Documentum site.The user is added to 'dm_read_all'.So i think the attributes should not get modified.

DCTM_Guru

Verify that the user does not belong to other groups that have WRITE permissions (including dm_world). You will need to look in the server admin guide for the parameter setting to change the docbase to read-only state.

AnupritaSapate

I had added user to group 'dm_read_all' which is the read only group.

Regarding the dm_read_all group.

Without a special mechanism, such a requirement would lead to some group being added to all the ACLs used by documents. Documentum 6.5 SP2 introduced a built-in group dm_read_all, which has READ access to any sysobject in the repository regardless of the ACL assigned to the object.