nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TeamSite Search - how to exclude all files except DCRs

System

I want to only index DCRs. My DCRs do not have file extensions. From what I can tell, I would have to add all the possible file extensions that my users import (100 to 120 extensions) to the iw.index.binaryextensions entry in the search.properties file in order to exclude them. The problem with that, is that a user can import a file with an extension that isn't in the list and then, voila, it's indexed. Also, if they create a file without an extension, which is possible, then this also would get past.

Is there a better way to do this than by adding this large list and routinely checking the list file extensions on a periodic basis?

Find more posts tagged with

Comments

Migrateduser

No way currently to do that from TS search. You can try looking at CSSDK for your specialized search needs.

aviz_de_expeditie2.rptdesign

Adam Stoller

I want to only index DCRs. My DCRs do not have file extensions. From what I can tell, I would have to add all the possible file extensions that my users import (100 to 120 extensions) to the iw.index.binaryextensions entry in the search.properties file in order to exclude them. The problem with that, is that a user can import a file with an extension that isn't in the list and then, voila, it's indexed. Also, if they create a file without an extension, which is possible, then this also would get past.

Is there a better way to do this than by adding this large list and routinely checking the list file extensions on a periodic basis?

Perhaps you should enforce having an extension (e.g.: .dcr) on your DCRs and fix all existing ones to comply with that rule -- it's a bit of a pain in the short-term but would probably make life a lot easier in the long-term...

nipper

Perhaps you should enforce having an extension (e.g.: .dcr) on your DCRs and fix all existing ones to comply with that rule -- it's a bit of a pain in the short-term but would probably make life a lot easier in the long-term...

Hindsight is a beautiful thing. All my DCRs are .XML. I can certainly understand that changing this mid project could be rather difficult.

Migrateduser

We've been running without an extension since 2002. Changing the extension would result in all existing dcrs losing their revision history as a file rename causes a brand new file (I just tested this out). Not an option.

I eventually went with adding all the extensions to the config file. Our attachments are in different locations from the DCRs and as long as they are somewhere inside the templatedata folder they are fine, but this is only true for CCPro. CCStandard searches the whole thing, but I also changed the file size limit in the index from 20mb to 1mb and this helped weed out many files. The resultset coming back is acceptable, however, the ability to select indexing of only DCRs would be ideal. I suppose I should submit a FR for this.