Open Source Document Management System | OpenKM

I have a metadata field (text) for Social Security Numbers. (###-##-####).

Given the number: 123-45-6789, I can use the Advanced Search -> MetaData -> Funeral Group -> SSI field and search for 123-45-6789. That comes up perfectly. If, however, I search for 123* or *6789, it comes up with nothing. Is there someway to specify wildcard searching on metadata fields, or is that simply not an option? I've been looking through the docs and I can't seem to figure it out.

I'm using community 6.2.0 build 13077.

Thanks.

Probably there's a problem with default lucene tokenizer. Default tokenizer split word when found some special characters like ., and seems - too. 123-456-789 are tokenized by lucene to 3 words 123 456 and 789 and that causes the search problem.

I think here you got two options; or change the default tokenizer ( will need rebuild Lucene indexes which is fast operation ) or change character - to _ or simply remove -

Thanks for your prompt reply. You have been very responsive to all of my inquires and that has been very helpful. I have tested a bit further and I'm having problems with text property fields. I have the following:
and I have the phrase "Hello World" in the phrasetest field of a document. However, when I search for "Hello World" or "Hello*", nothing comes up. The only thing that I can get to work correctly is the Date of Death field and a specific SS#, but not a SS# with a wildcard. I get the problem with "-"'s, but even when I replace the "-"''s with letters, the wildcards still don't work. I have rebuilt my lucene indexes.

I did create the phrasetest and link fields created AFTER I created and registered the Date of Death and Social Security # fields. Could that be a problem?

Any ideas?

Thanks.

I have tested in professional version at our online demo and goes right, you can test yourself, could be a bug on community version but is strange because these parts are so similar. Can you test in our online demo and confirm goes right but not in your community version ?

I went to the demo site, ( http://demo.openkm.com/OpenKM/login.jsp ). Searching worked perfectly fine, exactly the way I would expect it to. I then made a completely brand new install of the community edition, using as few changes as possible to the default configuration. I get the exact same result as before.

I installed using the file: openkm-6.2.0-community-linux-installer.run md5: b806bca75db473d02c6392e1791ae2ab on Linux Ubuntu 11.04. I've had no problems with any of the other openkm app. This seems to be the only problem.

BTW, on the online demo, 123* AND 123-* worked, so apparently the dashes aren't an issue with lucene.

Please, try a recent nightbuild from http://integration.openkm.com/6.2/ because we want to make a release soon and need feedback from users.

I tested using the nightly build: 6.2.3-DEV build 7928 with Community Extension.

Searching appears to work perfectly in that version. So whatever happened appears to be fixed since the community download I used.

Good to know. Thank for testing.