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" <[email protected]>
Per: [email protected]
Cc: [email protected]
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.
Parsing schema for file './installer/data/mysql/kohastructure.sql'
Parsing schema for database 'koha_library'
-- Convert schema '' to '':;
BEGIN;
ALTER TABLE account_debit_types CHANGE COLUMN can_be_sold can_be_sold
tinyint(1) NOT NULL DEFAULT 0 comment 'boolean flag to denote if this debit
type is available at point of sale';
ALTER TABLE account_offsets DROP INDEX account_offsets_ibfk_t;
ALTER TABLE accountlines DROP INDEX accountlines_ibfk_branches,
DROP INDEX accountlines_ibfk_borrowers_2,
DROP INDEX accountlines_ibfk_debit_type,
DROP INDEX accountlines_ibfk_credit_type,
ADD INDEX credit_type_code (credit_type_code),
ADD INDEX debit_type_code (debit_type_code),
ADD INDEX branchcode (branchcode),
ADD INDEX manager_id (manager_id);
ALTER TABLE additional_contents DROP FOREIGN KEY
additional_contents_borrowernumber_fk,
ADD CONSTRAINT borrowernumber_fk FOREIGN KEY
(borrowernumber) REFERENCES borrowers (borrowernumber) ON DELETE SET NULL ON
UPDATE CASCADE;
ALTER TABLE authorised_value_categories CHANGE COLUMN category_name
category_name varchar(32) NOT NULL DEFAULT '';
ALTER TABLE biblio_metadata DROP FOREIGN KEY biblio_metadata_fk_1,
CHANGE COLUMN schema schema varchar(16) NOT NULL,
ADD CONSTRAINT record_metadata_fk_1 FOREIGN KEY
(biblionumber) REFERENCES biblio (biblionumber) ON DELETE CASCADE ON UPDATE
CASCADE;
ALTER TABLE categories CHANGE COLUMN password_expiry_days password_expiry_days
smallint(6) NULL DEFAULT NULL comment 'number of days after which the patron
must reset their password';
ALTER TABLE class_sources ADD INDEX class_source_ibfk_2 (class_split_rule),
ADD CONSTRAINT class_source_ibfk_2 FOREIGN KEY
(class_split_rule) REFERENCES class_split_rules (class_split_rule);
ALTER TABLE creator_layouts CHANGE COLUMN scale_width scale_width decimal(28,
6) NOT NULL DEFAULT 0.800000,
CHANGE COLUMN scale_height scale_height decimal(28,
6) NOT NULL DEFAULT 0.010000;
ALTER TABLE deletedbiblio_metadata DROP FOREIGN KEY deletedbiblio_metadata_fk_1,
CHANGE COLUMN schema schema varchar(16) NOT
NULL,
ADD CONSTRAINT deletedrecord_metadata_fk_1
FOREIGN KEY (biblionumber) REFERENCES deletedbiblio (biblionumber) ON DELETE
CASCADE ON UPDATE CASCADE;
ALTER TABLE erm_counter_files CHANGE COLUMN date_uploaded date_uploaded
timestamp NULL DEFAULT CURRENT_TIMESTAMP comment 'counter file upload date';
ALTER TABLE erm_counter_logs CHANGE COLUMN importdate importdate timestamp NULL
DEFAULT CURRENT_TIMESTAMP comment 'counter file import date';
ALTER TABLE erm_eholdings_packages DROP FOREIGN KEY erm_packages_ibfk_1,
DROP INDEX erm_packages_ibfk_1,
ADD INDEX erm_eholdings_packages_ibfk_1
(vendor_id),
ADD CONSTRAINT erm_eholdings_packages_ibfk_1
FOREIGN KEY (vendor_id) REFERENCES aqbooksellers (id) ON DELETE SET NULL ON
UPDATE CASCADE;
ALTER TABLE illrequests DROP CONSTRAINT illrequest_id;
ALTER TABLE import_record_matches CHANGE COLUMN chosen chosen tinyint(1) NULL
DEFAULT NULL comment 'whether this match has been allowed or denied';
ALTER TABLE language_descriptions DROP INDEX subtag_type_lang;
ALTER TABLE library_groups DROP INDEX parent_id;
ALTER TABLE library_hours DROP FOREIGN KEY library_hours,
ADD CONSTRAINT library_hours_ibfk_1 FOREIGN KEY
(library_id) REFERENCES branches (branchcode) ON DELETE CASCADE ON UPDATE
CASCADE;
ALTER TABLE marc_modification_template_actions CHANGE COLUMN action action
enum('delete_field', 'add_field', 'update_field', 'move_field', 'copy_field',
'copy_and_replace_field') NOT NULL;
ALTER TABLE message_transports DROP INDEX message_transports_ibfk_3;
ALTER TABLE messages DROP INDEX manager_id,
ADD INDEX messages_ibfk_1 (manager_id);
ALTER TABLE old_reserves DROP INDEX old_desk_id;
ALTER TABLE patron_consent CHANGE COLUMN type type tinytext NULL DEFAULT NULL
comment 'consent type, could be custom type',
ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE
utf8mb4_unicode_ci;
ALTER TABLE patron_lists CHANGE COLUMN name name varchar(255) character set
utf8mb4 collate utf8mb4_general_ci NOT NULL comment 'the list''s name';
ALTER TABLE recalls DROP INDEX borrowernumber,
DROP INDEX biblionumber,
DROP INDEX itemnumber,
DROP INDEX branchcode,
ADD INDEX recalls_ibfk_1 (patron_id),
ADD INDEX recalls_ibfk_2 (biblio_id),
ADD INDEX recalls_ibfk_3 (item_id),
ADD INDEX recalls_ibfk_4 (pickup_library_id);
ALTER TABLE repeatable_holidays CHANGE COLUMN branchcode branchcode varchar(10)
NOT NULL comment 'foreign key from the branches table, defines which branch
this closing is for';
ALTER TABLE search_field CHANGE COLUMN type type enum('', 'string', 'date',
'number', 'boolean', 'sum', 'isbn', 'stdno', 'year', 'callnumber', 'geo_point')
NOT NULL comment 'what type of data this holds, relevant when storing it in the
search engine';
ALTER TABLE special_holidays CHANGE COLUMN branchcode branchcode varchar(10)
NOT NULL comment 'foreign key from the branches table, defines which branch
this closing is for';
ALTER TABLE subscription DROP INDEX by_biblionumber,
ADD INDEX subscription_ibfk_3 (biblionumber);
ALTER TABLE subscriptionhistory DROP INDEX biblionumber,
ADD INDEX subscription_history_ibfk_1
(biblionumber);
ALTER TABLE suggestions DROP INDEX suggestions_budget_id_fk,
DROP INDEX suggestions_ibfk_acceptedby,
DROP INDEX suggestions_ibfk_rejectedby,
ADD INDEX acceptedby (acceptedby),
ADD INDEX rejectedby (rejectedby),
ADD INDEX budgetid (budgetid);
ALTER TABLE ticket_updates DROP FOREIGN KEY ticket_updates_ibfk_4,
DROP INDEX ticket_updates_ibfk_4,
ADD INDEX ticket_updates_ibfk_3 (assignee_id),
ADD CONSTRAINT ticket_updates_ibfk_3 FOREIGN KEY
(assignee_id) REFERENCES borrowers (borrowernumber) ON DELETE CASCADE ON UPDATE
CASCADE;
COMMIT;
WARNING!!!
These commands are only suggestions! They are not a replacement for
updatedatabase.pl!
Review the database, updatedatabase.pl, and kohastructure.sql before making any
changes!
_______________________________________________
Koha mailing list http://koha-community.org
[email protected]
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
