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

Metadata Search TS 6.5

bturns

Has anyone enabled the search of Metadata in TS 6.5? I've enabled search on file properties. However, when it comes to custom metadata it appears that the metadata is not being indexed. Does anyone have any suggestions?

Thanks,

Brian

Find more posts tagged with

Comments

iwovGraduate

Were you able to resolve this ?

If so can you post what did you do to fix this ?

If not, can you post what have you tried so far ?
How did you know what metadata is not being indexed ? From the index log file ?

Migrateduser

Did you add your custom metadata to fieldmapping.xml? Most likely you did. Just checking...

Johnny

The problem (oversight) I ran into with this was leaving out the ":zone" portion for a string type.

Have a close look at the example file and read over the paragraphs in the admin manual regarding search.

Strings need :zone and the others (eg date, int) need to use the predefined custom names

EG


                <extendedAttributeFields>
                        <fieldSpecification>
                                <fieldName>Document_AVAILABILITY</fieldName>
                                <fieldType>string</fieldType>
                                <fieldStorage>zoneocument_AVAILABILITY</fieldStorage>
                        </fieldSpecification>

                        <fieldSpecification>
                                <fieldName>Document_EFFECTIVE_DATE</fieldName>
                                <fieldType>date</fieldType>
                                <formatString>dd-MMM-yy</formatString>
                                <fieldStorage>CustomDate1</fieldStorage>
                        </fieldSpecification>

John Cuiuli

CrosstabEmptyCells.JPG

iwovGraduate

Yes I did.
I got it working now. The problem I had was a matter of a little RTFM on fieldStorage element.

The gotchas (as noticed by me.) -

- After changing FieldMapping.xml, you need to restart Index service for it to pick up the new fields.

- For the fieldStorage element in FieldMapping.xml you MUST have one of CustomInt1 through CustomInt5,
CustomFloat1 through CustomFloat5, or CustomDate1 through CustomDate5 for fieldType attribute of int, float or date respectively.

- This implies to me that you can't have 6 (or more) date (or int or float) fields. Its unlikely to have 5+ date fields, but a limitation regardless.

- The indexer is very picky about date formats and its important to carefully RTFM the details on this. The error messages are misleading.

- Even after I removed one of the fields from FieldMapping.xml and then restarted the Index service and then reindexed the branch, the removed field still show up as an option in the Search screen in the UI. Not sure how to remove this. Anybody knows ?

- The index log file shows which attributes are indexed.

- After adding a extended attribute to the FieldMapping, the Indexer did NOT automatically (re-)index the files in Staging for the new field. I had to resubmit the files and reindex the branch to be able to search. (I am not using incremental updates). I guess the indexer looks at which was the last version indexed and compares it with the lastet version in order to determine whether to reindex (ignoring which fields are indexed).

Does anybody have similar or conflicting observations ?

iwovGraduate

Thats exactly what I ran into for the date field. Just had to RTFM a little carefully....

Johnny

Sounds like we were working on the same machine Smiley Happy

John Cuiuli

bturns

I was able to resolve this.

I ran the command:

iwndxrefreshbr -b /default/main/intranet/kpnet_sites/kphealthconnect

it didn't reindex the content right away. The next day when I came in the content was reindexed and searchable. I am now looking for a way to reindex the content on demand through the command line.

smenon

This was probably because it was indexing the content for the baseline index which might have taken some time to finish.. Any subsequent re-indexes should only index the deltas and those should be relatively fast depending on how many files are included in the delta..

--Sunil Menon
Product Manager
Interwoven, Inc.

Migrateduser

According to the CLT manual, there are 2 options for this CLT, -b which is a bulk index, and -i which is an incremental index.

Perhaps the -i would be done right away? It doesn't say in the CLT manual, but it might be worth a shot.

hth,

lissa

Migrateduser

sorry, i just say your later post, I'll see if someone else can lend a hand.

lissa

NathansDIS

Has anyone found out definitively which procedures/commandline options to use to get the branches reindexed after editing fieldmapping.xml? Also, can someone explain which commandline I can use to show me when the reindex operation has completed? Thanks in advance for your time.

Regards,

Nathan Sunderman
Washington State DIS
~~~

iwovGraduate

Did you read my post above in this thread ?

iwovGraduate

... Also, can someone explain which commandline I can use to show me when the reindex operation has completed? ...

iwndxstatus

See the CLT documentation for command line options, etc.
If you see status "11 - Indexed" means its completed. You will see something else (don't remember right now exactly what it is) if the indexing is in progress.

NathansDIS

Thanks for your response IWOV grad. Ya, I read the entire thread. I'm still not sure it says which option to use (b or i) with the iwndxrefreshbr CLT?!? Maybe i'm just missing it. Anyone care to go on record with a definitive answer to this question? Thx again.

NathansDIS

Thanks for the info. I have just been using iwndxstatus -a which does not show the status code you mentioned in your post. Using the -f flag really helps. Guess I should RTFCLTM! -n

bturns

i've used iwndxrefreshbr -i <branch_name> and it works great.

You can go into your index reporsitory (<index-home>/parts/) and see the index created within about 5 minutes of running the command line.

after that if you run iwsrchndxstatus -f <branch_name> the response will give the date of the most recent index.

Here is an example:

bash-2.05$ iwsrchndxstatus -f /default/main/intranet/kpnet_sites/kphealthconnect/
Index status for branch: //ktazd1064/default/main/intranet/kpnet_sites/kphealthconnect
Index Status: 11 - Indexed
Edition Creation Time: Mon Mar 14 16:42:41 2005
Collections:
00000001000000000000005100000064000000000000202000008D590000000000002250_1

DavidMusser

Were you able to get these EA's to sort in the Advanced GUI? It seams to me that some of them show up at the beginning of the drop down, and others at the end but no real reason to it.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

smenon

I am not sure if you have already seen this. We published a KB article that describes how to configure and run search for a few sample queries using the CLTs and using CSSDK. I believe that the KB article number is 54140 available at

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=54140

...lissa made the link a hyperlink.

thanks
Sunil

--Sunil Menon
Product Manager
Interwoven, Inc.

Edited by lissa on 05/23/05 12:34 PM (server time).

DavidMusser

I had not seen that thank you, but what I'm looking for is if you can sort (not the results) but the advanced search drop down list. When I updated the config to include my metadata fields expiration etc. They show up in the drop down list, but there is no real order to them.

Some of them are at the top, but some are at the bottom. This is the indexed drop down list.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01