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; } } }

Workarea Search not returning expected results

SethHickel

I have a continuing situation that I have posted about before without finding a solution.

My users want to be able to search for files in their workareas including files that may not have been submitted to TeamSite staging (0+ version files).

With my current settings I would have thought all would be well - but - it is not. As an example we enter as the file name myfile.html in the advanced search "Filename:" text box. This file is version 0+. The search does not return any results even though the file was created many days ago.

Question 1: Is it possible to index and search against "0+" versions in a workarea?

Question 2: Considering the portion of my search.properties file below are there additional configuration changes that I need to make?

Question 3: What constitutes a "modification" in a workarea that would trigger a re-indexing of the workarea?

Question 4: If indexing and searching on workareas is dependent upon a files submission to TeamSite staging can I assume that modifications in a workarea to a file that has previously been submitted to TeamSite staging will or will not trigger a re-index OR does the modification need to be submitted to TeamSite staging before the re-index is triggered.

The branch is listed in the results of the iwndxlistbr command.
The branch was last indexed today and the file we are searching for was created 4 days ago but has never been submitted to TeamSite staging.

Below is the applicable section of my search.properties file.

# Indexing workarea modifications
# Control whether indexing of and searching across modifications in workareas
# of indexed branches is turned on or not.
iw.index.wamodifications.enable=true
# Control whether indexing the modifications of ALL the workareas of a branch
# at the time the branch is first indexed should be turned on or off (permissible
# values are none and all).
iw.index.wamodifications.branchcreation.default=none
# Control how often (in minutes) an attempt is made to index the modified files in the
# relevant workareas of all the relevant indexed branches.
iw.index.wamodifications.frequency=2
# Control after how much time (in hours) the collections of workarea modifications for a
# branch are considered too old and hence deleted and then re-indexed. Checked during
# index server startup only.
iw.index.wamodifications.deleteindexes=72

Find more posts tagged with

Comments

SethHickel

Version: Interwoven TeamSite 6.7.1.0
Build Number: 60750

Interwoven TeamSite Search and Index 2.1.0.0.60744

nipper

If you submit the file and then change it, are the changes searchable ? It *may* be that index only hits changes to versioned files and not version 0+

You may have hit a product bug/doc bug

SethHickel

Thanks Nipper - that is a test that I am trying now. I will post the results.

I also opened a ticket with support to see if they have any suggestions.

After I run this test I plan on making a change to the value iw.index.wamodifications.branchcreation.default from "none" to "all " in my search.properties file. I will stop search and index, make the change, start index and search. I may delete the collection too.

SethHickel

Well - duh on my part - the following from the search results page when no results are found.

"Only submitted and approved content is indexed for search. New changes made in your modified content, since it was last submitted, is not used in the search match. Also, recently submitted and approved content may not be indexed immediately."

I created a new file but did not submit it to TeamSite staging (version 0+) I then waited for the engine to re-index and tried to search for the file. I did not get a return. I then submitted the file to TeamSite staging and waited for the engine to re-index and tried to search for the file again. This time the file was returned in the search.

I edited the file but did not submit the changes to TeamSite staging. I waited for re-index and then searched for my edited text: no results as expected.

I then submitted my edited file to TeamSite staging, waited on the re-index, searched for my edited text and got my file in the results.

So the question now would be - what does workarea modification indexing and search mean? Are we only searching in workareas for versioned files? And what is it using to index: it would appear the content in TeamSite staging.

Interesting.

Crsb

Version: Interwoven TeamSite 6.7.1.0
Build Number: 60750

Interwoven TeamSite Search and Index 2.1.0.0.60744

to confirm, you have just the base TS 671? no service pack?

if you had 671 SP1, you could upgrade to Search 3.1.1, it also indexes only submitted and approved content but it has significantly better, faster indexing and results than 2.x.

SethHickel

Thank you

From earlier in this thread:

Version: Interwoven TeamSite 6.7.1.0
Build Number: 60750

Interwoven TeamSite Search and Index 2.1.0.0.60744

nipper

When search was initially released in 6.5 it was only for submitted content. There was a feature request to index workarea modifications as well. I thought it was released already but I am not certain when.

SethHickel

Interesting - thank you - I will add this as a question to my support ticket and see if they know the specifics.

SethHickel

I got this to work with help from a support ticket.

Steps follow.

1. Change iw.index.wamodifications.branchcreation.default=none to iw.index.wamodifications.branchcreation.default=all in the "search.properties" file and submit the changes.

2. Delete collections

3. stop search,index

4. start index, search

5. run iwndxstatus -a to confirm that value is TRUE

After following these steps I added a new file to a workarea. I waited the length of time I have set in search.properties: iw.index.wamodifications.frequency=2

The file, which I have not submitted to TeamSite staging showed up in my search results when I searched for it by name. I also did a search for conentsin the file and got a hit too. I then edited the file and added more text. Waited the 2 minutes, searched for the new text and got a hit.

Hope this helps someone else too.