Creative re-purposing of major fields
I'm currently using Koha to catalog a collection of mostly non-book resources at my school, many of which are stored on physical DVDs and/or online available for download. I'm thinking of re-purposing some of Koha's major data fields where their usual meaning isn't all that relevant to this project. For example, I plan to create my call numbers so they are sufficient to identify the physical location within a given branch. This will free up "Collection" and "Shelf Location" for other, more relevant classifications. Before I start mapping this out, I first want to get feedback that I'm not way off-track thinking this way. First question: I believe that the original intention was a hierarchy for physical location: Home branch --> Collection --> Shelving location --> Call number If I re-purpose these fields so that e.g. Collection is used for distinguishing between "Disc-Data" vs "Disc-Video" vs "Disc-Mixed", is their any remnant of the above original hierarchy that will cause trouble? Is Collection completely independent of Branch in the database and UI design, or is there some enforcement of one Collection being "contained" within a Branch? Same question of course with Shelving location relative to both Collection and Branch - say I used this field to map to "Age Appropriateness" (Adult-only, Young adult, Juvenile, Early learners). Note that the Age factor is a biblio level one, while many biblios will have both a Data and a Video disc - a member may want to borrow only one or both. Next question is - are these easily used as search factors in the OPAC, so members can browse a subject only looking at VDO discs suitable for Juveniles? I don't mind a bit of customization, assuming this can be preserved across upgrades. Obviously the latter fits well within Item type, but this seems designed for factors that are affect circulation policies - loan duration, charges etc. Last question - is that field even available as a search limiter? I could use "Film-Disc-Data" and "Film-Disc-Video" or "Film-Disc-Mixed", but many members don't care about the distinction, so I'm thinking it would be simplest to just use "Film" as a monolithic category and not worry about the media details there; as I'd rather have them manually pick and choose among their results than have to run multiple searches. Obviously besides having the direct questions addressed, any general ideas or suggestions would be most welcome.
Sorry to be talking to myself here, but in doing some more extensive googling, I came across this: http://library-matters.blogspot.com/2009/03/dont-be-afraid-of-using-lots-of-... Thanks Joann! And this: http://koha.org/documentation/manual/3.0/cataloging/item-fields-data-migrati... These answered some of my questions - summarizing for future googlers (list members please correct me if this is wrong) ---------------------- Administrator can set an option to allow using either Collection or Item type for the OPAC's Advanced search, but not both (enhancement request! 8-) Item type does determine circulation rules in effect for an item, but its usage doesn't need to be limited to this function - can have 50 item types covered by four rules. Shelving location is not available for advanced search. ---------------------- The question remains on whether the Collection and/or Shelving location can be assigned to items completely independently of Home branch - I realize the latter especially is "supposed to be" subsidiary to Branch, but since I don't need to use it for that function, and it displays in the OPAC, can I use it for something like Age appropriateness across locations? On Tue, Feb 15, 2011 at 6:30 PM, <hansbkk@gmail.com> wrote:
I'm currently using Koha to catalog a collection of mostly non-book resources at my school, many of which are stored on physical DVDs and/or online available for download.
I'm thinking of re-purposing some of Koha's major data fields where their usual meaning isn't all that relevant to this project. For example, I plan to create my call numbers so they are sufficient to identify the physical location within a given branch. This will free up "Collection" and "Shelf Location" for other, more relevant classifications.
Before I start mapping this out, I first want to get feedback that I'm not way off-track thinking this way. First question:
I believe that the original intention was a hierarchy for physical location: Home branch --> Collection --> Shelving location --> Call number
If I re-purpose these fields so that e.g. Collection is used for distinguishing between "Disc-Data" vs "Disc-Video" vs "Disc-Mixed", is their any remnant of the above original hierarchy that will cause trouble? Is Collection completely independent of Branch in the database and UI design, or is there some enforcement of one Collection being "contained" within a Branch?
Same question of course with Shelving location relative to both Collection and Branch - say I used this field to map to "Age Appropriateness" (Adult-only, Young adult, Juvenile, Early learners). Note that the Age factor is a biblio level one, while many biblios will have both a Data and a Video disc - a member may want to borrow only one or both.
I'm currently using Koha to catalog a collection of mostly non-book resources at my school, many of which are stored on physical DVDs and/or online available for download.
I'm thinking of re-purposing some of Koha's major data fields where
"Shelving location is not available for advanced search." See a patch I submitted a year ago: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4329 I don't think it's been incorporated into head yet. Jane Wagner Senior Project Manager LibLime, a division of PTFS Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@liblime.com -----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of hansbkk@gmail.com Sent: Tuesday, February 15, 2011 8:42 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Creative re-purposing of major fields Sorry to be talking to myself here, but in doing some more extensive googling, I came across this: http://library-matters.blogspot.com/2009/03/dont-be-afraid-of-using-lots-o f-item.html Thanks Joann! And this: http://koha.org/documentation/manual/3.0/cataloging/item-fields-data-migra tion These answered some of my questions - summarizing for future googlers (list members please correct me if this is wrong) ---------------------- Administrator can set an option to allow using either Collection or Item type for the OPAC's Advanced search, but not both (enhancement request! 8-) Item type does determine circulation rules in effect for an item, but its usage doesn't need to be limited to this function - can have 50 item types covered by four rules. Shelving location is not available for advanced search. ---------------------- The question remains on whether the Collection and/or Shelving location can be assigned to items completely independently of Home branch - I realize the latter especially is "supposed to be" subsidiary to Branch, but since I don't need to use it for that function, and it displays in the OPAC, can I use it for something like Age appropriateness across locations? On Tue, Feb 15, 2011 at 6:30 PM, <hansbkk@gmail.com> wrote: their usual
meaning isn't all that relevant to this project. For example, I plan to create my call numbers so they are sufficient to identify the physical location within a given branch. This will free up "Collection" and "Shelf Location" for other, more relevant classifications.
Before I start mapping this out, I first want to get feedback that I'm not way off-track thinking this way. First question:
I believe that the original intention was a hierarchy for physical location: Home branch --> Collection --> Shelving location --> Call number
If I re-purpose these fields so that e.g. Collection is used for distinguishing between "Disc-Data" vs "Disc-Video" vs "Disc-Mixed", is their any remnant of the above original hierarchy that will cause trouble? Is Collection completely independent of Branch in the database and UI design, or is there some enforcement of one Collection being "contained" within a Branch?
Same question of course with Shelving location relative to both Collection and Branch - say I used this field to map to "Age Appropriateness" (Adult-only, Young adult, Juvenile, Early learners). Note that the Age factor is a biblio level one, while many biblios will have both a Data and a Video disc - a member may want to borrow only one or both.
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Also see that there are issues with the patch that require additional work. -- Owen On Feb 15, 2011, at 8:56 AM, "Wagner, Jane" <jwagner@liblime.com> wrote:
"Shelving location is not available for advanced search."
See a patch I submitted a year ago:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4329
I don't think it's been incorporated into head yet.
Jane Wagner Senior Project Manager LibLime, a division of PTFS Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@liblime.com
-----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of hansbkk@gmail.com Sent: Tuesday, February 15, 2011 8:42 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Creative re-purposing of major fields
Sorry to be talking to myself here, but in doing some more extensive googling, I came across this: http://library-matters.blogspot.com/2009/03/dont-be-afraid-of-using-lots-o f-item.html
Thanks Joann!
And this: http://koha.org/documentation/manual/3.0/cataloging/item-fields-data-migra tion
These answered some of my questions - summarizing for future googlers (list members please correct me if this is wrong)
---------------------- Administrator can set an option to allow using either Collection or Item type for the OPAC's Advanced search, but not both (enhancement request! 8-)
Item type does determine circulation rules in effect for an item, but its usage doesn't need to be limited to this function - can have 50 item types covered by four rules.
Shelving location is not available for advanced search.
---------------------- The question remains on whether the Collection and/or Shelving location can be assigned to items completely independently of Home branch - I realize the latter especially is "supposed to be" subsidiary to Branch, but since I don't need to use it for that function, and it displays in the OPAC, can I use it for something like Age appropriateness across locations?
I'm currently using Koha to catalog a collection of mostly non-book resources at my school, many of which are stored on physical DVDs and/or online available for download.
I'm thinking of re-purposing some of Koha's major data fields where
On Tue, Feb 15, 2011 at 6:30 PM, <hansbkk@gmail.com> wrote: their usual
meaning isn't all that relevant to this project. For example, I plan to create my call numbers so they are sufficient to identify the physical location within a given branch. This will free up "Collection" and "Shelf Location" for other, more relevant classifications.
Before I start mapping this out, I first want to get feedback that I'm not way off-track thinking this way. First question:
I believe that the original intention was a hierarchy for physical location: Home branch --> Collection --> Shelving location --> Call number
If I re-purpose these fields so that e.g. Collection is used for distinguishing between "Disc-Data" vs "Disc-Video" vs "Disc-Mixed", is their any remnant of the above original hierarchy that will cause trouble? Is Collection completely independent of Branch in the database and UI design, or is there some enforcement of one Collection being "contained" within a Branch?
Same question of course with Shelving location relative to both Collection and Branch - say I used this field to map to "Age Appropriateness" (Adult-only, Young adult, Juvenile, Early learners). Note that the Age factor is a biblio level one, while many biblios will have both a Data and a Video disc - a member may want to borrow only one or both.
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
With a little modification, I've gotten the original patch to apply, and it works for searching on the OPAC. I think the next steps to get this incorporated into Koha is to mimic the functionality on the staff side, and add a system preference to control it. It's on my list, but I'd happily pass it off to anyone else who wants to tackle it :) -Ian On Tue, Feb 15, 2011 at 9:00 AM, Owen Leonard <oleonard@myacpl.org> wrote:
Also see that there are issues with the patch that require additional work.
-- Owen
On Feb 15, 2011, at 8:56 AM, "Wagner, Jane" <jwagner@liblime.com> wrote:
"Shelving location is not available for advanced search."
See a patch I submitted a year ago:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4329
I don't think it's been incorporated into head yet.
Jane Wagner Senior Project Manager LibLime, a division of PTFS Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@liblime.com
-----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of hansbkk@gmail.com Sent: Tuesday, February 15, 2011 8:42 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Creative re-purposing of major fields
Sorry to be talking to myself here, but in doing some more extensive googling, I came across this:
http://library-matters.blogspot.com/2009/03/dont-be-afraid-of-using-lots-o
f-item.html
Thanks Joann!
And this:
http://koha.org/documentation/manual/3.0/cataloging/item-fields-data-migra
tion
These answered some of my questions - summarizing for future googlers (list members please correct me if this is wrong)
---------------------- Administrator can set an option to allow using either Collection or Item type for the OPAC's Advanced search, but not both (enhancement request! 8-)
Item type does determine circulation rules in effect for an item, but its usage doesn't need to be limited to this function - can have 50 item types covered by four rules.
Shelving location is not available for advanced search.
---------------------- The question remains on whether the Collection and/or Shelving location can be assigned to items completely independently of Home branch - I realize the latter especially is "supposed to be" subsidiary to Branch, but since I don't need to use it for that function, and it displays in the OPAC, can I use it for something like Age appropriateness across locations?
I'm currently using Koha to catalog a collection of mostly non-book resources at my school, many of which are stored on physical DVDs and/or online available for download.
I'm thinking of re-purposing some of Koha's major data fields where
On Tue, Feb 15, 2011 at 6:30 PM, <hansbkk@gmail.com> wrote: their usual
meaning isn't all that relevant to this project. For example, I plan to create my call numbers so they are sufficient to identify the physical location within a given branch. This will free up "Collection" and "Shelf Location" for other, more relevant classifications.
Before I start mapping this out, I first want to get feedback that I'm not way off-track thinking this way. First question:
I believe that the original intention was a hierarchy for physical location: Home branch --> Collection --> Shelving location --> Call number
If I re-purpose these fields so that e.g. Collection is used for distinguishing between "Disc-Data" vs "Disc-Video" vs "Disc-Mixed", is their any remnant of the above original hierarchy that will cause trouble? Is Collection completely independent of Branch in the database and UI design, or is there some enforcement of one Collection being "contained" within a Branch?
Same question of course with Shelving location relative to both Collection and Branch - say I used this field to map to "Age Appropriateness" (Adult-only, Young adult, Juvenile, Early learners). Note that the Age factor is a biblio level one, while many biblios will have both a Data and a Video disc - a member may want to borrow only one or both.
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
2011/2/15 Ian Walls <ian.walls@bywatersolutions.com>:
See a patch I submitted a year ago: Also see that there are issues with the patch that require additional work. With a little modification, I've gotten the original patch to apply, and it works for searching on the OPAC. I think the next steps to get this
Well, I'm coming from a plain ol' user's POV, so if it's not in stable it's not available 8-) NBD anyway, just because it's not available as a search factor, the fact that it displays in the OPAC, means I'd like to use it to display meaningful information about the item. So how about it guys, could someone try to answer my question? Here's a concrete example - suppose I've got a huge "Animation" collection, large "Disney" and "Directors" collections, and a smaller "Barbie" one. Could these items be located at multiple library branches? Say I've got shelving locations called "Princesses" and "Fairies" and "Action". Can these span across Collections, so that items from both "Directors" and "Animation" could be in the "Action" shelving location. Or do the "Disney Princesses" need to be a separate shelving location from the "Barbie Princesses"? I realize this is a whimsical illustration, and am not asking about the logic of this from a librarian's POV - strictly on the IT-technical question of whether the Koha UI or DB enforce a "containing hierarchy" relationship between these fields. While I'm at it, I'd like confirmation that the call number sequence is also completely separate from all of the above (I think "orthogonality" is a word?) and that this is the order used for the OPAC's "browse the shelf" functionality?
* hansbkk@gmail.com (hansbkk@gmail.com) wrote:
2011/2/15 Ian Walls <ian.walls@bywatersolutions.com>:
See a patch I submitted a year ago: Also see that there are issues with the patch that require additional work. With a little modification, I've gotten the original patch to apply, and it works for searching on the OPAC. I think the next steps to get this
Well, I'm coming from a plain ol' user's POV, so if it's not in stable it's not available 8-)
Luckily not everyone has that attitude, or things never would get into stable :)
NBD anyway, just because it's not available as a search factor, the fact that it displays in the OPAC, means I'd like to use it to display meaningful information about the item.
So how about it guys, could someone try to answer my question?
Here's a concrete example - suppose I've got a huge "Animation" collection, large "Disney" and "Directors" collections, and a smaller "Barbie" one.
Could these items be located at multiple library branches?
Say I've got shelving locations called "Princesses" and "Fairies" and "Action". Can these span across Collections, so that items from both "Directors" and "Animation" could be in the "Action" shelving location. Or do the "Disney Princesses" need to be a separate shelving location from the "Barbie Princesses"?
I realize this is a whimsical illustration, and am not asking about the logic of this from a librarian's POV - strictly on the IT-technical question of whether the Koha UI or DB enforce a "containing hierarchy" relationship between these fields.
In that case, this query belongs on the koha-devel list. That's the place for technical discussions.
While I'm at it, I'd like confirmation that the call number sequence is also completely separate from all of the above (I think "orthogonality" is a word?) and that this is the order used for the OPAC's "browse the shelf" functionality?
The answer is yes, Koha does not force you to shelve things in a certain way. There is no enforced relationship between collection code, shelving location and callnumber. You can fill those fields with whatever you like. Also I note in an earlier mail from you, you were looking at the old koha site. Make sure you use www.koha-community.org, that is the official and maintained site. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
On Wed, Feb 16, 2011 at 12:34 AM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
The question remains on whether the Collection and/or Shelving location can be assigned to items completely independently of Home branch - I realize the latter especially is "supposed to be" subsidiary to Branch, but since I don't need to use it for that function, and it displays in the OPAC, can I use it for something like Age appropriateness across locations?
Thanks very much Chris, looks like the only thing holding back my creativity on classifying our collection will be (should be) common sense 8-)
Well, I'm coming from a plain ol' user's POV, so if it's not in stable it's not available 8-)
Luckily not everyone has that attitude, or things never would get into stable :)
Point well taken on users contributing back, I am certainly willing to do so within my capabilities, and where I've seen people offering to document the issues I'm struggling with, I've already been offering to help out as my understanding solidifies. Maybe one day I'll be capable of testing beta stuff - right now I'm just getting my feet wet.
Make sure you use www.koha-community.org, that is the official and maintained site.
I'll certainly make that my starting point, but I'm finding all kinds of useful stuff scattered all over the interwebs - much that was written even for v2.x is useful for someone just trying to wrap their head around basic concepts. There doesn't seem to be as much content depth yet to the v3-specific information. For example, I found this juicy item here: http://www.pakban.net/brooke/tut/newbie.html as well as here: http://wiki.koha-community.org/wiki/Category:Documentation/newbieguide I assume the latter is more up to date? Side note - "Setting up a Development Environment" is classified as "for newbies?" When it comes to tech-level implementation details I am very aware of the fast-moving development pace - Koha's obviously a very active project! Thanks again for your (plural) contributions. . .
Chris Cormack wrote:
* hansbkk@gmail.com (hansbkk@gmail.com) wrote:
Well, I'm coming from a plain ol' user's POV, so if it's not in stable it's not available 8-)
Luckily not everyone has that attitude, or things never would get into stable :)
Equally, if no-one used stable, things would never get into stable because there'd be no point! Both are needed... let's be friends :) Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
participants (6)
-
Chris Cormack -
hansbkk＠gmail.com -
Ian Walls -
MJ Ray -
Owen Leonard -
Wagner, Jane