Specific requirements for indexing of individual object

Documentum 6.5 SP2

I have disabled indexing of dm_sysobject and all subtypes and specifically re-enabled certain custom object types. This means that dm_document will not be indexed which is intentional. However, a new customer will only be using dm_document for their content but would still like this content to be full text indexed. I do not want to index all dm_document objects so I was wondering what specifically is the bare minimum to get an object to index?

Questions:

1. Will an object index irrespective of its type registration status so long as a_full_text attribute is true?

2. If #1 is true, since I can't use a TBO on dm_document what other ways are there to set a_full_text to true based on object path? I'd prefer not to customize my WebTop interface but maybe presets could be used?

3. Can aspects be registered for indexing as if they were a type? If so, can a TBO be created on an aspect?

Any other suggestions or ideas are welcome.

Thanks,

Mark

Find more posts tagged with

Comments

lastnitescurry

for one I would say NO

Do not know if Aspects can be indexed, but I doubt it.

I am sure there are valid business arguments for a client using dm_document directly. Maybe there are no additional attributes. But a type also controls what business logic can be applied. And from past experience I would disagree strongly with the same type having different business logic in different repositories.

had to maintain a system where "General" document had different behaviour. Was a royal pain and it was an itch that would never go away!!!

DCTM_Guru

Have you tried manually "queueing" the document to Index Queue? If this works, then you should be able to employ this code logic using any custom attribute/flag in your TBO.

fainemr

I considered it and that is basically the gist of what I meant by question #1 above. I haven't tried it yet. I guess I could research it and give it a try. The way I understand it all that I'd need to do is override doSave and generate a dm_queue_item to dm_fulltext_user upon save?

*Actually, it just occured to me that a TBO is out since we are dealing with dm_document objects.*

Thanks,

-Mark

Message was edited by: fainemr - after pondering for a while...

DCTM_Guru

"...*Actually, it just occured to me that a TBO is out since we are dealing with dm_document objects.*"

- Why is it out? Your TBO should be against your custom object type. If you design your object model carefully, you should have only have a few "parent" custom types. In your code, you can also check the object type is what you want before queueing it.