Bug 22108 - Items generated through MARCItemFieldsToOrder do not receive values applied in Item Information and Default Accounting Details
Summary: Items generated through MARCItemFieldsToOrder do not receive values applied i...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-11 20:10 UTC by Andrew Fuerste-Henry
Modified: 2024-01-31 21:13 UTC (History)
8 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2019-01-11 20:10:35 UTC 
When adding titles to a basket from a staged file (acqui/addorderiso2709.pl), item and fund choices can be applied item-by-item on the Select To Import tab or can be applied to all titles at once using the Item Information or Default Accounting Details tabs.

However, if the library is using MARCItemFieldsToOrder to pull some of these values from vendor-supplied MARC files, Koha will ignore selections made on the Item Information or Default Accounting Details tabs. Nothing in the interface indicates that values selected on those tabs will not be used.
Comment 1 Ron Houk 2019-05-06 14:52:18 UTC 
This bug has been effecting our workflow here.  Since we're not able to import "Date Acquired" via MARCItemsFieldstoOrder, it would be handy to be able to set this date on the "Item information" tab.
Comment 2 kate 2024-01-31 21:13:38 UTC 
Andrew, as usual your insight saved me - I took everything out of MARCItemFieldsToOrder and put price into MARCFieldsToOrder. Replacement Price is still left blank but the item information comes over correctly (so funds and status are correct). This has been causing enough disruption to our workflow that I have been contemplating asking to roll back to the previous version of Koha.