Problem with 24.05.01 windows stalls with "processing" box
Hi everybody we have a Koha 23.11 with it_IT language installed and well running on a Debian 11 system. While doing a ordinary system update (sudo apt get update / sudo apt get upgrade) I'm asked to change repository for Koha-common from 23 to 24. I agreed. The update seems to reach the end without any error and when I log in the version installed is 24.05.01 But trying to open a bibio record from intranet interface a box with the word "Processing..." appears and the windows stalls. I attach a screenshot of the "Processing..." box and the installation log. Koha logs seem clean. If you have any idea it will be very helpful. thanks tommaso
Hi. The main cause of this issue is problems with your item data. This includes: 1. Items not having a home library and current library (both are required). 2. Item date fields that have 0000-00-00 - these need to be an actual date or NULL (includes 952$d - Date acquired, 952$w - Price effective from). 3. Invalid entries for any of the item fields that use authorized values - the values need to match what is in your authorized values lists. You can still edit items by going to Edit > Edit items. Ways to fix the incorrect data (open for any suggestions here): 1. Use reports to find incorrect data and then use the item batch modification tool to fix them up (Cataloging > Batch editing > Batch item modification). 2. Update items directly in the database using SQL - item data is in the items table (not recommended unless you know what you are doing - make a database backup first!). 3. ... please comment if you know other ways. Why did this happen? Bug 33568 - Use the REST API to display items on the biblio detail view. This important enhancement in 24.05.00 significantly improves the display of the holdings table when then are a very large number of items. However, it is much more "fussy" about all the item data being valid. Some causes of incorrect data that may have crept in to your system: imported or migrated data may have been incomplete, or MARC frameworks that don't make the home and current library mandatory (there are probably other things as well). Why did your system automatically upgrade from 23.11(?? - guessing here) to 24.05.01? Check how your package sources list is set up. If you used codenames (like stable, oldstable), then as soon as a new major version is released (in this case 24.05 in late May 2024), when you run your update and upgrade commands, then it will upgrade you to the next major release. Despite the best efforts of the release team, there can be unexpected issues with new major releases (the .05 and .11 versions released every six months). Many Koha libraries often wait until after the first few maintenance releases to upgrade, as most of the significant issues are sorted out by then. In the future, if you don't want to upgrade to the next major release until you have tested in a test environment (highly recommended!), then update your package sources to use the version number. I've tried to update the installation instructions to explain this: https://wiki.koha-community.org/wiki/Koha_on_Debian#Choosing_what_Koha_relea... My explanation of what you get with the different releases: - If you want the *most bug-free* release of Koha at any given time, you should track the oldoldstable or oldoldoldstable (long term support) branch. - If you want the *most feature rich* release of Koha and don't mind dealing with bugs every few months, then track the stable branch. - The *happy middle ground* of oldstable will get new features six months later than stable, but should be considerably more tried and tested, and as such more bug free. What you can do now: 1. Stay on 24.05 and fix your item date - depending on the number of items you have, your skills, and the time available, this could take a while (note that your OPAC will still work OK). (The next maintenance release (24.05.02) is just around the corner - it fixes other known issues, such as some forms not working, but won't fix your item data). 2. Restore your system to before your upgrade from your backups/system images (extreme care required, as always). David Nind New Zealand On Sun, 21 Jul 2024 at 04:33, <spazzali@magritte.it> wrote:
Hi everybody
we have a Koha 23.11 with it_IT language installed and well running on a Debian 11 system.
While doing a ordinary system update (sudo apt get update / sudo apt get upgrade) I'm asked to change repository for Koha-common from 23 to 24. I agreed.
The update seems to reach the end without any error and when I log in the version installed is 24.05.01
But trying to open a bibio record from intranet interface a box with the word "Processing..." appears and the windows stalls.
I attach a screenshot of the "Processing..." box and the installation log.
Koha logs seem clean.
If you have any idea it will be very helpful.
thanks tommaso
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Hi David, thanks for your quick reply. Looking for the wrong fields I edited the items of some records and they look ok We don't make loan and in general we fill: items.withdrawn 995 0 (default) items.itemlost 995 2 (default) items.restricted 995 3 (default) items.dateaccessioned 995 5 (dd/mm/yyyy, filled with the calendar widget) items.homebranch 995 b items.holdingbranch 995 c items.notforloan 995 o (not for loan) items.itype 995 r sometimes we use items.itemnotes 995 u but rarely not more than that. In the table under the "Processing..." box there are fields that we don't use and even fields I don't know at all (i.e. "Serial enumeration chronology") I guess that there isn't a REST Api log or a debug mode that shows where the problem is. I also create a new BiblioRecord with a new Item but the problems remains the same. We started with Koha in 2016 (Koha 16.5) and generally we always update to the last Stable versions with no problems. Now if the problem might be in one (or a bounch) of the thousands items we are dealing it could be difficult catch the wrong record. On the contrary if the problem should be in the Items I am opening the BiblioRecord of (generally there is a single item for each BiblioRecord) I must know where it is to fix it. I can easily make a rollback because I still have an image with data and Koha23 installed. In general I would prefer to have the possibility to upgrade to the latest version but I can wait. It depends if this behaviour is considered as a "bug" or a "feature". In the last case I have to correct the Items or keep Koha23 forever. Thanks again for your help tommaso Da: "David Nind" <david@davidnind.com> Per: spazzali@magritte.it Cc: koha@lists.katipo.co.nz Data: 20/07/2024 21.43 Oggetto: Re: [Koha] Problem with 24.05.01 windows stalls with "processing" box Hi. The main cause of this issue is problems with your item data. This includes: 1. Items not having a home library and current library (both are required). 2. Item date fields that have 0000-00-00 - these need to be an actual date or NULL (includes 952$d - Date acquired, 952$w - Price effective from). 3. Invalid entries for any of the item fields that use authorized values - the values need to match what is in your authorized values lists. You can still edit items by going to Edit > Edit items. Ways to fix the incorrect data (open for any suggestions here): 1. Use reports to find incorrect data and then use the item batch modification tool to fix them up (Cataloging > Batch editing > Batch item modification). 2. Update items directly in the database using SQL - item data is in the items table (not recommended unless you know what you are doing - make a database backup first!). 3. ... please comment if you know other ways. Why did this happen? Bug 33568 - Use the REST API to display items on the biblio detail view. This important enhancement in 24.05.00 significantly improves the display of the holdings table when then are a very large number of items. However, it is much more "fussy" about all the item data being valid. Some causes of incorrect data that may have crept in to your system: imported or migrated data may have been incomplete, or MARC frameworks that don't make the home and current library mandatory (there are probably other things as well). Why did your system automatically upgrade from 23.11(?? - guessing here) to 24.05.01? Check how your package sources list is set up. If you used codenames (like stable, oldstable), then as soon as a new major version is released (in this case 24.05 in late May 2024), when you run your update and upgrade commands, then it will upgrade you to the next major release. Despite the best efforts of the release team, there can be unexpected issues with new major releases (the .05 and .11 versions released every six months). Many Koha libraries often wait until after the first few maintenance releases to upgrade, as most of the significant issues are sorted out by then. In the future, if you don't want to upgrade to the next major release until you have tested in a test environment (highly recommended!), then update your package sources to use the version number. I've tried to update the installation instructions to explain this: https://wiki.koha-community.org/wiki/Koha_on_Debian#Choosing_what_Koha_relea... My explanation of what you get with the different releases: If you want the most bug-free release of Koha at any given time, you should track the oldoldstable or oldoldoldstable (long term support) branch. If you want the most feature rich release of Koha and don't mind dealing with bugs every few months, then track the stable branch. The happy middle ground of oldstable will get new features six months later than stable, but should be considerably more tried and tested, and as such more bug free. What you can do now: 1. Stay on 24.05 and fix your item date - depending on the number of items you have, your skills, and the time available, this could take a while (note that your OPAC will still work OK). (The next maintenance release (24.05.02) is just around the corner - it fixes other known issues, such as some forms not working, but won't fix your item data). 2. Restore your system to before your upgrade from your backups/system images (extreme care required, as always). David Nind New Zealand On Sun, 21 Jul 2024 at 04:33, <spazzali@magritte.it> wrote: Hi everybody we have a Koha 23.11 with it_IT language installed and well running on a Debian 11 system. While doing a ordinary system update (sudo apt get update / sudo apt get upgrade) I'm asked to change repository for Koha-common from 23 to 24. I agreed. The update seems to reach the end without any error and when I log in the version installed is 24.05.01 But trying to open a bibio record from intranet interface a box with the word "Processing..." appears and the windows stalls. I attach a screenshot of the "Processing..." box and the installation log. Koha logs seem clean. If you have any idea it will be very helpful. thanks tommaso _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso. Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden.
Hi. I made the incorrect assumption about the MARC flavour you are using - it looks like you are using UNIMARC. For UNIMARC, the item data is in the 995 fields. As you have created a new record and added your normal item data, and you still get the same 500 error, then it sounds like something else is causing the issue. It may be useful to join https://chat.koha-community.org/ - the mailing list is really useful, but it isn't easy to share screenshots and other information. I've made some comments below, but welcome any other ideas and suggestions! It is also great that you have backups and can restore things to where you were before the upgrade! At the moment, I've run out of ideas! Holdings table change in the staff interface ================================ The change in 24.05 for the holdings table is intended to be a feature, not a bug. However, I think some guidance is required on how to troubleshoot what the issue is, and some solutions to help libraries fix any data or other issues. There could also be actual bugs that need fixing, or at least something to make it easier to identify what records and items have things that are incorrect. I've created *Bug 37416* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37416> - Holdings table 500 errors in the staff interface - how to identify cause and possible solutions, so hopefully the developers and those more technical than me can help on there. Identifying the cause of the 500 error ============================ There may be multiple causes, so I welcome suggestions on how to identify what they are. For 500 errors, there is often more information in the server logs. So that is a place to start to help narrow it down. You could also use the web developer tools for your browser and check the console to see if there are any other errors there. I'm sure there is something to help debug the API, but it is not something I know about. Some causes that I know of are the ones I included in my initial reply: 1. Items not having a home library and current library (both are required). 2. Item date fields that have 0000-00-00 - these need to be an actual date or NULL (MARC21 date fields are defined in 952, UNIMARC date fields are in 995). 3. Invalid entries for any of the item fields that use authorized values - the values need to match the authorized values lists. There are most likely others as well! Current tools to help some identify data issues =================================== 1. Check if bibliographic frameworks have any errors: Administration > Catalog > MARC Bibliographic framework test 2. Command line scripts to help identify any issues: - misc/maintenance/audit_database.pl - checks to see if there are any database structure issues (added in 23.11) - misc/maintenance/search_for_data_inconsistencies.pl - checks for some data inconsistencies (but doesn't fix them), including: . items that have undefined home libraries (homebranch) and holding library (holdingbranch) . authorities with undefined authority types (authtypecodes) . issues with item types (item type codes must match with what is defined in Administration > Basic parameters > Item types; also includes issues when the 'item-level_itypes' system preference is set to 'specific item') . invalid MARCXML in bibliographic records (this now shows on record details pages) . patrons with invalid category types for their age (not relevant to item data) . bibliographic records without a title . patron guarantee/guarantor issues 3. About Koha information in the staff interface - Server information, Perl modules, and System information tabs. There may be other tools available that can help. David Nind New Zealand
Hi, a little update. With Chrome web developer tools i get that the error seems to be this: detail.pl?biblionumber=4607:3207 Uncaught TypeError: Cannot read properties of undefined (reading 'str') at render (detail.pl?biblionumber=4607:3207:57) at datatables.min_24.0501000.js:41:12136 at e.fnGetData (datatables.min_24.0501000.js:41:15516) at S (datatables.min_24.0501000.js:41:18049) at St (datatables.min_24.0501000.js:41:20531) at y (datatables.min_24.0501000.js:41:22994) at It (datatables.min_24.0501000.js:41:28350) at datatables.min_24.0501000.js:41:26897 at Object.e [as success] (datatables.min_24.0501000.js:41:25877) at c (jquery-3.6.0.min_24.0501000.js:2:28327) Then I run search_for_data_inconsistencies.pl and I fixed some biblio with non title, a biblio without metadata. Now it runs clean but the "Processing..." box is still there. Then I run audit_database.pl and i get a long output (i attach the file) but it seems as if all the changes are already applied to koha_library database. Bibliographic frameworks seems to have an error. MARC bibliographic framework test returns: biblio and biblionumber - The biblio.biblionumber and biblioitems.biblioitemnumber fields be mapped to a MARC subfield, But biblio.biblionumber is 001 @ and biblioitems.biblioitemnumber is 090 a thanks tommaso Da: "David Nind" <david@davidnind.com> Per: spazzali@magritte.it Cc: koha@lists.katipo.co.nz Data: 21/07/2024 06.29 Oggetto: Re: [Koha] Rif: Re: Problem with 24.05.01 windows stalls with "processing" box Hi. I made the incorrect assumption about the MARC flavour you are using - it looks like you are using UNIMARC. For UNIMARC, the item data is in the 995 fields. As you have created a new record and added your normal item data, and you still get the same 500 error, then it sounds like something else is causing the issue. It may be useful to join https://chat.koha-community.org/ - the mailing list is really useful, but it isn't easy to share screenshots and other information. I've made some comments below, but welcome any other ideas and suggestions! It is also great that you have backups and can restore things to where you were before the upgrade! At the moment, I've run out of ideas! Holdings table change in the staff interface ================================ The change in 24.05 for the holdings table is intended to be a feature, not a bug. However, I think some guidance is required on how to troubleshoot what the issue is, and some solutions to help libraries fix any data or other issues. There could also be actual bugs that need fixing, or at least something to make it easier to identify what records and items have things that are incorrect. I've created Bug 37416 - Holdings table 500 errors in the staff interface - how to identify cause and possible solutions, so hopefully the developers and those more technical than me can help on there. Identifying the cause of the 500 error ============================ There may be multiple causes, so I welcome suggestions on how to identify what they are. For 500 errors, there is often more information in the server logs. So that is a place to start to help narrow it down. You could also use the web developer tools for your browser and check the console to see if there are any other errors there. I'm sure there is something to help debug the API, but it is not something I know about. Some causes that I know of are the ones I included in my initial reply: 1. Items not having a home library and current library (both are required). 2. Item date fields that have 0000-00-00 - these need to be an actual date or NULL (MARC21 date fields are defined in 952, UNIMARC date fields are in 995). 3. Invalid entries for any of the item fields that use authorized values - the values need to match the authorized values lists. There are most likely others as well! Current tools to help some identify data issues =================================== 1. Check if bibliographic frameworks have any errors: Administration > Catalog > MARC Bibliographic framework test 2. Command line scripts to help identify any issues: - misc/maintenance/audit_database.pl - checks to see if there are any database structure issues (added in 23.11) - misc/maintenance/search_for_data_inconsistencies.pl - checks for some data inconsistencies (but doesn't fix them), including: . items that have undefined home libraries (homebranch) and holding library (holdingbranch) . authorities with undefined authority types (authtypecodes) . issues with item types (item type codes must match with what is defined in Administration > Basic parameters > Item types; also includes issues when the 'item-level_itypes' system preference is set to 'specific item') . invalid MARCXML in bibliographic records (this now shows on record details pages) . patrons with invalid category types for their age (not relevant to item data) . bibliographic records without a title . patron guarantee/guarantor issues 3. About Koha information in the staff interface - Server information, Perl modules, and System information tabs. There may be other tools available that can help. David Nind New Zealand È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso. Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden.
Hello, It seems that something is missing in biblio with biblionumber 4607 that prevents it to be displaid with datatable. What says your koha logs ? S. Meynieux Le 21/07/2024 à 18:39, spazzali@magritte.it a écrit :
Hi,
a little update.
With Chrome web developer tools i get that the error seems to be this:
detail.pl?biblionumber=4607:3207 Uncaught TypeError: Cannot read properties of undefined (reading 'str') at render (detail.pl?biblionumber=4607:3207:57) at datatables.min_24.0501000.js:41:12136 at e.fnGetData (datatables.min_24.0501000.js:41:15516) at S (datatables.min_24.0501000.js:41:18049) at St (datatables.min_24.0501000.js:41:20531) at y (datatables.min_24.0501000.js:41:22994) at It (datatables.min_24.0501000.js:41:28350) at datatables.min_24.0501000.js:41:26897 at Object.e [as success] (datatables.min_24.0501000.js:41:25877) at c (jquery-3.6.0.min_24.0501000.js:2:28327)
Then I run search_for_data_inconsistencies.pl and I fixed some biblio with non title, a biblio without metadata.
Now it runs clean but the "Processing..." box is still there.
Then I run audit_database.pl
and i get a long output (i attach the file) but it seems as if all the changes are already applied to koha_library database.
Bibliographic frameworks seems to have an error. MARC bibliographic framework test returns: biblio and biblionumber - The biblio.biblionumber and biblioitems.biblioitemnumber fields be mapped to a MARC subfield,
But biblio.biblionumber is 001 @ and biblioitems.biblioitemnumber is 090 a
thanks
tommaso
Da: "David Nind" <david@davidnind.com> Per: spazzali@magritte.it Cc: koha@lists.katipo.co.nz Data: 21/07/2024 06.29 Oggetto: Re: [Koha] Rif: Re: Problem with 24.05.01 windows stalls with "processing" box
Hi.
I made the incorrect assumption about the MARC flavour you are using - it looks like you are using UNIMARC. For UNIMARC, the item data is in the 995 fields.
As you have created a new record and added your normal item data, and you still get the same 500 error, then it sounds like something else is causing the issue.
It may be useful to join https://chat.koha-community.org/ - the mailing list is really useful, but it isn't easy to share screenshots and other information.
I've made some comments below, but welcome any other ideas and suggestions!
It is also great that you have backups and can restore things to where you were before the upgrade!
At the moment, I've run out of ideas!
Holdings table change in the staff interface ================================
The change in 24.05 for the holdings table is intended to be a feature, not a bug.
However, I think some guidance is required on how to troubleshoot what the issue is, and some solutions to help libraries fix any data or other issues.
There could also be actual bugs that need fixing, or at least something to make it easier to identify what records and items have things that are incorrect.
I've created Bug 37416 - Holdings table 500 errors in the staff interface - how to identify cause and possible solutions, so hopefully the developers and those more technical than me can help on there.
Identifying the cause of the 500 error ============================
There may be multiple causes, so I welcome suggestions on how to identify what they are.
For 500 errors, there is often more information in the server logs. So that is a place to start to help narrow it down.
You could also use the web developer tools for your browser and check the console to see if there are any other errors there.
I'm sure there is something to help debug the API, but it is not something I know about.
Some causes that I know of are the ones I included in my initial reply: 1. Items not having a home library and current library (both are required). 2. Item date fields that have 0000-00-00 - these need to be an actual date or NULL (MARC21 date fields are defined in 952, UNIMARC date fields are in 995). 3. Invalid entries for any of the item fields that use authorized values - the values need to match the authorized values lists.
There are most likely others as well!
Current tools to help some identify data issues ===================================
1. Check if bibliographic frameworks have any errors: Administration > Catalog > MARC Bibliographic framework test 2. Command line scripts to help identify any issues: - misc/maintenance/audit_database.pl - checks to see if there are any database structure issues (added in 23.11) - misc/maintenance/search_for_data_inconsistencies.pl - checks for some data inconsistencies (but doesn't fix them), including: . items that have undefined home libraries (homebranch) and holding library (holdingbranch) . authorities with undefined authority types (authtypecodes) . issues with item types (item type codes must match with what is defined in Administration > Basic parameters > Item types; also includes issues when the 'item-level_itypes' system preference is set to 'specific item') . invalid MARCXML in bibliographic records (this now shows on record details pages) . patrons with invalid category types for their age (not relevant to item data) . bibliographic records without a title . patron guarantee/guarantor issues 3. About Koha information in the staff interface - Server information, Perl modules, and System information tabs.
There may be other tools available that can help.
David Nind New Zealand
È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso.
Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden.
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- Responsable support BibLibre +33 (0)4 91 81 35 08 https://www.biblibre.com
A related bug to look at is *Bug 37375* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37375> - Holdings table not loading if MARC framework is missing certain 952 subfields. While this relates to MARC21, something similar may be happening for the equivalent subfields in UNIMARC. It is also interesting to note that (for me) the developer tools in Firefox show the undefined property missing, but Chromium doesn't: - Firefox: Uncaught TypeError: can't access property "str", row._strings.collection_code is undefined - Chromium: Uncaught TypeError: Cannot read properties of undefined (reading 'str') David Nind New Zealand
this can be the case inspecting data I found some problems with items fields (995) in ous frameworks and I'm trying to fix them I'm waiting for translation web site to come back to install a new italian version. I will let you know thanks t.s. Da: "David Nind" <david@davidnind.com> Per: koha@lists.katipo.co.nz Data: 29/07/2024 02.04 Oggetto: Re: [Koha] Rif: Re: Rif: Re: Problem with 24.05.01 windows stalls with "processing" box Inviato da: "Koha" <koha-bounces@lists.katipo.co.nz> A related bug to look at is *Bug 37375* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37375> - Holdings table not loading if MARC framework is missing certain 952 subfields. While this relates to MARC21, something similar may be happening for the equivalent subfields in UNIMARC. It is also interesting to note that (for me) the developer tools in Firefox show the undefined property missing, but Chromium doesn't: - Firefox: Uncaught TypeError: can't access property "str", row._strings.collection_code is undefined - Chromium: Uncaught TypeError: Cannot read properties of undefined (reading 'str') David Nind New Zealand _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso. Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden.
Hi, I'm here again. As I wrote in a previous thead ( https://lists.katipo.co.nz/public/koha/2024-August/060888.html) I realized that I have a corrupt default MARC bibliographic framework I don't know why, I don't know since when. I didn't bothered because frameworks we currently use are almost correct. Now I need to add a items subtag (995.s in unimarc) that is missing and I need a correct default framework. (and I hope that this could help me to fix the previous thread i mentioned before) I managed to export a csv file for a correct default framework from a temporary new installation. But when I try to import the .csv over the default tag (and subtag) structure apparently nothing happens. Looking into the database (tables "marc_tag_structure" and "marc_subfield_strucure") I see that there are a number of records with the field frameworkcode valorized as "defa" that apparently contain the correct default structure I intended to import. Now I wonder what can happen if I sobstitute records with empty frameworkcode with those with "defa" as frameworkcode (i.e. cut records with empty frameworkcode and empty frameworkcode field where it is equal to "defa"). Or maybe somebody has an idea on how reset the default MARC bibliographic framework In any case thanks a lot tommaso È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso. Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden.
Maybe https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37606 for wrong import after export of a framework ? Best regards S. Meynieux Le 16/08/2024 à 14:05, spazzali@magritte.it a écrit :
Hi,
I'm here again.
As I wrote in a previous thead ( https://lists.katipo.co.nz/public/koha/2024-August/060888.html) I realized that I have a corrupt default MARC bibliographic framework I don't know why, I don't know since when.
I didn't bothered because frameworks we currently use are almost correct.
Now I need to add a items subtag (995.s in unimarc) that is missing and I need a correct default framework. (and I hope that this could help me to fix the previous thread i mentioned before)
I managed to export a csv file for a correct default framework from a temporary new installation.
But when I try to import the .csv over the default tag (and subtag) structure apparently nothing happens.
Looking into the database (tables "marc_tag_structure" and "marc_subfield_strucure") I see that there are a number of records with the field frameworkcode valorized as "defa" that apparently contain the correct default structure I intended to import.
Now I wonder what can happen if I sobstitute records with empty frameworkcode with those with "defa" as frameworkcode (i.e. cut records with empty frameworkcode and empty frameworkcode field where it is equal to "defa").
Or maybe somebody has an idea on how reset the default MARC bibliographic framework
In any case thanks a lot
tommaso
È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso.
Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden.
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- Responsable support BibLibre +33 (0)4 91 81 35 08 https://www.biblibre.com
Hi David, hi everybody, I fixed my db. The misconfigurazion was in the bibliographic frameworks we were using I particular I had to set the authorizad table "LOC" for subtag 995,e [Unimarc] and connect 995,y to Koha field items.datelastseen (that weren't) I realized that DataTable is also sensible to the visibility of item fields. Thanks a lot, without your suggestions I would never have done this t Da: spazzali@magritte.it Per: koha@lists.katipo.co.nz Data: 06/08/2024 12.15 Oggetto: [Koha] Rif: Re: Rif: Re: Rif: Re: Problem with 24.05.01 windows stalls with "processing" box Inviato da: "Koha" <koha-bounces@lists.katipo.co.nz> this can be the case inspecting data I found some problems with items fields (995) in ous frameworks and I'm trying to fix them I'm waiting for translation web site to come back to install a new italian version. I will let you know thanks t.s. Da: "David Nind" <david@davidnind.com> Per: koha@lists.katipo.co.nz Data: 29/07/2024 02.04 Oggetto: Re: [Koha] Rif: Re: Rif: Re: Problem with 24.05.01 windows stalls with "processing" box Inviato da: "Koha" <koha-bounces@lists.katipo.co.nz> A related bug to look at is *Bug 37375* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37375> - Holdings table not loading if MARC framework is missing certain 952 subfields. While this relates to MARC21, something similar may be happening for the equivalent subfields in UNIMARC. It is also interesting to note that (for me) the developer tools in Firefox show the undefined property missing, but Chromium doesn't: - Firefox: Uncaught TypeError: can't access property "str", row._strings.collection_code is undefined - Chromium: Uncaught TypeError: Cannot read properties of undefined (reading 'str') David Nind New Zealand _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso. Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha È strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso. Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden.
participants (3)
-
David Nind -
Sophie MEYNIEUX -
spazzali＠magritte.it