Bug 36808 - Slips should be a message transport type
Summary: Slips should be a message transport type
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Martin Renvoize
QA Contact: Testopia
URL:
Keywords:
Depends on: 35285
Blocks: 15278 36809
  Show dependency treegraph
 
Reported: 2024-05-08 06:35 UTC by Martin Renvoize
Modified: 2024-05-13 16:04 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize 2024-05-08 06:35:40 UTC
Currently we create entirely new notices for SLIP type notices when really they're just a different medium and thus should be a message transport type.

I propose adding a SLIP message transport type and where appropriate merging the current SLIP notices into their corresponding non-slip counterparts.

A 'slip' is just a small form printer and likely to have similar summary detail as an SMS for example.
Comment 1 Martin Renvoize 2024-05-08 06:36:18 UTC
This would also make it clearer when SlipCSS and NoticeCSS should be used.
Comment 2 Lisette Scheer 2024-05-13 16:04:40 UTC
These are the slips listed as slips in my devbox:
 
Current Code     Transport   New Code
ACCOUNT_SUMMARY  print       ACCOUNT_SUMMARY
AR_SLIP          print       AR_NEW
CHECKINSLIP      print       CHECKIN
HOLD_SLIP        email       HOLD
ISSUEQSLIP       email       CHECKOUTS
OVERDUES_SLIP    print       ODUE (/first OD notice if different?) 

PRES_TRAIN_ITEM  print -> This doesn't have a corresponding email notice, so we could change this to slip transport type
TRANSFERSLIP     email-> This doesn't have a corresponding email notice, so we could change this to slip transport type
ISSUESLIP        email -> -> This doesn't have a corresponding email notice, so we could change this to slip transport type
SR_SLIP          email -> (This looks like it's more an email than a slip?)