Bug 14379 - Batch item modification tool can't change subfields stored in more_subfields_xml
Summary: Batch item modification tool can't change subfields stored in more_subfields_xml
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-12 14:26 UTC by Pablo AB
Modified: 2023-08-05 12:02 UTC (History)
3 users (show)

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


Attachments
Subfield $1 is missing in Batch Item Modification process (51.49 KB, image/png)
2015-09-05 17:25 UTC, Claudio Costales
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo AB 2015-06-12 14:26:01 UTC
On a framework a librarian create custom item subfields, like withdrawn date or date when item was sent to bookbinding sector ("$D", uppercase).

Batch item modification tool (batchMod.pl) doesn't let you change this new item subfields (saved on more_subfields_xml).
Comment 1 Joonas Kylmälä 2015-08-20 11:08:40 UTC
Can you list the steps of how to reproduce this bug. I have had hard time trying to figure out how to reproduce this bug.
Comment 2 Claudio Costales 2015-09-05 17:23:56 UTC
It also can not be changed the subfield $1 (lost status) which is a standard Koha subfield. See image attached.
Comment 3 Claudio Costales 2015-09-05 17:25:18 UTC
Created attachment 42422 [details]
Subfield $1 is missing in Batch Item Modification process
Comment 4 Claudio Costales 2016-09-08 20:47:53 UTC
Subfield $1 is missing in Batch Item Modification tool (tag 952). Is there a reason for this? I can not find a configuration rule...
Comment 5 Katrin Fischer 2020-01-07 22:17:56 UTC
(In reply to Claudio from comment #4)
> Subfield $1 is missing in Batch Item Modification tool (tag 952). Is there a
> reason for this? I can not find a configuration rule...

There was, because it behaved differently than changing the lost status form the items tab. I think this part was fixed, as MarkLostItemsAsReturned includes the option 'batch item modification tool' now.
Comment 6 Katrin Fischer 2023-08-05 12:02:18 UTC
I think if $1 is still an issue (I believe we fixed that?), than it should be on a separate bug report.