Discussion:
[Koha] Encoding and Character Sets in Koha
Narcis Garcia
2018-08-23 07:22:39 UTC
Permalink
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.

MariaDB works with character set utf8mb4
Apache works with charset UTF-8
All Koha database tables have collarion utf8_unicode_ci
Koha HTML output is UTF-8 encoded and includes Content-Type... charset=utf-8

Using Koha 17.11.06-1 on Debian 9.

I don't find Koha's system preferences about this. What can I review?

Thanks.
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
htt
Narcis Garcia
2018-08-23 13:09:19 UTC
Permalink
I sent you a complete export of MARC framework.
Hi Narcis,
 
I am sorry, but that's not the MARC record. Please check if you have the
LDR/000 in your MARC framework. You can also copy the MARC from the MARC
view on the staff detail page (link below the bibliographic details).
 
Katrin
 
*Gesendet:* Donnerstag, 23. August 2018 um 13:06 Uhr
*Betreff:* Re: Encoding and Character Sets in Koha
We are using own framework derived from default one.
No tag added or removed to framework; only changed visibilities and
captions.
SELECT * FROM koha_biblio.biblio WHERE biblionumber = 2;
+--------------+---------------+------------------+-------------------+----------+-------+--------+-------------+---------------+---------------------+-------------+----------+
| biblionumber | frameworkcode | author           | title             |
unititle | notes | serial | seriestitle | copyrightdate |
timestamp           | datecreated | abstract |
+--------------+---------------+------------------+-------------------+----------+-------+--------+-------------+---------------+---------------------+-------------+----------+
|            2 | FIG           | Hammet, Dashiell | El halcon Maltés  |
NULL     | NULL  |      0 | NULL        |          NULL | 2018-06-19
11:43:59 | 2018-06-19  | NULL     |
+--------------+---------------+------------------+-------------------+----------+-------+--------+-------------+---------------+---------------------+-------------+----------+
 
 
Hi,
 
how did you catalog them? Did you use a standard or a modified
framework? Z39.50/SRU? Can you show us the MARC of your record?
 
Hope this helps,
 
Katrin
 
*Gesendet:* Donnerstag, 23. August 2018 um 09:22 Uhr
*Betreff:* [Koha] Encoding and Character Sets in Koha
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
MariaDB works with character set utf8mb4
Apache works with charset UTF-8
All Koha database tables have collarion utf8_unicode_ci
Koha HTML output is UTF-8 encoded and includes Content-Type...
charset=utf-8
Using Koha 17.11.06-1 on Debian 9.
I don't find Koha's system preferences about this. What can I review?
Thanks.
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lists.katipo
Michael Kuhn
2018-08-24 14:59:04 UTC
Permalink
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
MariaDB works with character set utf8mb4
Apache works with charset UTF-8
All Koha database tables have collarion utf8_unicode_ci
Koha HTML output is UTF-8 encoded and includes Content-Type...
charset=utf-8
Using Koha 17.11.06-1 on Debian 9.
I don't find Koha's system preferences about this. What can I review?
Just an idea: Did you check what character set is used by your webbrowser?

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E ***@adminkuhn.ch · W www.adminkuhn.ch
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinf
Narcis Garcia
2018-08-24 16:11:33 UTC
Permalink
Recorded "El Halcon Maltés" is presented as "El halcon Maltš"

Bad viewed with tested browsers:
M. Firefox: UTF-8 (no luck switching to central european ISO / Windows)
Gnu Icecat: UTF-8 (no luck switching to central european ISO / Windows)
Midori: Unicode (no luck switching to UTF-8 / ISO-8859-1)
Epiphany (Gnome web): (no idea but same bad characters)
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
MariaDB works with character set utf8mb4
Apache works with charset UTF-8
All Koha database tables have collarion utf8_unicode_ci
Koha HTML output is UTF-8 encoded and includes Content-Type...
charset=utf-8
Using Koha 17.11.06-1 on Debian 9.
I don't find Koha's system preferences about this. What can I review?
Just an idea: Did you check what character set is used by your webbrowser?
Best wishes: Michael
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
ht
Michael Kuhn
2018-08-24 16:24:12 UTC
Permalink
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?

What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?

Is your Koha OPAC maybe accessible, and if yes what is the URL?

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E ***@adminkuhn.ch · W www.adminkuhn.ch
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lists
Narcis Garcia
2018-08-25 09:44:27 UTC
Permalink
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
Michael Kuhn
2018-08-25 10:05:44 UTC
Permalink
Hi
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
Do you mean the following that you have sent only to Katrin Fischer?

