-
Notifications
You must be signed in to change notification settings - Fork 0
Uutta versiossa 26.xx
Tiedot poimittu yhteisön Release noteseista
https://koha-community.org/koha-26-05-00-released/ https://koha-community.org/koha-25-11-00-is-here/
41135 Convert about page Perl module table to DataTable
This enhancement updates the Perl modules about page to use the standard data table format – this allows for sorting, filtering by required or missing, and searching (More > About Koha > Perl modules).
41319 Link content of ‘Contributing companies and institutions’ to bug sponsors
This enhancement automates the generation of contributing companies and institutions on the about page (About Koha > Koha team), and (where known): – Links to their website – Includes the country
38262 Add additional fields to vendors
This enhancement lets you add and use additional fields for vendors (Administration > Additional parameters > Additional fields > Acquisitions > Vendors)
40383 Modernise the EDIFACT Message display modal
The EDIFACT message viewer has been significantly improved with a new interactive modal interface replacing the previous basic display.
New features:
- Tree view — Collapsible, hierarchical display of EDIFACT interchange structure with segment tagging
- Raw view — Plain-text fallback for direct inspection of message content
- Search — Real-time search with regex support, result count, and previous/next navigation
- Focus mode — Highlights segments relevant to the current context (basket or invoice) when opened from those pages
- JSON download — New ?format=json endpoint on edimsg.pl and download button for programmatic access and debugging; backed by a new to_json() method on Koha::Edifact
7132 Check for duplicates when creating a new record in acquisitions
Acquisitions: duplicate check when ordering from an empty record
When creating a new order via Acquisitions → New order (empty record), Koha now checks for existing bibliographic duplicates (using C4::Search::FindDuplicate). If a potential match is found, staff see the standard Duplicate warning screen with options to Use existing record, Create new anyway, or Cancel and return to the basket.
This aligns the empty-record workflow with the existing duplicate checks used for external source imports and cataloging, reducing accidental duplicate bibs in the catalog.
40942 Vendor’s contacts not displayed nicely on the vendor detail view
20638 Add audit logging for API key actions
42003 Upgrade DataTables from 2.3.4 to 2.3.7 (and FixedHeader to 4.0.6)
This enhancement upgrades the DataTables JavaScript library from version 2.3.4 to 2.3.7.
This brings in upstream fixes and improvements released since 2.3.4, especially version 4.0.6 of the FixedHeader plugin, which fixes a scrolling glitch with sticky headers.
35761 Add an administration editor for FTP and SFTP servers
Koha now includes a unified administration interface for managing FTP and SFTP server connections, eliminating the need to duplicate connection details across different parts of the system.This new centralised configuration system allows you to define FTP and SFTP server credentials once and then reference them from multiple features (such as EDI). If a password changes or a vendor upgrades from FTP to SFTP, only a single configuration record needs updating.Key features:
- Unified server management: Configure FTP and SFTP servers under Administration → File transports
- Secure credential storage: Passwords and SSH keys are encrypted in the database
- Connection testing: Test connections directly from the Koha interface to verify credentials and connectivity
- Granular permissions: New manage_file_transports permission controls access to the configuration interface
- Reusable configurations: Server configurations can be referenced by multiple features, reducing duplication
Configuration options:
- Transport type (FTP or SFTP)
- Server hostname and port
- Username and password
- Upload and download directories
- Connection settings (passive mode, debug mode)
- SSH private key (for SFTP)
For administrators:
Access the new file transport management under Administration → File transports. The interface includes a connection testing feature that validates your credentials and checks read/write permissions on the configured directories.
Future extensibility:
This architecture provides a foundation for adding file transport capabilities to other Koha features such as runreport.pl, export_records.pl, and export_borrowers.pl, allowing them to upload outputs directly to remote servers.
36674 Lazy load api-client JS files
38201 VueJS architecture rethink
The idea behind this bug was to introduce a framework for building Vue applications and components that would allow a developer to make use of pre-existing components and logic, rather than having to write everything from scratch. Currently in Koha, we have a lot of bespoke logic for each different form/display page as well as a lot of repeated code. This can make regressions more likely and reduce code consistency. To address this, we have introduced standardised components for rendering form elements (e.g. inputs, selects) and displaying data, as well as a standardised ‘list’ component. This means that each new Vue module can be built very quickly without the need to write out all the HTML structure and logic for creating a form/display page – the developer can simply access the pre-written logic in the framework to do the heavy lifting for them.The FormElement and ShowElement components are at the core of this work, as they render the different input and display options in a standardised manner. These are made use of by ResourceFormSave, ResourceShow and ResourceList which act as generic components that can be used by the developer to handle any Koha data type. To prove this, all the existing Vue modules (ERM, Preservation, Record Resources and Vendors) have been migrated to use it. A new suite of cypress tests has been written to verify the functionality as well as catch regressions and part of this is introducing component testing into Koha for any future Vue work that may need it.Moving forwards, the aim would be that new modules are built using this framework. It is important to note that the framework is not restrictive – it is possible to inject bespoke components directly into FormElement and ShowElement where there are particularly niche requirements. However, the goal is that if the developer feels that there could be a need for that requirement in future for someone else, then the goal should be to expand the framework to support it so that all can benefit. We have documented this through the use of JSDoc in base-resource.js, as well as with an example SkeletonResource.vue to show how it should be used. There are also the live examples in the modules mentioned above.
30724 Add ability for administrator to reset a users 2FA
This enhancement enables superlibrarians to turn off two-factor authentication (2FA) for a staff patron when they lose access to their authenticator application or device. This is accessed from the patron’s account > More > Manage two-factor authentication.
17387 Add an undelete feature for items/biblios
When a bibliographic record or item is deleted in Koha, the data is moved to the deletedbiblio, deletedbiblioitems, and deleteditems tables rather than being permanently removed. This new feature exposes those tables through a dedicated staff interface and REST API, enabling authorised users to restore that data back into the active catalogue.
New Features
A Restore Deleted Records page is accessible from the Cataloguing module home page, presenting two tables: one for deleted bibliographic records and one for deleted items. Each table displays key identifying information such as biblio ID, title, barcode, and the date the record was deleted. A date range filter in the sidebar allows staff to narrow results by deletion date. Restoring a deleted item whose parent bibliographic record is also deleted will present a warning modal, prompting the user to restore the bibliographic record first. Restoring a deleted bibliographic record opens a modal listing any associated deleted items, with checkboxes allowing the user to select which items (if any) to restore alongside the bibliographic record. Restored records are automatically re-indexed in the search engine (Zebra / Elasticsearch) upon restoration. Restore actions are written to the action log (RESTORE action for both biblios and items), providing an audit trail. Library group membership is taken into account during permission checks, so staff are only able to restore records within their permitted scope.
New REST API Endpoints
New endpoints have been added to the Koha REST API to support programmatic restoration of deleted records:
- POST /api/v1/deleteditems/{item_id}/restore — restore a single deleted item
- POST /api/v1/deletedbiblios/{biblio_id}/restore — restore a single deleted bibliographic record
- GET /api/v1/deleteditems — list deleted items (supports embedding associated biblio data and pagination headers)
- GET /api/v1/deletedbiblios — list deleted bibliographic records (supports embedding associated deleted items)
New Permission
A new restore_deleted_records permission has been added as a child of the Cataloguing permissions group. Users must be granted this permission to access the Restore Deleted Records page and to use the restore API endpoints.
Important Notes
Restoration is only possible for records still present in the deleted records tables. Data in related tables (e.g. link tracker, holds history) that was cascade-deleted when the record was removed cannot be recovered by this tool. A restored record will be re-inserted with its original biblio/item ID where possible.
This feature does not constitute a full “soft delete” or undo system — it is a targeted recovery tool for data held in Koha’s existing deleted-record tables.
32773 Have the ability to have more than 1 Fast Add framework
This enhancement adds the ability for libraries to use multiple bibliographic frameworks for Fast add.
Administrators with the manage_marc_frameworks permission can now enable MARC bibliographic frameworks to be used as Fast add frameworks.
Library staff with the fast_cataloging permission will be able to create and edit Fast add enabled bibliographic records. They will be able to create items for Fast add enabled records and edit the attached items if allowed by library or library group.
A Fast add badge will be displayed in the details of Fast add enabled bibliographic records.
39418 Add authorized value lists for MARC21 RDA Carrier, Content, and Media Vocabularies
This enhancement adds authorized value lists for use in MARC21 tags 336 – Content Type, 337 – Media Type, and 338 – Carrier Type, subfields $a and $b. Note: Manual updates are required to your frameworks to link the subfields to the authorized value lists.
The six new authorized value lists:
- RDACARRIER
- RDACARRIER_CODE
- RDACONTENT
- RDACONTENT_CODE
- RDAMEDIA
- RDAMEDIA_CODE
40031 Creation of a new MARC modification template should redirect to have the template ID in the URL
This updates the URL when adding a new MARC modification template (Cataloging > Batch editing > MARC modification templates). It adds the template ID to the URL so that you can directly link to the template.
Previously, you had to click Edit actions from the list of templates, and couldn’t directly link to the template to see the actions:
- Previous URL after adding a template: STAFF-INTERFACE-URL/cgi-bin/koha/tools/marc_modification_templates.pl
- New URL after adding a template: STAFF-INTERFACE-URL/cgi-bin/koha/tools/marc_modification_templates.pl?template_id=(template_id)&op=select_template
40154 Deleting an item does not warn about an item level hold
Sponsored by Koha-Suomi Oy
40584 When AutoControlNumber is activated, do not show 001 in Advanced Editor
40633 Add keyboard shortcut to advanced cataloging editor for fixed length field plugins
This enhancement adds a keyboard shortcut to the advanced cataloging editor to open the value builder plugins for the MARC leader, 006, 007, and 008 fields. This shortcut defaults to Control-Shift-H but can be customized as desired.
40841 Limit z39.50 targets to specific libraries
This enhancement adds the option to limit the Z3950/SRU targets to specific libraries.
Within larger systems, catalogers at individual library may have different z39.50 targets that they prefer to use or are allowed access to.
41060 Add a value_builder to check if ISSN is valid
This enhancement adds a new cataloging plugin (value builder) for validating ISSNs. If you enter an invalid ISSN, a browser pop-up window warns that the ISSN is invalid, but you can ignore this (the field is highlighted in yellow) and still save the record.For new installations, the validate_issn.pl plugin is added to the bibliographic frameworks by default for 022$a (MARC21) or 011$a (UNIMARC).For existing installations, update your frameworks manually.
41170 Highlight previously edited item on add items page
This patch adds highlighting of the most recently edited/added item on the ‘add items page’. The feature allows catalogers to identify recent item and confirm their edits or compare to other items in the catalog.
41902 Allow configuration of bibliographic information to be shown on new record duplicate check
This enhancement adds a way to display more bibliographic information when Koha suspects a newly-created bibliographic record may be a duplicate of an existing record. This is done through “Tools” > “Additional content” > “Record display customizations”, using the new display location of StaffDuplicateCheckPage. Information to be displayed is defined in TemplateToolkit and styled with HTML. Available data includes the contents of the biblio table and the full MARC record.
29980 Validate ISBN when cataloguing bibliographic records
This enhancement adds a new cataloging plugin (value builder) for validating ISBNs. If you enter an invalid ISBN, a browser pop-up window warns that the ISBN is invalid, but you can ignore this (the field is highlighted in yellow) and still save the record.
For new installations, the validate_isbn.pl plugin is added to the bibliographic frameworks by default for 020$a (MARC21) or 010$a (UNIMARC).
For existing installations, update your frameworks manually.
7376 Transfer limits should be checked at check-in
This patch introduces new controls to prevent a check-in at a library where transfer rules would forbid the item transfer back to this item’s home/issuing library.
For items set to ‘float’ transfer rules are not set as the check-in would not trigger a transfer.
16131 Error messages for library transfers show with bullet points
When transferring items (Circulation > Transfers > Transfer), any error messages are shown as a bulleted list in one alert box.
If there is only one error, it looks a bit odd having a bulleted list with only one item.
With this enhancement, each error message is now shown in its own alert box.
23415 Notify patron fines when renewing
It was possible to renew items for patrons who had fines over the accepted limit on the renew item page or from their list of checkouts.
This enhancement adds a new system preference, AllowFineOverrideRenewing, to allow staff to renew items for patrons with fines greater than value in FineNoRenewal (previously OPACFineNoRenewals).
New features
New system preference AllowFineOverrideRenewing. It allows staff to renew items for patrons whose fines are over the amount set in the FineNoRenewals system preference. Otherwise, renewing is prevented. If renewing items is allowed, staff are still required to confirm if they really want to renew items for the patron.
Changes made to system preferences and API endpoints
- These system preferences were renamed as they are now also used in the staff interface (not just the OPAC):
- OPACFineNoRenewals was renamed FineNoRenewal.
- OPACFineNoRenewalsIncludeCredits was renamed FineNoRenewalsIncludeCredits.
- OPACFineNoRenewalsBlockAutoRenew was renamed FineNoRenewalsBlockAutoRenew.
- Adds support to the REST API renewal endpoints for the AllowFineOverrideRenewing functionality.
Important notes
- There were several places in the code where the auto-renewal error code was written as “auto_too_much_oweing” instead of “auto_too_much_owing”.
- The same typo was also present in example notices templates, and possibly in notice templates saved in the database.
- The typo is automatically fixed with a database update.
Sponsored by Koha-Suomi Oy and OpenFifth
26993 Allow StoreLastBorrower to retain a locally-defined number of previous borrowers
This enhancement expands the StoreLastBorrower system preference to allow for the retention of a locally defined number of previous borrowers for a given item. This enhancement also introduces a mechanism that will delete any extra borrowers stored in the items_last_borrower table that exceed the number set in the StoreLastBorrower system preference.
28530 Allow configuration of floating limits by item type
This enhancement adds the ability to define and enforce a maximum number of items per item type to be held at each library when items are allowed to float. This feature is enabled with the UseLibraryFloatLimits system preference. Float limits are defined within Administration. Items checked in at a library that has met its float limit for that item type will be transferred to the branch with the lowest ratio of held items to allowed items.
32682 Add permission for viewing patron reading history
This enhancement adds a new permission for viewing parton’s reading history. ( view_checkout_history )
Now when intranetreadinghistory is enabled staff must also have the specific ‘view_checkout_history’ permission in order to view a patron’s reading history. With intranetreadinghistory turned off the no users are able to view patron’s reading history.32682 Add permission for viewing patron reading history
This enhancement adds a new permission for viewing parton’s reading history. ( view_checkout_history ) Now when intranetreadinghistory is enabled staff must also have the specific ‘view_checkout_history’ permission in order to view a patron’s reading history. With intranetreadinghistory turned off the no users are able to view patron’s reading history.
40364 Add permission for viewing patron holds history
This enhancement adds a new permission for viewing parton’s hold history. ( view_holds_history )
Now when IntranetReadingHistoryHolds is enabled staff must also have the specific ‘view_holds_history’ permission in order to view a patron’s hold history. With IntranetReadingHistoryHolds turned off the no users are able to view patron’s hold history.
37966 When overriding a hold to renew a book the due date becomes “now” if not specified
39802 Add CircControl equivalent system preference for lost item fees and actions
This enhancement adds a new system preference: LostChargesControl which is used to determine the branch that is used to look up the circulation rule for charging lost fees when an item is marked lost.
Choices are:
- library the item is from (follows HomeOrHolding)
- library the patron is from
- library you are logged in at
Currently this is only used by the longoverdue cronjob. Selecting “library you are logged in at” will cause the cronjob to cancel as there is no branch – this mimics current behavior, but is more verbose.
41134 Add table settings to transfers
This enhancement adds standard table settings to the transfers table (Circulation > Transfers > Transfer). This includes options to change the columns shown, export data, and to configure the default table settings.
41338 Hold found dialog does not show item home and check-in libraries
41539 Include item barcode in waiting hold message on patron record
This enhancement adds the item barcode to the holds waiting information on a patron’s check out and details page.
This makes it easier for circulation staff to copy the barcode to check the item out when a patron picks it up (where this is the library workflow and a self-service option is not available.
Before: Title (Item type), Author. Hold place on DD-MM-YY After: Title (Item type), Author. (Barcode) Hold place on DD-MM-YY
23260 Anonymize (remove) patron data from items_last_borrower
This enhancement allows the automatic deletion of data from the items_last_borrower table. This data is generated based on the StoreLastBorrower system preference. Deletion of this data performed by the new cronjob anonymize_last_borrowers.pl, with its behavior governed by the new system preferences AnonymizeLastBorrower and AnonymizeLastBorrowerDays. When the cronjob is run, entries in items_last_borrower are anonymized if older than the number of days defined in AnonymizeLastBorrowerDays.
35612 Record branch context in accountlines.branchcode for OVERDUE, LOST, and PROCESSING fees
This enhancement allows the optional recording of the branch used when generating an accountline.
For OVERDUE fees, the branch chosen by CircControl will be reflected here. For LOST and PROCESSING fees, the branch chosen by LostChargesControl will be reflected here.
This development will allow librarians to reference charges against the circ rules to determine which branches rule was applied when creating a fine.
Tätä vastaava on jo meillä, voiko tiputtaa omaa koodia?
40255 Allow custom debit descriptions
This patchset allows for the ability to set custom debit descriptions via Notices and Slips by adding a new module called “Debit description (custom)” to notices/slips.. By using a Debit description (custom) notice/slip with the same name as a debit type, a custom debit description will be used instead of the default.
40435 Allow CanBookBeRenewed to consider future holds
Historically, renewals are not blocked for future holds (which are only possible when enabled). This report adds a new preference FutureHoldsBlockRenewals to override that behavior. If you enable it, renewals are blocked by future holds when they are not further away than the threshhold used for Holds to Pull in preference ConfirmFutureHolds.
41957 Hyperhold/hold group information should show on ‘Hold found’ modal
This enhancement adds a notification to the hold found modal when the hold to be filled is part of a group. The modal will include the message “part of a hold group” and a link to the holds table in the patron’s account.
41983 Holds queue should show when holds are part of a group
This adds “(part of a hold group)” to the holds queue (under the title in the title column), when hold groups are enabled (DisplayAddHoldGroups system preference).
37762 Expand ILL to allow for supplying agency/lending library workflows
40504 ILL requests should have ability to assign staff to manage
This enhancement adds a “Managed by” feature for Interlibrary Loan (ILL) requests, mirroring existing functionality in purchase suggestions. This is particularly beneficial for large consortia managing high volumes of requests.
41009 When editing an ILL request, the user is returned to the list
This enhancement will return a user to the ill request page instead of the list of requests after saving an edit.
41536 ILL “Confirm Request” button fails to stand out as a primary action
42267 Update lists pages to use grid layout for forms
38096 Field 857 is not considered for display on XSLT files
41000 Update label on record detail pages for 041$d – “Spoken language” to “Sung or spoken language”
This enhancement updates the label on detail pages in the staff interface and OPAC for records with a 041$d (MARC21) – Language code of sung or spoken text.
It is now labelled as “Sung or spoken language”, instead of “Spoken language” –better matching the MARC21 definition.
For music libraries, this also more accurately reflects the information for the record.
35267 Clarify CSS options for Notices
Clarify existing and add new CSS options for Notice Templates.
21555 Merging Patrons allows for all patrons to be selected
30303 Add ability to select which values to retain when merging patrons
This enhancement provides greater control over data preservation and streamlines the process of managing duplicate patron records.
When merging two patron records, users can now selectively copy fields to retain from the record being deleted (source) into the record being kept (destination).
40794 Add an id to the div containing payments tabs
An id=”account-tabs” attribute has been added to the account/payment tab navigation (Transactions, Make a payment, Create manual invoice, Create manual credit). This allows for easier customization and targeting with CSS/JS without conflicting with the global toptabs navigation.
41954 Staff interface: Patron hold history table should show hyperhold/hold group information
28701 primary_contact_method not part of the REST API spec
29668 Add API route to create a basket
41107 Create an API endpoint to get Koha version
This enhancement adds a new REST API endpoint to retrieve Koha version information. The returned version object includes the full version string (e.g., ‘25.06.00.029’) as well as its constituent parts: major version number, minor version number, release number, maintenance version number, and development version number (if applicable). This prepares the foundation for a future /status endpoint that will include all information displayed in the About page.
41994 REST API route to list system preferences
42206 Add REST endpoint GET /libraries/{library_id}/closed_dates
39043 Style improvement to guided reports controls
39164 Add max_statement_time to SQL report queries
This patchset adds the abilty to set a maximum execution time in seconds for SQL report queries. Reports exceeding this limit will be automatically terminated. This is configured in the koha-conf.xml file by setting the report_sql_max_statement_time_seconds parameter. By default this is turned off.
40896 Run report button should be disabled after click
The “Run report” buttons in the guided reports interface are now disabled upon click and display a spinner icon, preventing accidental duplicate submissions that could overload the system. This improvement uses a new reusable throttled button component that automatically re-enables after a configurable timeout and correctly handles browser back-forward cache navigation. The component wraps icons in semantic containers for accessibility (aria-busy) and is designed to be reused across other parts of the staff interface.
41918 Prevent users from running the same report multiple times concurrently
41919 Limit number of current reports a single user can run simultaneously
42190 Add datatables to reports
This enhancement allows report results to be viewed with the DataTables feature used elsewhere in Koha. DataTables allows sorting by any column in the results as well as dynamic filtering. Export options within the DataTables view include a new Copy option and export data respecting the user’s current sorting and filtering.
42406 Create permission to allow user to delete only their own reports
41311 Add ability for SIP to send patron home library ( branchcode ) in AO field
41383 SIP2 server does not search patrons by unique patron attributes (alternate IDs unusable in SIP2)
36920 Greater/less than search option on item search page to Barcode-drop-down menu
This enhancement adds greater than and less than search options on item search page field drop-down menu. With them staff can search e.g. items which have release year starting from specific year.
Meillä on tähän oma toteutus - tiputettavissa?
21820 Zebraqueue should not be added to when only Elasticsearch is used
We added a new syspref “ElasticsearchEnableZebraQueue”. If disabled, no data will be written to the zebraqueue table, because usually when using Elasicsearch you don’t need to also run Zebra.
But if your workflows require changed biblio/auths to show up in the zebraqueue table, set the syspref to “enable”. When upgrading, the old behavior will be kept, i.e. the syspref is set to “enable”. New installations will default to “disable”.
22639 Ability to export Elasticsearch mappings and facets settings
This enhancement adds an ‘Export mappings’ button to the Elasticsearch mappings configuration page to download the current search field mappings as YAML.
36550 koha-elasticsearch commit default should be configurable
You can now set custom defaults for koha-elasticsearch in /etc/default/koha-common. You can still override the defaults using the command line.
36849 Add more tags to Elasticsearch mapping for title, title as phrase
This enhancement adds these fields to the ‘title’ index for new installations using Elasticsearch: 440$a, 600$t, 800$t, 810$t, 830$n$p. This makes records with information in these fields findable in the staff interface and OPAC, and in the advanced search, when using the ‘Title’ and ‘Title as phrase’ options.
Note: Existing installations will need to either manually add these, or reset the mappings.
36853 Enhance Elasticsearch Notes/Comments MARC21 index mappings
This enhancement adds these note subfields to the Notes/Comments index for new installations using Elasticsearch: 501$a, 503$a, 504$a, 508$a, 511$a, 521$a, 538$a, and 547$a. This makes them notes findable in the staff interface and OPAC, and in the advanced search for when the Notes/Comments option is selected.
Note: Existing installations will need to either manually add these, or reset the mappings.
37099 Add uniform title fields to the title and subject Elasticsearch index mappings
This enhancement adds the 630$a field to the ‘subject (Topics)’ search field index for new installations using Elasticsearch.
Note: Existing installations will need to either manually add the mapping, or reset their mappings.
40577 Bulk update Elasticsearch index for bibliographic records after authority change
When merging (or updating) authorities, the Elasticsearch indexing of the linked biblios now will happen in one background job per authority instead of one background job per biblio. So an authority that is used in 100 biblios will now trigger one indexing background job with 100 biblio items instead of 100 background jobs with 1 biblio item each.
42107 Add score to staff search results
38009 Add a generate next button in serials receive page
This enhancement adds a “Generate next” button to the receive page for a serial, similar to the one on the serial collection page (Serials > [subscription page] > Receive).
38061 Serials collection table improvements
This introduces for each new and existing subscription a field named “Pre-select issues in the collections table”
24949 Provide password visibility toggle / icon to unmask password on staff login screen
35211 Make it possible to split holdings tab using library groups in intranet
This enhancement adds a new system preference SeparateHoldingsByGroup. When this preference is enabled and the logged-in library is part of a library group marked Use for staff search groups, the holdings table will include a tab listing all items with a homebranch within that group. When SeparateHoldings is also enabled, the Other holdings tab will only include items not owned by either the logged-in library or a library sharing a group with the logged-in library.
36698 Display ‘diff’ nicely in action logs
This enhancement adds styling to the diff column in the action logs to make it more human readable.
38946 Add serial enumeration to inventory table
This change adds a “Serial enumeration / chronology” column into the inventory results. This is particularly useful when doing inventory/stocktake with serials which share the same call number but have different volume numbers. This new column can be hidden by clicking “Columns” and hiding it or going into table settings.
39142 Add debug permission to allow user to toggle JS and CSS customizations on/off
This fix adds GUI controls to disable custom CSS and JS on the page. It also includes a system preference, user flag, to control managing this along with updates to permissions for being able to do this. This works alongside the pre-existing url parameters to disable custom css and JS in the page.
Tämä on tuotu meille jo versioon 25.05.
40816 Upgrade DataTables from 2.1.8 to 2.3.4
This enhancement upgrades the DataTables JavaScript library from version 2.1.8 to 2.3.4.This brings in upstream fixes and improvements released since 2.1.8, including bug fixes and general stability updates.No functional changes are expected in Koha beyond those provided by the updated DataTables library.
40933 Add SMS support under Add message feature
This new feature allows staff with appropriate permissions, send_messages_to_borrowers, to send SMS messages patrons from the patron details pages.Notice templates can be defined, and used for defaults, using the Patrons (custom message) module.
41206 Add collection to transfers to receive
41692 “See all charges” link in the guarantor details does not activate Guarantees charges tab
41885 Rename iso2709 to MARC for the staff interface download options for the cart and lists (to match the OPAC)
This enhancement renames iso2709 to MARC for staff interface cart and lists download options. This now matches the OPAC.
28495 Add hint about whitespace usage upon library creation
41980 SIP codes in the new SIP Config UI could have better descriptions
This enhancement improves the descriptions and tooltips for several SIP2 account form fields: – Allow and hide fields: instead of just codes (such as CQ), most codes now include a description (such as CQ – Valid Patron Password) – Improved tooltips for these fields: . CR item field . CT always send . CV always send 00 on success . CV triggers alert – Adds tooltips in the template section for the AE, AV, and DA field templates
23269 Long hold queues are slowing the service
The patron holds table now uses the REST API to fetch, display and modify hold information, replacing the previous implementation.
What Changed
- Migrated the patron holds table to use REST API endpoints for data retrieval.
- All existing holds table functionality remains intact with improved performance and maintainability
Impact
This change modernizes the holds table architecture by leveraging the REST API, providing:
- Better separation of concerns between frontend and backend
- Improved consistency with other API-driven features
- Foundation for future enhancements to holds management
Sponsored by Koha-Suomi Oy
37773 Show search term in cataloging search results
This enhancement updates the cataloging search results page so that the search term is shown in the page title, breadcrumb, and headings (Staff interface > Cataloging > Cataloging search).
39715 Do not quote DataTables options
This patch updates templates so that the options passed to DataTables, via KohaTable, are not quoted. The quotes are not necessary, and are not consistent with official DataTables documentation. This establishes a standard for us to follow in the future.
39780 Update library groups form to use grid layout
40113 Update accounting admin pages to use grid layout for forms
41350 Terminology: Biblio was already issued
This changes the log viewer message “Biblio was already issued” to “An item from this bibliographic record is already checked out.”
This action is recorded in the logs when AllowMultipleIssuesOnABiblio is set to “Don’t allow” and staff confirm a check-out where a patron has already checked out another item for the record.
41638 Patron record field labels lack distinct id in HTML
This enhancement adds ids to all the labels on memberentry.pl with the convention of for easier jquery selection.
41823 Update acquisitions admin pages to use grid layout for forms
41827 Update authority types pages to use grid layout for forms
16994 Import and export MARC modification templates
This enhancement brings in the possibility for a librarian to export a Marc modification template in a json file. This can serve either as a backup or for sharing purposes.
40135 Record diff in action logs when modifying a bibliographic record
This enhancement adds a ‘diff’ to the action logs when modifying a bibliographic record (creating, modifying, and deleting). Previously, no diff was recorded (although some information was recorded in the Info column).Note: Details for changes to items were already recorded a diff.
40136 Record diff in action logs when modifying a patron
This enhancement adds a ‘diff’ to the action logs when modifying a patron (creating, modifying, changing a card number, and deleting). Previously, no diff was recorded (although some information was recorded in the info column).
40905 Past unique holidays not shown when enabling Show past checkbox
41126 Move shelving location into a separate column in inventory
42032 Add diff support to AUTHORITIES action logs
This enhancement adds a ‘diff’ to the action logs for authority record changes (creating, modifying, and deleting). Previously, no diff was recorded (although some information was recorded in the Info column).