Hi Charles, I don't have much experience with Elasticsearch yet, but it should not be hard to add the field to an existing index. This might be helpful:
https://koha-community.org/manual/21.05/en/html/administration.html?highlight=elastic#search-engine-configuration Hope this helps, Katrin On 02.06.21 06:57, Charles Kelley wrote:
Hello, Katrin et al! In our latest exchange, on 2 Jun 2021 at 9:01 [JST], I received from Katrin Fischer: I wonder if it would not be the easier solution to make 242 searchable?Are you using Zebra or Elasticsearch? If there are other advantages of putting the information in 740 as well, the "Build new field" feature might be what you are looking for: https://marcedit.reeset.net/build-new-field Hope this helps,We're running Koha v. 20.05 under ElasticSearch. We installed ElasticSearch because of the multilingual nature of the collection; and we could not get Zebra to work with the collection. I would love to make 242 and other fields searchable, and it looks like ElasticSearch has that ability built in. Unfortunately, searchability of field XXX has to be turned on and I don't know how to do so. From what I understand, Bywater Solutions or another third party can help with this. Our system is behind an airtight firewall, as it were, and that precludes another party from turning it on for us. That said, the interim solution of duplicating 242 fields into 740 fields works perfectly. Thanks for the solution.
_______________________________________________ Koha mailing list http://koha-community.org [email protected] Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
