Bug 9156: itemcallnumber not pulling more than 2 subfields
authorOwen Leonard <oleonard@myacpl.org>
Tue, 19 Nov 2019 14:56:05 +0000 (14:56 +0000)
committerJoy Nelson <joy@bywatersolutions.com>
Fri, 31 Jan 2020 21:25:22 +0000 (21:25 +0000)
commitc536b04b6db249e887043459f34742cf6b5da8e4
tree003733307b888233931cf9b74af486ef11f70ad6
parent6e788eaeb1b08d53fc7528d0c6cf007e80a46169
Bug 9156: itemcallnumber not pulling more than 2 subfields

When the itemcallnumber system preference is defined, the item add form
pulls data from the specified tag and subfield(s) to pre-populate the
call number field. This update makes it possible to build the
prepopulated callnumber from more than just the first two subfields.

To test, apply the patch and update the itemcallnumber system preference
so that it includes more than two subfields. For instance, "092abef"

 - Edit a bibliographic record and populate the specified subfields.
   e.g. subfield a -> "One", b-> "Two", e-> "Three", f-> "Four".
 - Save the record and go to the add/edit items screen.
 - The call number field should contain a string which contains each of
   the subfields you populated, concatenated with spaces: "One Two Three
   Four."
 - Test with other numbers of subfields.
 - Test with an empty itemcallnumber preference.

Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com>
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Joy Nelson <joy@bywatersolutions.com>
cataloguing/additem.pl