Hello, Ann!
In our latest exchange, on 3 June 2021 at 8:06 [JST], I received from
you:
Beginning Koha user – so haven’t approached the administrators.
>
So are we. Only a little over two years.
> I knew you could do this with MarcEdit – we use this extensively for
> post-processing.
Hello!
In our latest exchange, on 2 June 2021 at 17:23 [JST], I received from
you:
Sorry, I don't seem to be authorized to respond on the list.
>
Sorry about that. Have you contacted the administrators to see whether
you can so authorised?
> However, you can indeed use Marc
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
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
Hi Charles,
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:
Hello, all!
A bit off topic from Koha, but here goes.
Our catalog has quite a few records that have translated title (242)
fields. Alas, while the translated titles display in the OPAC and the staff
cataloging module, they are not searchable. Through experimentation, I have
learned that
6 matches
Mail list logo
