Advanced Search Enhancement

I have a user requirement to enhance Advanced Search to allow for searching on additional metadata that would/could be either entered by the user or automatically by the tool.

Four questions/research paths:

1. Can advanced search be edited to search on additional metadata that is either entered by the user or automatically by the tool?
2. Can the tag interface be edited to collect additional metadata that advanced search would ultimately use?
3. Can the tool be used to add associated additional metadata with the generated file?
4. Can you point me to documentation that might help me fulfill this requirement?

Thank you.

Find more posts tagged with

Comments

Trey

Short answer is yes, yes and yes.

The interface is a little weak.

Read the search document on how to configure additional fields. The TeamSite admin guide has a whole chapter on configuring metadata capture.

Good luck,

ChartImage.PNG

SethHickel

I've been doing the reading. I think I understand the configuration of metadata capture and the files involved there.

I am still having a hard time (looking at chapter 7 - configuring interwoven search) finding a direct correlation between some file that is edited to cause selections to display for the user in the section of search in the attached jpg. And understanding if getting those drop-downs selections edited is what I need to do to get users to be able to search against the EA's that I allow them to apply to a file with the TAG GUI.

What file is it that controls what gets displayed for the advanced search and what file(s) do I need to affect to match up the EA's that I gather with the Advanced Search interface so that the users can construct a query that returns files with an EA of the value they provide?

Thanks.

Seth

Trey

You add the attributes to the [left]iwsearch-home

\etc\FieldMapping.xml

Now, you must index the content with the search indexer before this will work. Also, unless you enable the workarea for seach which is off by default then you can only search submitted content.

[/left]

SethHickel

Thanks for the reply. I found the information about adding of attributes to the FieldMapping .xml file. What I am not finding in the documentation is how to allow users to search across generated files for specific values of EA's.

For instance: If I affect datacapture.cfg and metadata-rules.cfg to allow for gathering a value about the sister-in-law of the author, and I edit FieldMapping.xml so that this value is indexed, what file(s) do I affect to allow "sister-in-law" EA values to be searched by a user selection in the advanced search interface?

Another way to word this question would be:
If I add EA's to files, does the drop-down list of options on the advanced search dynamically pull in those new EA's selections, or is that a fixed list that has to be manually updated? And if it is a manual edit what file(s) do I affect so that the new EA is available to search against via the Advanced Search interface.

Bottom line: I need to be able to allow users to associate EA values with a file and then search against those values in Advanced Search.

Trey

iwsearch-home

\etc\FieldMapping.xml

should be all you need. Have to tried it to see? Be sure to reindex the branch after you made the changes.

SethHickel

I have tried this. Let me outline my steps. Perhaps I am still missing something. I was trying to get the Expiration Date EA to be searchable. I have additional EA's that I need to add but this was an exercise to make sure I could get this to work. So far, I have not been successful.

1. I edited FieldMapping.xml. Please see attached txt file. (Is the fieldStorage use of CustomDate1 correct/required?)

2. I published to my production TeamSite server. The file is located at

\Interwoven\Search\etc

3. I used the CLT commands from d:\Interwoven\Search\bin:
iwdxpurgebr \default\main\NameOfSubBranch
iwndxaddbr \default\main\NameOfSubBranch
iwndxrefreshbr \default\main

4. The Expiration Date is still not showing up in the advanced search UI as a choice in the drop down. I've attached a screen shot showing this.

Trey

In our serach configs we don't use spaces. Not sure if that will make a difference, but you may want to give it a try. (be sure to mod the datacpature config as well). btw the date format looks correct.

TeamSite/Metadata/ExpirationDate

Some other questions.
Have you updated the branches.cfg as well before indexing?
Is the index service running?

HTH

SethHickel

I updated FieldMapping.xml to NOT include the space as suggested.
Interwoven TeamSite Index service is running.

my branches.cfg entries follow.

/default/main/lowescom/content
/default/main/lowescom/spanish
/default/main/lowesnet
/default/main/TS-Administration
/default/main/loweslink
/default/main

I ran iwndxpurgebr \default\main and then ran iwndxrefreshbr for each of the listed branches and sub branches.

Lo and Behold - SUCCESS!

Thank you. I'm not sure if it was the space or something else - but - for the future I will not use spaces.

Thanks again!!

SethHickel

I do still have a question:

In the documentation (Chapter 7 – “Configuring Interwoven Search” pg 123) it states that

“If the fieldType element is an int, float, or date, then the fieldStorage element should respectively be one of CustomInt1 through Custom Int5, …”

Does this mean that there can only be a total of 5 custom int and 5 custom float and 5 custom date EA’s that can be indexed? And, if so, does my first int, as an example, need to need to be referenced as customInt1?

In my case, the Expiration Date fieldStorage I have as CustomDate1. Is this naming convention required? If not, what is an example of what it could be? Could it be ExpirationDate?

Thanks.

Seth