http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #1 from David Cook <dcook@prosentient.com.au> --- Doesn't this already exist with the "location" field? If you're losing the permanent location, it could be that there's a bug... -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 --- Comment #3 from David Cook <dcook@prosentient.com.au> --- (In reply to Christopher Brannon from comment #2)

(In reply to David Cook from comment #1)

...

Doesn't this already exist with the "location" field?

Sort of, but it is tied in with the PROC and CART features. How would you retain the permanent location, the temp location of the display, and the PROC/CART locations?

I guess if you didn't want the item going back to display, that would work, but what if you have a special holiday or themed collection residing somewhere for a while? After the first time out it goes back to its permanent location.

Christopher

Ahh, I see what you're saying. I've always found items in Koha to be a bit funny/confusing. There's a permanent_location, location, ccode (collection code). Personally, I would think the collection would be synonymous with shelving location, and that location would be more like "status" (in processing, on cart, on shelf, etc). If anything, I would think it would make more sense to have ccode and location/status. Maybe permanent_ccode if you wanted to designate the "true" collection for an item, and then have an ability to add it to temporary collections without losing track of the original collection. -- You might also be able to use the rotating collections feature: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8836 Once upon a time, I worked at a multilingual library where we had books in 29 different languages each with their own set of collections. Every so often, a small rotating collection would be created from some of these books, it would be sent around the province (in Canada) to other libraries before returning home to our library where the books would go back to their original collection. In this case, you wouldn't have to transfer the collection to another library. You could use it as a temporary collection. That's theoretical though. I haven't used this feature in Koha... worth experimenting or talking to Kyle Hall about it, I imagine. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 --- Comment #5 from David Cook <dcook@prosentient.com.au> --- (In reply to Katrin Fischer from comment #4)

I think a lot of libraries use the collection with something unrelated to the location in the library - for example it could be a special donation they want to highlight, that was shelved with the other books.

I think the rotating collection an item belongs to is currently not visible in the OPAC, but might be something that could be added. A problem might be searching for it - that would be easier to solve if it was a field in the item record. Hm.

Fair enough. I suppose my concern is that there are already 43 columns in the items table, and we're running out of conventional subfield codes in the 952. I suppose we could start using capital letters or any of the other interesting things available in the following range: [\dA-Za-z!"#$%&'()*+,-./:;<=>?{}_^`~\[\]\\]{1} (http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd) -- You are receiving this mail because: You are watching all bug changes.