Limiting search fields.

[Atom Fundceri]

Good morning.
I was wondering if there´s any way to default limit search fields so some of them aren´t object of the search query. In this case, I´d like to know if there´s any way to prevent Decription Control Area from searchs as I understand this field to be an internal control field, or maybe to prevent notes from appearing in the results.

Thank you everyone.

[Dan Gillean]

Hi there, 

I did a bit of searching online in various forums for Elasticsearch 5.6 (the version that AtoM currently uses), and unfortunately I couldn't find any way of an end-user specifying a field to exclude while searching. 

If you are a developer comfortable making local code customizations to the application then you could modify the search index itself, and exclude notes from archival description searches for everyone, for example, but I couldn't find a per-search way of doing so. 

Keep in mind that presently, I don't think the Description Control field is even indexed, and we do apply some basic weighting to results - so a search term match in a description's Title (or even Scope and Content) is going to appear much higher in your results than a match in the Archivist's Notes field, for example.

We have a list of indexed fields for descriptions in the documentation here: 

• https://www.accesstomemory.org/docs/2.7/user-manual/access-content/advanced-search/#list-of-archival-description-es-fields
  

In general, this section of the documentation has some advanced search tips and tricks that don't exactly cover this request, but might be helpful nonetheless. See also: 

• https://www.slideshare.net/accesstomemory/searching-in-atom-103945925
  

If you did want to alter AtoM's search index, the mapping.yml and search.yml files will be the mains ones to edit, in the arElasticsearchPlugin. See for example: 

• https://github.com/artefactual/atom/blob/qa/2.x/plugins/arElasticSearchPlugin/config/mapping.yml#L477
  

Here's a recent pull request that shows how one of our developers removed an indexed field from the description results: 

• https://github.com/artefactual/atom/pull/1654/files
  

Be sure to restart PHP-FPM and Elasticsearch after making changes, and clear the application cache. 

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

he / him

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/c06cab2c-27a7-490b-bc59-b7cf74e3b9f5n%40googlegroups.com.