I sent you a complete export of MARC framework. El 23/08/18 a les 15:07, Katrin Fischer ha escrit:
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 *Von:* "Narcis Garcia" <informatica@actiu.net> *An:* "Katrin Fischer" <Katrin.Fischer.83@web.de> *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 | +--------------+---------------+------------------+-------------------+----------+-------+--------+-------------+---------------+---------------------+-------------+----------+
El 23/08/18 a les 09:43, Katrin Fischer ha escrit:
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 *Von:* "Narcis Garcia" <informatica@actiu.net> *An:* "Koha list" <koha@lists.katipo.co.nz> *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 Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi Narcis You wrote:
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 mik@adminkuhn.ch · W www.adminkuhn.ch
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) El 24/08/18 a les 16:59, Michael Kuhn ha escrit:
Hi Narcis
You wrote:
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
Hi Narcis You wrote:
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 mik@adminkuhn.ch · W www.adminkuhn.ch
Didn't see the "El halcon Maltš" example? As "Koha web interface" I meant both OPAC and staff area. El 24/08/18 a les 18:24, Michael Kuhn ha escrit:
Hi Narcis
You wrote:
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
Hi
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š"?
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 mik@adminkuhn.ch · W www.adminkuhn.ch
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 On 25.08.2018 11:44, Narcis Garcia wrote:
Didn't see the "El halcon Maltš" example? As "Koha web interface" I meant both OPAC and staff area.
El 24/08/18 a les 18:24, Michael Kuhn ha escrit:
Hi Narcis
You wrote:
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 Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
From: koha-owner@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 000@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? El 26/08/18 a les 19:27, Katrin Fischer ha escrit:
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
On 25.08.2018 11:44, Narcis Garcia wrote:
Didn't see the "El halcon Maltš" example? As "Koha web interface" I meant both OPAC and staff area.
El 24/08/18 a les 18:24, Michael Kuhn ha escrit:
Hi Narcis
You wrote:
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 Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
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 On 29.08.2018 10:09, Narcis Garcia wrote:
From: koha-owner@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 000@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?
El 26/08/18 a les 19:27, Katrin Fischer ha escrit:
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
On 25.08.2018 11:44, Narcis Garcia wrote:
Didn't see the "El halcon Maltš" example? As "Koha web interface" I meant both OPAC and staff area.
El 24/08/18 a les 18:24, Michael Kuhn ha escrit:
Hi Narcis
You wrote:
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 Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
- 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. El 30/08/18 a les 22:08, Katrin Fischer ha escrit:
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
On 29.08.2018 10:09, Narcis Garcia wrote:
From: koha-owner@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 000@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?
El 26/08/18 a les 19:27, Katrin Fischer ha escrit:
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
On 25.08.2018 11:44, Narcis Garcia wrote:
Didn't see the "El halcon Maltš" example? As "Koha web interface" I meant both OPAC and staff area.
El 24/08/18 a les 18:24, Michael Kuhn ha escrit:
Hi Narcis
You wrote:
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 Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
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 On 31.08.2018 10:26, Narcis Garcia wrote:
- 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.
El 30/08/18 a les 22:08, Katrin Fischer ha escrit:
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
On 29.08.2018 10:09, Narcis Garcia wrote:
From: koha-owner@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 000@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?
El 26/08/18 a les 19:27, Katrin Fischer ha escrit:
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
On 25.08.2018 11:44, Narcis Garcia wrote:
Didn't see the "El halcon Maltš" example? As "Koha web interface" I meant both OPAC and staff area.
El 24/08/18 a les 18:24, Michael Kuhn ha escrit:
Hi Narcis
You wrote:
> 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 Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
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. El 03/09/18 a les 08:00, Katrin Fischer ha escrit:
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
On 31.08.2018 10:26, Narcis Garcia wrote:
- 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.
El 30/08/18 a les 22:08, Katrin Fischer ha escrit:
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
On 29.08.2018 10:09, Narcis Garcia wrote:
From: koha-owner@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 000@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?
El 26/08/18 a les 19:27, Katrin Fischer ha escrit:
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
On 25.08.2018 11:44, Narcis Garcia wrote:
Didn't see the "El halcon Maltš" example? As "Koha web interface" I meant both OPAC and staff area.
El 24/08/18 a les 18:24, Michael Kuhn ha escrit: > Hi Narcis > > You wrote: > >> 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 Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
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. El lun., 3 sept. 2018 a las 5:05, Narcis Garcia (<informatica@actiu.net>) escribió:
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.
El 03/09/18 a les 08:00, Katrin Fischer ha escrit:
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
On 31.08.2018 10:26, Narcis Garcia wrote:
- 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.
El 30/08/18 a les 22:08, Katrin Fischer ha escrit:
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
On 29.08.2018 10:09, Narcis Garcia wrote:
From: koha-owner@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 000@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?
El 26/08/18 a les 19:27, Katrin Fischer ha escrit:
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
On 25.08.2018 11:44, Narcis Garcia wrote: > Didn't see the "El halcon Maltš" example? > As "Koha web interface" I meant both OPAC and staff area. > > > > El 24/08/18 a les 18:24, Michael Kuhn ha escrit: >> Hi Narcis >> >> You wrote: >> >>> 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 > Koha@lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz 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
What if the user types something there by mistake? El 03/09/18 a les 15:09, Tomas Cohen Arazi ha escrit:
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.
El lun., 3 sept. 2018 a las 5:05, Narcis Garcia (<informatica@actiu.net <mailto:informatica@actiu.net>>) escribió:
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.
El 03/09/18 a les 08:00, Katrin Fischer ha escrit: > 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 > > > On 31.08.2018 10:26, Narcis Garcia wrote: >> - 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. >> >> >> El 30/08/18 a les 22:08, Katrin Fischer ha escrit: >>> 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 >>> >>> >>> On 29.08.2018 10:09, Narcis Garcia wrote: >>>> From: koha-owner@lists.katipo.co.nz <mailto:koha-owner@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 000@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? >>>> >>>> >>>> >>>> El 26/08/18 a les 19:27, Katrin Fischer ha escrit: >>>>> 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 >>>>> >>>>> >>>>> On 25.08.2018 11:44, Narcis Garcia wrote: >>>>>> Didn't see the "El halcon Maltš" example? >>>>>> As "Koha web interface" I meant both OPAC and staff area. >>>>>> >>>>>> >>>>>> >>>>>> El 24/08/18 a les 18:24, Michael Kuhn ha escrit: >>>>>>> Hi Narcis >>>>>>> >>>>>>> You wrote: >>>>>>> >>>>>>>> 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 >>>>>> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> >>>>>> https://lists.katipo.co.nz/mailman/listinfo/koha >>>>> _______________________________________________ >>>>> Koha mailing list http://koha-community.org >>>>> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> >>>>> https://lists.katipo.co.nz/mailman/listinfo/koha >>>> _______________________________________________ >>>> Koha mailing list http://koha-community.org >>>> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> >>>> https://lists.katipo.co.nz/mailman/listinfo/koha >>> _______________________________________________ >>> Koha mailing list http://koha-community.org >>> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> >>> https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> >> https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> 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
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. On 03.09.2018 10:04, Narcis Garcia wrote:
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.
El 03/09/18 a les 08:00, Katrin Fischer ha escrit:
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
On 31.08.2018 10:26, Narcis Garcia wrote:
- 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.
El 30/08/18 a les 22:08, Katrin Fischer ha escrit:
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
On 29.08.2018 10:09, Narcis Garcia wrote:
From: koha-owner@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 000@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?
El 26/08/18 a les 19:27, Katrin Fischer ha escrit:
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
On 25.08.2018 11:44, Narcis Garcia wrote: > Didn't see the "El halcon Maltš" example? > As "Koha web interface" I meant both OPAC and staff area. > > > > El 24/08/18 a les 18:24, Michael Kuhn ha escrit: >> Hi Narcis >> >> You wrote: >> >>> 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 > Koha@lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
participants (4)
-
Katrin Fischer -
Michael Kuhn -
Narcis Garcia -
Tomas Cohen Arazi