bug 1615: AddItem() now sets issues, renewals, and reserves
When an item was created, the renewals, issues, and reserves columns were not set from the MARC data. This was noticed particularly in the context of batch loads, where a user might supply data for those fields. Signed-off-by: Chris Cormack <crc@liblime.com> Signed-off-by: Joshua Ferraro <jmf@liblime.com>
This commit is contained in:
parent
45d570e378
commit
6bb4eb130d
1 changed files with 6 additions and 0 deletions
|
@ -3837,6 +3837,9 @@ sub _koha_new_items {
|
||||||
paidfor = ?,
|
paidfor = ?,
|
||||||
location = ?,
|
location = ?,
|
||||||
onloan = ?,
|
onloan = ?,
|
||||||
|
issues = ?,
|
||||||
|
renewals = ?,
|
||||||
|
reserves = ?,
|
||||||
cn_source = ?,
|
cn_source = ?,
|
||||||
cn_sort = ?,
|
cn_sort = ?,
|
||||||
ccode = ?,
|
ccode = ?,
|
||||||
|
@ -3867,6 +3870,9 @@ sub _koha_new_items {
|
||||||
$item->{'paidfor'},
|
$item->{'paidfor'},
|
||||||
$item->{'location'},
|
$item->{'location'},
|
||||||
$item->{'onloan'},
|
$item->{'onloan'},
|
||||||
|
$item->{'issues'},
|
||||||
|
$item->{'renewals'},
|
||||||
|
$item->{'reserves'},
|
||||||
$item->{'items.cn_source'},
|
$item->{'items.cn_source'},
|
||||||
$items_cn_sort,
|
$items_cn_sort,
|
||||||
$item->{'ccode'},
|
$item->{'ccode'},
|
||||||
|
|
Loading…
Reference in a new issue