https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41534

--- Comment #2 from David Nind <[email protected]> ---
Some areas (not exhaustive) where British English spelling is used.

System preference descriptions
==============================

These system preferences use "cancelling" in the description:
- AcqItemSetSubfieldsWhenReceiptIsCancelled
- CancelOrdersInClosedBaskets
- TransferWhenCancelAllWaitingHolds

These system preferences use "cancelled" in the description:
- HoldCancellationRequestSIP
- SearchCancelledAndInvalidISBNandISSN (and in the system preference name)

Authorized values
=================

AR_CANCELLATION authorized values category:
- OPAC authorized value: description is "Cancelled from the OPAC user page"

ERM_AGREEMENT_CLOSURE_REASON authorized values category:
- cancelled: authorized value and description

User interface
==============

ERM
---

ERM module > Agreements > New agreement:
- Status: select closed
- Closure reason: Cancelled

Circulation - Bookings
----------------------

1. Enable the booking module
2. Make Books bookable
3. Place a booking for a record
4. Note the filters on the bookings section: Exclude cancelled
5. Note in the status column: "Cancelled: Whatever you entered for the
cancellation reason" 

Circulation - Recalls
---------------------

1. Enable Recalls
2. Set a circulation and fines rule
3. Check out an item to a patron
4. Create a recall, and then cancel it in the staff interface
5. On the record in the staff interface, cancel the recall: Recalls > Actions >
Cancel
6. In the last column it shows as "Cancelled"
7. Go to: [the patron that created the recall] > Recalls history: note that in
the status column there is "Cancelled on [date]"
8. Go to: [the patron account in the OPAC > Recalls history: note that in the
status column there is "Cancelled on [date]"
9. Go to: Circulation > Recalls > Old recalls: note that in the status column
there is "Cancelled on [date]"

Patrons - Accounting
--------------------

1. Go to a patron's account
2. Create a manual invoice
3. From the transactions tab, Actions > Cancel charge
4. Note in the 'Account type' column:
   - Cancelled charge (for the transaction to cancel the charge)
   - Manual fee (Cancelled charge) (for the original charge)

Administration - Jobs
---------------------

Status column for a canceled job - shown as "Cancelled"

Article requests
----------------

1. Enable the ArticleRequests system preference
2. Place an article request for a patron on a record
3. Go to Circulation > Patron request > Article requests
4. Cancel the request: Actions > Cancel request
5. In the dialog box, for the cancellation reason select "Cancelled from the
OPAC user page"

Acquisitions - "Cancelled orders" heading should be "Canceled orders"
---------------------------------------------------------------------

1. Go to the basket for My Vendor
2. Add an order
3. In the "Cancel order" column, click "Cancel order" for the order
4. Note the heading for a section of the basket is "Cancelled orders", instead
of "Canceled orders"

Other places
============

From using just regular case-insensitive searches, cancelling and cancelled are
used the most:
- canceled: 246
- cancelled: 942
- canceling: 10
- cancelling: 106
- cancellation: 1111
- cancelation: 3

Other things
============

Should we fix code comments and coded values?
- I think there is too many of them, and little gain from doing so.

Should we fix notices?

For UNIMARC installer data, should this be left as cancelled/cancelling? I
think so, as UNIMARC is not used by the US (as far as I'm aware).

Previous release notes would be left as they are.

All the tests use a mix, but predominately with double ls.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to