https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26635 --- Comment #47 from Tomás Cohen Arazi <tomascohen@gmail.com> --- (In reply to David Cook from comment #46)
In any case, I reckon backwards compatibility is important, especially since we're still using "v1" for the API, so I don't think we can change the existing "location" field.
Agreed!
On non-Koha projects where I've needed to maintain backwards compatibility, I've added fields like "location_description".
Right. We also need the category it is linked to, do we can draw things like drop-downs.
Sometimes, I think that authorised values should be removed from item data, and replaced with proper foreign key references.
Location is an important field which by rights deserves its own database table I think.
Locations, collections... We've done that with credit/debit tired recently.
Of course, that data migration is easier said than done...
Generally speaking, the problem is lack of infinite time. -- You are receiving this mail because: You are watching all bug changes.