Bug 23282

Summary: Show all columns in Batch Item Modification and Batch Item Deletion
Product: Koha Reporter: Kelly McElligott <kelly>
Component: ToolsAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: andrewfh, jonathan.druart, severine.queune
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6018
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24087
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Attachments: Bug 23282: Display all item's subfields when batch item editing

Description Kelly McElligott 2019-07-08 19:48:49 UTC
Currently when using either the Batch Item Modification or Batch Item Deletion, columns will only appear if there is in fact data in these fields.  IF there is no value in the Source of Acquisition (for example) field, then the column does not appear with a blank value in it.  Libraries may want to see all columns with blank data for double checking purposes.
Comment 1 Kelly McElligott 2019-07-08 19:49:54 UTC
I can say that if one has a batch of 100 barcodes and 1 item has a value in the Source of Acquisitions, then this column will appear and the items that don't have a value in them, the column will still appear.
Comment 2 Jonathan Druart 2019-11-21 14:37:40 UTC
Created attachment 95660 [details] [review]
Bug 23282: Display all item's subfields when batch item editing

This is a start, but the display needs to be adjusted.

Also there is something wrong in the logic (.pl).

What is supposed to happen if a librarian decides to display in tab 10 a subfield that is not part of 942?
Should we allow that?
Comment 3 Jonathan Druart 2019-11-22 10:35:00 UTC
(In reply to Jonathan Druart from comment #2)
> Created attachment 95660 [details] [review] [review]
> Bug 23282: Display all item's subfields when batch item editing
> 
> This is a start, but the display needs to be adjusted.
> 
> Also there is something wrong in the logic (.pl).
> 
> What is supposed to happen if a librarian decides to display in tab 10 a
> subfield that is not part of 942?
> Should we allow that?

I opened a new bug report for that, see bug 24087.
Comment 4 Andrew Fuerste-Henry 2020-01-17 17:12:03 UTC
Removing In Discussion flag as Jonathan opened a new bug for his question.