https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24857 --- Comment #149 from Kyle M Hall <kyle@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #126)
This one is a little scary already, but going in for a first review :)
1) QA script Fixed!
2) Doubled up use statement in Biblio.pm
Fixed!
3) REST API
I'd love to have Tomas take a look on the REST API bits here.
I'll ask Tomas to take a look!
4) sysprefs.sql
Fixed!
5) Pref (question)
Enable|Don't enable volumes feature to allow collecting groups of items on a record into volumes.
Does it mean the items have to be from the same record or could they be from different ones?
We decided early on that volumes would have contain only items within the same record.
6) Table configuration
The new volumn column on the holdings table needs to be added to the table configuration options.
This table is not a datatable so that doesn't really apply.
7) GUI
"Create new" on the items table would work nicer as "Create new volume" or "New volume" to give context to translators and for better accessibility.
Fixed!
Future improvements: It might be nice to offer a kind of grouped view for the items in volumes... but I am not sure yet how this would work best. It might be nice to show the volumes in the OPAC as well.
Agreed. If volume management turns out to be popular, that would be an easy extension to this work.
8) Use case and future plans?
Can you tell a bit about in what context or use case this partner is using this? Serials?
Our current and only use case at this time is for volume level holds. Some libraries keep different volumes on the same record ( imagine different seasons of a TV series ). In these cases, a bib level hold won't work if you only want Season 1, but if there are 3 copies of season one, you wouldn't want an item level hold either. Volume level holds solve this problem. -- You are receiving this mail because: You are watching all bug changes.