SELECT * FROM koha_biblio.biblio WHERE biblionumber = 2;
+--------------+---------------+------------------+-------------------+----------+-------+--------+-------------+---------------+---------------------+-------------+----------+
| biblionumber | frameworkcode | author | title |
unititle | notes | serial | seriestitle | copyrightdate |
timestamp | datecreated | abstract |
+--------------+---------------+------------------+-------------------+----------+-------+--------+-------------+---------------+---------------------+-------------+----------+
| 2 | FIG | Hammet, Dashiell | El halcon Maltés |
NULL | NULL | 0 | NULL | NULL | 2018-06-19
11:43:59 | 2018-06-19 | NULL |
+--------------+---------------+------------------+-------------------+----------+-------+--------+-------------+---------------+---------------------+-------------+----------+

I can't see anything wrong about the encoding here.

That's why I asked for some examples. What exactly is wrong for what
characters? Does "Maltés" show up as "Maltš"?
Post by Narcis Garcia
As "Koha web interface" I meant both OPAC and staff area.
So is at least your Koha OPAC maybe accessible, and if yes what is the URL?

You should give more information.

Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E ***@adminkuhn.ch · W www.adminkuhn.ch
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https:
Katrin Fischer
2018-08-26 17:27:05 UTC
Permalink
Hi Narics,

try the following:

In your MARC framework, make the LDR 000 @ visible in the editor again.
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record again, see
if that fixes your problem.

Note: the leader contains information about the encoding of the record,
if the LDR is missing, you can get records that behave strangely.

Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
htt
Narcis Garcia
2018-08-29 08:09:45 UTC
Permalink
From: koha-***@lists.katipo.co.nz
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"

I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.


Thank you Katrin for the 000@ subfield steps, but now I see that
behaviour strange:
To a MARC21 record is shown properly with unicode strings, it must be
typed and saved 2 times:
- First time it's saved right, but characters are shown bad on any Koha
web interface.
- After editing, re-typing and re-saving, all things are right (database
data and web representation).

If I set and leave [MARC21]000@ subfield with Visibility:Editor=Disabled
Then a JS error message prevents I save new catalog records:
"Can't save this record because the following field aren't filled:
* tag 000 subfield 0 campo de control de longitud fija in tab 9"

Does ***@0 subfield expect a constant value for any new record, or
different value on each record? Can I default some pre-fixed value, or
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lis
Katrin Fischer
2018-08-30 20:08:36 UTC
Permalink
Hi Narcis,

000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record for the
first time.

- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?

If the LDR is there, new records should display ok without need to edit
them again.

Katrin
Post by Narcis Garcia
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.
To a MARC21 record is shown properly with unicode strings, it must be
- First time it's saved right, but characters are shown bad on any Koha
web interface.
- After editing, re-typing and re-saving, all things are right (database
data and web representation).
* tag 000 subfield 0 campo de control de longitud fija in tab 9"
different value on each record? Can I default some pre-fixed value, or
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lists.katipo.c
Narcis Garcia
2018-08-31 08:26:22 UTC
Permalink
- No plugin icon; as far as I know the form icons.
- 000 is mandatory and 000@ is mandatory too; but it has effect only
when Visibility:Editor=Enabled
- When Visibility:Editor=Enabled it only populates a value on click.
When this is done, international characters have full expected behavior
(right recorded and shown).

I understand now that 000@ subfield is required to be visible on catalog
record creation, and must be filled with JS proposed value.
Is there some way to cataloguer people doesn't have to deal with 000@
subfield? A prefilled value?

Thanks.
Hi Narcis,
000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record for the
first time.
- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?
If the LDR is there, new records should display ok without need to edit
them again.
Katrin
Post by Narcis Garcia
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.
To a MARC21 record is shown properly with unicode strings, it must be
- First time it's saved right, but characters are shown bad on any Koha
web interface.
- After editing, re-typing and re-saving, all things are right (database
data and web representation).
* tag 000 subfield 0 campo de control de longitud fija in tab 9"
different value on each record? Can I default some pre-fixed value, or
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lists.katipo.co.nz/mail
Katrin Fischer
2018-09-03 06:00:22 UTC
Permalink
Hi Narcis,

if configured correctly Koha will not let you save the record without
filling in a default value. If it only does fill the LDR if you click in
the field, something is still not quite right in your configuration.

I suggest you try the behavior in one of the available demo databases
and compare your framework configuration with the default.

You can also use the 'default' setting, but getting it to work the
standard would be better I think.

