Solved

Document Content Seach Domain - Possible to limit Doc Classes?

  • 13 January 2023
  • 6 replies
  • 82 views
N
Rank
Userlevel 2
Badge +7

Hi

We are looking into enabling text search on documents, and have looked at the document content search domain which would allow this. But enabling this search domain, gets it to start synchronizing all documents, of which we have millions. 

Is it possible to limit this to specific document classes? We are only interested in doing this for certain document classes. Doing it for all our documents at once also seems unfeasible, at the rate of syncronizing we see.

Is this possible, or is it necessary to create a new search domain?

We use IFS APP10 UPD8

Best Regards

icon

Best answer by Jonas Feigl 13 January 2023, 13:57

View original

6 replies

Amila Samarasinghe
Rank
Userlevel 6
Badge +14

As far as I know there is no way to filter this functionality by Document class. But having said that, document content search domain will only works for documents that are saved in the database. So perhaps you can try to move other document classes which you do not need the search domain enabled to some other repository type such as FTP or shared folder.

 

Thanks.

Amila S. - https://www.linkedin.com/in/amila-samarasinghe-b3285974/
Jonas Feigl
Rank
Userlevel 5
Badge +17

@NicklasMadsen Unfortunately this is not possible via configuration. With a modification you could change the existing search domain model (DocumentContent.searchdomain in component DOCMAN) and add a condition to it:

 

You mentioned that it would take too long to synchonise all your documents due to the rate of synchronisation. How long do you think this will take? You can limit the number of records that get synchronised each time the sync job runs via the “Search Domain” page in Solution Manager. Once you have a rough idea how many records get processed per hour you could set a limit and schedule the sync job to start outside of working hours etc. and over time all documents should get synchronised without noticable impact to the users.

Mathias Dahl
Rank
Userlevel 7
Badge +30

I just want to add a heads up to the above. If you plan to upgrade to IFS Cloud anytime soon, you should know that the document content search feature is not there yet, for reasons I'm not going to repeat here (all search domains and the whole search domain concept is removed). We want to add it back in some form or another, for Docman, but it's not done yet, not even in IFS Cloud 23R1, soon to be released.

/Mathias
N
Rank
Userlevel 2
Badge +7

@Jonas Feigl 
The current rate is just under 4000 documents pr hour, which at 2,4 million documents takes the better part of a month, and thats if its run 24 hours a day. 

We might investigate the possibility of modification

Jonas Feigl
Rank
Userlevel 5
Badge +17

@Jonas Feigl 
The current rate is just under 4000 documents pr hour, which at 2,4 million documents takes the better part of a month, and thats if its run 24 hours a day. 

We might investigate the possibility of modification

It’s obviously not ideal that it takes that long but as long as your database has some headroom to have one additional process running 24/7 (which most installations do) would this not still be an option?

N
Rank
Userlevel 2
Badge +7

@Jonas Feigl 
It is definitely a possibility we are considering, but we unfortunately do sometimes max out on sessions. 

Nevertheless. Thank you for the responses

Reply


Terms & ConditionsCookie settings