https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26635 --- Comment #46 from David Cook <dcook@prosentient.com.au> --- 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. Whether we embed the data or provide a lookup reference, I think it needs to be as a separate field. On non-Koha projects where I've needed to maintain backwards compatibility, I've added fields like "location_description". -- 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. Of course, that data migration is easier said than done... -- You are receiving this mail because: You are watching all bug changes.