https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19814 --- Comment #58 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Benjamin Daeuber from comment #56)
(In reply to Marcel de Rooy from comment #54)
For testing you currently need:
insert into authorised_value_categories (category_name,is_system) values ( 'BATCH_CHECKIN_DEFAULTS', 1 );
insert into authorised_values (category, authorised_value, lib, lib_opac, is_system) values ( 'BATCH_CHECKIN_DEFAULTS', 'BATCH_CHECKIN_ENABLED', 'Enable batch mode', 'Enable batch mode', 1 ), ( 'BATCH_CHECKIN_DEFAULTS', 'BATCH_CHECKIN_KEEP_SELECTION', 'Keep selection', 'Keep selection', 1 ), ( 'BATCH_CHECKIN_DEFAULTS', 'BATCH_CHECKIN_IGNORE_NOTISSUED', 'Ignore NOTISSUED message', 'Ignore NOTISSUED message', 1 ), ( 'BATCH_CHECKIN_DEFAULTS', 'BATCH_CHECKIN_CONFIRM_TRANSFER', 'Confirm transfer', 'Confirm transfer', 1 ), ( 'BATCH_CHECKIN_DEFAULTS', 'BATCH_CHECKIN_CONFIRM_HOLD', 'Confirm hold', 'Confirm hold', 1 );
From this I would gather libraries could toggle on or off trapping holds, receiving messages and confirming transfers? Leaving the option to use the holds queue or items it transfer tools to find those items (same as a library would if using SIP check-in or batch item modification)?
What about making these configurable by the user at the point of check-in as well? I can see a staff person wanting to configure this behavior based on current work levels. For example, we've bunch of items to deal with after a closed day and we need to get them all checked in to free up space and we'll go around later and pick them. On a more normal day we might want a different behavior. Similarly if we're handling items coming in on a shuttle vs. regular checkins.
Still thinking about this. But please note that we want to add batch checkin here while touching core circulation such as the famous AddReturn function here as little as possible.. -- You are receiving this mail because: You are watching all bug changes.