Katrin
Post by Narcis Garcia
- No plugin icon; as far as I know the form icons.
when Visibility:Editor=Enabled
- When Visibility:Editor=Enabled it only populates a value on click.
When this is done, international characters have full expected behavior
(right recorded and shown).
record creation, and must be filled with JS proposed value.
subfield? A prefilled value?
Thanks.
Hi Narcis,
000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record for the
first time.
- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?
If the LDR is there, new records should display ok without need to edit
them again.
Katrin
Post by Narcis Garcia
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.
To a MARC21 record is shown properly with unicode strings, it must be
- First time it's saved right, but characters are shown bad on any Koha
web interface.
- After editing, re-typing and re-saving, all things are right (database
data and web representation).
* tag 000 subfield 0 campo de control de longitud fija in tab 9"
different value on each record? Can I default some pre-fixed value, or
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lists.katipo.co
Narcis Garcia
2018-09-03 08:04:19 UTC
Permalink
I've tested default framework in "Catalyst IT Ltd" demo, and it has same
behaviour: Without clicking in 000/LEADER field, it's not filled and
[Save] action complains about required value.
Hi Narcis,
if configured correctly Koha will not let you save the record without
filling in a default value. If it only does fill the LDR if you click in
the field, something is still not quite right in your configuration.
I suggest you try the behavior in one of the available demo databases
and compare your framework configuration with the default.
You can also use the 'default' setting, but getting it to work the
standard would be better I think.
Katrin
Post by Narcis Garcia
- No plugin icon; as far as I know the form icons.
when Visibility:Editor=Enabled
- When Visibility:Editor=Enabled it only populates a value on click.
When this is done, international characters have full expected behavior
(right recorded and shown).
record creation, and must be filled with JS proposed value.
subfield? A prefilled value?
Thanks.
Hi Narcis,
000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record for the
first time.
- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?
If the LDR is there, new records should display ok without need to edit
them again.
Katrin
Post by Narcis Garcia
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.
To a MARC21 record is shown properly with unicode strings, it must be
- First time it's saved right, but characters are shown bad on any Koha
web interface.
- After editing, re-typing and re-saving, all things are right
(database
data and web representation).
Visibility:Editor=Disabled
* tag 000 subfield 0 campo de control de longitud fija in tab 9"
different value on each record? Can I default some pre-fixed value, or
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
again.
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record
again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the
record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well
saved
strings at database (from OS console), but Koha web interface is
not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the
staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://lists.katipo.co.nz/m
Tomas Cohen Arazi
2018-09-03 13:09:32 UTC
Permalink
Narcis, what you describe is the expected behaviour: you need to click on
the field to get it filled. Not a bug, but the expected behaviour.
Post by Narcis Garcia
I've tested default framework in "Catalyst IT Ltd" demo, and it has same
behaviour: Without clicking in 000/LEADER field, it's not filled and
[Save] action complains about required value.
Hi Narcis,
if configured correctly Koha will not let you save the record without
filling in a default value. If it only does fill the LDR if you click in
the field, something is still not quite right in your configuration.
I suggest you try the behavior in one of the available demo databases
and compare your framework configuration with the default.
You can also use the 'default' setting, but getting it to work the
standard would be better I think.
Katrin
Post by Narcis Garcia
- No plugin icon; as far as I know the form icons.
when Visibility:Editor=Enabled
- When Visibility:Editor=Enabled it only populates a value on click.
When this is done, international characters have full expected behavior
(right recorded and shown).
catalog
Post by Narcis Garcia
record creation, and must be filled with JS proposed value.
subfield? A prefilled value?
Thanks.
Hi Narcis,
000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record for the
first time.
- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?
If the LDR is there, new records should display ok without need to edit
them again.
Katrin
Post by Narcis Garcia
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.
To a MARC21 record is shown properly with unicode strings, it must be
- First time it's saved right, but characters are shown bad on any
Koha
Post by Narcis Garcia
Post by Narcis Garcia
web interface.
- After editing, re-typing and re-saving, all things are right (database
data and web representation).
Visibility:Editor=Disabled
* tag 000 subfield 0 campo de control de longitud fija in tab 9"
different value on each record? Can I default some pre-fixed value, or
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
✆ +54 9351 3513384
GPG: B2F3C15F
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
https://li
Katrin Fischer
2018-09-03 21:24:48 UTC
Permalink
It's correct that it complains, but if you check the LDR, it will now
have a default value and you can directly hit save again.
Post by Narcis Garcia
I've tested default framework in "Catalyst IT Ltd" demo, and it has same
behaviour: Without clicking in 000/LEADER field, it's not filled and
[Save] action complains about required value.
Hi Narcis,
if configured correctly Koha will not let you save the record without
filling in a default value. If it only does fill the LDR if you click in
the field, something is still not quite right in your configuration.
I suggest you try the behavior in one of the available demo databases
and compare your framework configuration with the default.
You can also use the 'default' setting, but getting it to work the
standard would be better I think.
Katrin
Post by Narcis Garcia
- No plugin icon; as far as I know the form icons.
when Visibility:Editor=Enabled
- When Visibility:Editor=Enabled it only populates a value on click.
When this is done, international characters have full expected behavior
(right recorded and shown).
record creation, and must be filled with JS proposed value.
subfield? A prefilled value?
Thanks.
Hi Narcis,
000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record for the
first time.
- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?
If the LDR is there, new records should display ok without need to edit
them again.
Katrin
Post by Narcis Garcia
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.
To a MARC21 record is shown properly with unicode strings, it must be
- First time it's saved right, but characters are shown bad on any Koha
web interface.
- After editing, re-typing and re-saving, all things are right
(database
data and web representation).
Visibility:Editor=Disabled
* tag 000 subfield 0 campo de control de longitud fija in tab 9"
different value on each record? Can I default some pre-fixed value, or
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
again.
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the record
again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the
record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well
saved
strings at database (from OS console), but Koha web interface is
not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the
staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
Narcis Garcia
2018-09-03 13:12:26 UTC
Permalink
What if the user types something there by mistake?
Post by Tomas Cohen Arazi
Narcis, what you describe is the expected behaviour: you need to click
on the field to get it filled. Not a bug, but the expected behaviour.
I've tested default framework in "Catalyst IT Ltd" demo, and it has same
behaviour: Without clicking in 000/LEADER field, it's not filled and
[Save] action complains about required value.
Hi Narcis,
if configured correctly Koha will not let you save the record without
filling in a default value. If it only does fill the LDR if you
click in
the field, something is still not quite right in your configuration.
I suggest you try the behavior in one of the available demo databases
and compare your framework configuration with the default.
You can also use the 'default' setting, but getting it to work the
standard would be better I think.
Katrin
Post by Narcis Garcia
- No plugin icon; as far as I know the form icons.
when Visibility:Editor=Enabled
- When Visibility:Editor=Enabled it only populates a value on click.
When this is done, international characters have full expected
behavior
Post by Narcis Garcia
(right recorded and shown).
catalog
Post by Narcis Garcia
record creation, and must be filled with JS proposed value.
subfield? A prefilled value?
Thanks.
Hi Narcis,
000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record
for the
Post by Narcis Garcia
first time.
- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?
If the LDR is there, new records should display ok without need
to edit
Post by Narcis Garcia
them again.
Katrin
Post by Narcis Garcia
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post
to the
Post by Narcis Garcia
Post by Narcis Garcia
list. I had to format it in HTML to present some SQL table
properties.
Post by Narcis Garcia
Post by Narcis Garcia
To a MARC21 record is shown properly with unicode strings, it
must be
Post by Narcis Garcia
Post by Narcis Garcia
- First time it's saved right, but characters are shown bad on
any Koha
Post by Narcis Garcia
Post by Narcis Garcia
web interface.
- After editing, re-typing and re-saving, all things are right
(database
data and web representation).
Visibility:Editor=Disabled
* tag 000 subfield 0 campo de control de longitud fija in tab 9"
different value on each record? Can I default some pre-fixed
value, or
Post by Narcis Garcia
Post by Narcis Garcia
the only way is to create + review each new catalog record at all?
Post by Katrin Fischer
Hi Narics,
again.
Open the record, make sure the field is filled, save it. The
plugin
Post by Narcis Garcia
Post by Narcis Garcia
Post by Katrin Fischer
linked to the LDR should take care of setting some sensible
default
Post by Narcis Garcia
Post by Narcis Garcia
Post by Katrin Fischer
value just by clicking into the field. Try to view the record
again, see
if that fixes your problem.
Note: the leader contains information about the encoding of the
record,
if the LDR is missing, you can get records that behave strangely.
Katrin
Post by Narcis Garcia
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
Hi Narcis
Post by Narcis Garcia
When cataloguing books with non-english characters, I see well
saved
strings at database (from OS console), but Koha web
interface is
Post by Narcis Garcia
Post by Narcis Garcia
Post by Katrin Fischer
Post by Narcis Garcia
Post by Narcis Garcia
not
showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "Koha web interface" - is this the
staff
client or the OPAC or both?
Is your Koha OPAC maybe accessible, and if yes what is the URL?
Best wishes: Michael
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
https://lists.katipo.co.nz/mailman/listinfo/koha
--
Tomás Cohen Arazi
Theke Solutions (https://theke.io <http://theke.io/>)
✆ +54 9351 3513384
GPG: B2F3C15F
_______________________________________________
Koha mailing list http://koha-community.org
***@lists.katipo.co.nz
h
Loading...