Hello,
I found this comment in Documentum connector
/** Let the crawler know the completeness of the information we are giving it.
*/
@Override
public int getConnectorModel()
{
// For documentum, originally we thought it would return the deleted
objects when we
// reseeded. Later research has shown that documentum simply
deletes the whole thing now
// and doesn't leave a gravemarker around at all. So we have no
choice but to treat this
// like other stupid repositories and check for deletes by scanning!
UGH. It also does
// not accurately provide changes, because the ACL changes are not
caught by the query.
return MODEL_ADD;
}
When you were discovering possibilities how to fetch updated and
deleted documents - had you tried to make use of Documentum table
dm_audittrail?
It looks that by querying it user is able to find ids of documents
which were modified or deleted. For example: select * from
dm_audittrail where event_name='dm_destroy' and
object_type='dm_document'
If yes - what was the reason this did not work?
Thank you very much
Roman
