Exclude certain fields from searching?

stefan

You can exclude fields from being indexed but then you can't search them at all, not even if you specifically ask for it.

To do that, you'd list them under the DONT_INDEX setting for the "virtual" metadata field for that table in search_indexing.conf, like so:

_metadata = {

DONT_INDEX = { author, description }

}

I haven't tried it in a while but that should work.

moronic

Which table is this for object metadata I created myself?

stefan

If it's metadata associated with objects, the table is ca_objects.

moronic

Like this? ca_objects = { fields = { _metadata = { DONT_INDEX = { meta1, meta2, meta3 } },

stefan

Yes ... well there should be an addition "table" block around what you posted, but yes.

moronic

I just copied and pasted from the file, I just added the DONT_INDEX part.

There was no table block, so I need more help. 

stefan

The config should be something like 

table = {

table1 = {

table2 = {

table3 = {

 }

tableA = {

...

 }

_metadata is usually just indexed for the primary table, i.e. object metadata is indexed for objects. So the part that you copied makes sense, it's just missing the surrounding "primary" table block (which is probably "ca_objects" too).

The config is structured this way because it's possible and very important that we index data from related tables, for instance names for entities related to objects, so that you can search objects by artist or creator.

moronic

A related question: there is a "search_indexing.conf" in both Pawtucket and Providence. I'm guessing the Pawtucket one is irrelevant?

moronic

It seems to have no effect. Attaching file - relevant line is 140, I think.

Uhm, can't seem to upload the file. But it is the standard file include in the install. https://github.com/collectiveaccess/providence/blob/master/app/conf/search_indexing.conf</div><div>All I did was add my stuff between on this line:

_metadata = {DONT_INDEX = {notes,price,insurancevalue}}, # forces indexing of all attributes

seth

The search_indexing.conf file in Pawtucket is used when it creates records in the database, so it's relevant if you're allowing users to tag, comment or contribute new records via the "contribute" plugin.

seth

Also, if you're using Pawtucket2 (the new version, which is in development on GitHub) you can set a "restrictSearchToFields" option for specific types of search that will implicitly limit unqualified searches to selected fields. This sounds like it is what you want: you can still index fields that you don't want searched by default. 

There is no way to configure this option in Providence at the moment – I don't think anyone expected it'd be needed there – but the configuration options could be added. If you want it create a JIRA for it please.

seth

mbutel

seth is this option currently working? Could you supply and example on how to use it in the .conf file?

stefan

A last note: When you change the search indexing configuration, you have to reindex the database contents (or save every record by hand once), otherwise it won't have any effect retroactively.

moronic

Still on Pawtucket 1. 

And I am trying to limit searches from Pawtucket, I don't mind if it shows up inside Providence. 

Yes, I have run the Rebuild search indices multiple times, but it seems to have no effect. 

...

And of course now it does. I can't tell why though...

Thank you for your patience.