[Koha] Adding new libraries (without re-inventing the wheel)
Fellow Kohaers, (Kohers?) The short request: Has anyone documented the steps necessary to add a new library into an existing koha system? The long request: We currently have 7 libraries, with multiple branches, and will be adding 2 more this year, with many more to come in the following years. I started writing up the system settings that need to be added to or updated (Libraries and Groups, Authorized lists, etc), when it occurred to me that someone might have done this before and be willing to share. Any help is appreciated! Conversely - I'm happy to share whatever documentation I put together. -- Kelly Drake HELM Project Manager ke...@flo.org | Conference calls: https://zoom.us/j/9606207016 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Long Shot - Looking for workaround suggestions for "Lost and Paid For" items
Collective wisdom, I'm guessing this is a long shot but perhaps someone out there is dealing with a similar situation. We're looking for a work around that would allow us to remove Lost and Paid for items from a patron's account while still maintaining the replacement cost, and having all other items with a Lost status remain on the patrons account. 1. have the system charge a patron the replacement fee for a lost item (which it does) 2. Allow the patron to pay for that item 3. Have that item removed from the patron account 4. Leave the replacement cost fine on the account or to put it an other way What we would like to happen when a patron pays for Lost item: 1. The patron's is charged for the item (either through the Long Overdue (Lost) process or manually) 2. The replacement fee shows on their account 3. Staff changes the item status to "Lost and Paid for" 4. The item is removed from their account... However, we want all other items, with any of the other Lost status, to remain on the patron's account. (MarkLostItemsAsReturned is set to "Do not mark") Hence the conflict. We've tried the workaround of checking in the item prior to the patron paying the fee with the idea that we could then set the item to Lost with no associated patron but then the replacement fee is forgiven. (Which is what we want to happen when a patron actual does return a lost item) (WhenLostChargeReplacementFee set to charge. If we try and clear the item from the patron's account by returning the item prior to their paying the bill, then the item is no longer lost and the replacement fee is forgiven. ) -- Kelly Drake HELM Project Manager ke...@flo.org | Conference calls: https://zoom.us/j/9606207016 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] 942 c - that alone should tell you all you need to know about this question
Thank you Joy! On Tue, Sep 4, 2018 at 12:06 PM, Joy Nelson wrote: > Kelly, > The 942c serves a couple purpose you may find useful or not depending on > your sites configuration. > 1. Searching: It assists with searches on itemtype when you have no item > attached. Typically eresources where libraries are not adding item records > to the bibs. > 2. Cataloging items. If the 942c has an itemtype the item records can > default to that itemtype automatically - one less click for catalogers. > 3. Holds: Record level (bib) holds cannot be done without the 942c as a > reference to what type it is. > 4. Searching: Facets are built partially on the 942c as itemtype > > Thanks, > Joy > > > On Tue, Sep 4, 2018 at 1:54 PM, Kelly Drake wrote: > >> Cataloging Gurus, >> >> What is the purpose of the 942 c? >> >> If we require all records to have an item record, and an item type in that >> record, what then is the purpose of the 942c? >> >> There are several places where it is noted that requiring the 942c is good >> practice, but I can't find anything on why. >> >> The Search Index section of the koha documentation lists: >> >> 942$c itemtype:w >> but I'm not sure what that means. Is the 942c included in an index? >> >> >> -- >> Kelly Drake >> HELM Project Manager >> >> ke...@flo.org | Conference calls: https://zoom.us/j/9606207016 >> ___ >> Koha mailing list http://koha-community.org >> Koha@lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > > > > -- > Joy Nelson > Vice President of Implementations > > ByWater Solutions <http://bywatersolutions.com> > Support and Consulting for Open Source Software > Phone/Fax (888)900-8944 > What is Koha? <http://bywatersolutions.com/what-is-koha/> > > -- Kelly Drake HELM Project Manager ke...@flo.org | Conference calls: https://zoom.us/j/9606207016 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] 942 c - that alone should tell you all you need to know about this question
Cataloging Gurus, What is the purpose of the 942 c? If we require all records to have an item record, and an item type in that record, what then is the purpose of the 942c? There are several places where it is noted that requiring the 942c is good practice, but I can't find anything on why. The Search Index section of the koha documentation lists: 942$c itemtype:w but I'm not sure what that means. Is the 942c included in an index? -- Kelly Drake HELM Project Manager ke...@flo.org | Conference calls: https://zoom.us/j/9606207016 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] [EXTERNAL] NCIP User Question - biblionum in 001 vs 999c
Hi Everyone! Thank you for all the input. Joy - we'll be talking! Heather - I do hope your pearls have weathered this storm Heather and Paul A - Does an ex-maritime librarian count? I used to work in the library at Mystic Seaport! Kelly On Thu, Jul 26, 2018 at 1:17 PM, Joy Nelson wrote: > Hi Kelly and Heather! > In many other ILS systems the 001 was/is indeed a field that contained a > unique value (control number). I still work with data from time to time > that has a unique id in the 001. Heather is right that in Koha the unique > id is stored in the 999$c, so you can use the 001 field for whatever you > like. Some sites put the oclc number in the 001, others just leave it > blank, or just take what comes when cataloging via z3950 (clutch your > pearls on that. :D ) > > Kelly, I have set up some sites to automatically copy the biblionumber to > the 001 tag. Yes, it duplicates the data from the 999c to the 001, but it > is done programmatically at night so no upkeep would be needed by > cataloging staff. As long as all your libraries are okay with this > configuration and don't plan to use the 001 for anything else, let us know > at ByWater and we can set this up for you. > > joy > > > > On Thu, Jul 26, 2018 at 10:01 AM, Heather Hernandez < > heather_hernan...@nps.gov> wrote: > >> Hi, Kelly-- >> >> Our records in Koha actually have different values in the 001 field based >> on the age of the record. When I first thought about this, I pretty much >> clutched my pearls and took to my fainting couch, thinking things like, >> "But the 001 should be our consistent, primary database key! Oh my stars >> and garters!!!" >> >> Then after applying a cool cloth to my forehead I got to thinking about >> how >> we used the 001 and what data was there: based on the age of the record, >> it's either an old catalog record number (which I want to keep in the >> record) or the OCLC number (which I definitely want to keep in the >> record). How do I use it? Well, to just store those numbers, and if I >> want to overlay the existing Koha record with a record that I'm exporting >> from the OCLC Connexion Client, I include a 999 $c with the Koha record >> number in that field in the OCLC record. I'm currently having some >> trouble >> with links into our catalog from our holdings in WorldCat.org, but that >> doesn't seem related--we're trying to use ISBNs or title data for that. >> >> So perhaps it might be helpful to ask how you would be using the 001 field >> and the 999 $c field, and how it's used among the other libraries. I >> don't >> have a lot of experience with using MarcEdit and such since ByWater >> supports our Koha catalog & I happily rely on them for things like this, >> but I think it would be entirely possible to export your records to >> MarcEdit, copy record numbers that you're not using to another field >> (e.g., >> 035) and copy the Koha biblionumbers to the 001, then reimport/replace the >> records. But that sounds kind of drastic to me. I also clutch my pearls >> at the thought of data being duplicated in a record, e.g., in the 999 $c >> as >> well as the 001, but I can't think of any harm that it would do in *my* >> setting--perhaps others could? Your system would also need some sort of >> configuring for ongoing cataloging, to see that the biblionumber gets >> copied into the 001. >> >> But if it were me, I'd think long and hard about if this is really >> necessary. For us, it's been absolutely fine to have the Koha >> biblionumbers in the 999 $c and an assortment of types of numbers in the >> 001--I've gotten up off my fainting couch, adjusted my pearls, and >> realized >> that it works!:) I hope that others will chime in, because I would be >> very >> interested to know about other options and possible consequences that >> might >> face us in the future since we do have such a variety of numbers in our >> 001 >> fields. >> >> I hope this helps! Best, >> h2 >> ~~ >> Heather Hernandez >> Technical Services Librarian >> San Francisco Maritime National Historical Park Research Center >> 2 Marina Blvd., Bldg. E, 3rd floor >> <https://maps.google.com/?q=2+Marina+Blvd.,+Bldg.+E,+3rd+floor&entry=gmail&source=g>, >> San Francisco, CA 94123-1284 >> 415-561-7032, heather_hernan...@nps.gov >> Library catalog: http://keys.bywatersolutions.com/ >> ___ >> Koha mailing list http
[Koha] NCIP User Question - biblionum in 001 vs 999c
Hi all, The HELM libraries of Massachusetts are new to Koha as of June, 2018. We are currently working to bring up our instance in the statewide lending system. The NCIP message from the statewide lending system is using the 001 for the biblio number but koha stores this value in the 999c The question are: 1. Has anyone developed a connector that looks in the 001? 2. Has anyone developed a system to copy the 999c value into the 001? 3. Is there another way to handle this? -- Kelly Drake HELM Project Manager ke...@flo.org | Conference calls: https://zoom.us/j/9606207016 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Not showing 505$t field (Contents) in Portugueses
FYI, we're seeing a similar situation, but in the English display. Bib records with values in the 505 _g and _t are not displaying correctly (ie same as 505 _a.) Instead the _t shows on a separate line which goes on and on forever instead of flowing from one -- to another, _g does not display. Incorrect display of _g and _t see: http://koha-test.helmlib.org/cgi-bin/koha/opac-detail.pl?biblionumber=278965&query_desc=kw%2Cwrdl%3A%202029221 Correct display _a: http://koha-test.helmlib.org/cgi-bin/koha/opac-detail.pl?biblionumber=684 Let us know if you found anything! Kelly Drake HELM On Fri, Feb 2, 2018 at 9:25 AM, camilabezerra wrote: > Hi Katrin, > > I am not using plack. Any other ideas? > > > > -- > Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html > ___ > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > -- Kelly Drake HELM Project Manager ke...@flo.org | 617.442.2384 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Course Reserves in Consortia | Visibility and Best Practices
Hello, We are wondering about the visibility to patrons of Courses in Course Reserves in a Consortium in 2 separate scenarios. 1. If a patron is logged into their branch and they select "Course Reserves" do they only see the Courses of their own branch? 2. Additionally, if the patron uses a "scoped" URL that indicates a particular branch, and they are not logged in, when they select "Course Reserves" do they only see the Courses of that branch? Additionally, does anyone who uses Course Reserves in a Consortia have any best practices and maintenance policies that they would be willing to share? Any and all insights are appreciated! -- Kelly Drake HELM Project Manager ke...@flo.org | 617.442.2384 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Multiple but different URLs for the same item
Thanks Indranil! That sounds like an interesting possibility. Kelly On Thu, Dec 28, 2017 at 1:07 PM, Indranil Das Gupta wrote: > Hi Kelly, > > Your users / patrons would be logged in into their own accounts via the > OPAC to access these authenticated resources? > > If so (assuming I understood your use-case correctly) then how about > adding a bit of jQuery to OpacUserJS sys pref which does the following: > > 1) look up the branch code from the class of the body tag which is in form > of "branch-" e.g. "branch-IDSK" where 'IDSK' is the branch > code. > > 2) and then latches on the the span class name - online_resources and > toggles the visibility of the URL of the resource as per #1 above (both for > results and the details page) > > hope this helps > > cheers, > -indranil > > > Indranil Das Gupta > L2C2 Technologies > > Phone : +91-98300-20971 <+91%2098300%2020971> > WWW : http://www.l2c2.co.in > Blog: http://blog.l2c2.co.in > IRC : indradg on irc://irc.freenode.net > Twitter : indradg > > On Fri, Dec 29, 2017 at 12:23 AM, Kelly Drake wrote: > >> Hi all, >> >> We are a consortia of 7 academic libraries just setting up on Koha and >> have >> a question on how folks are handling items that have multiple, but >> different URLS for the same item. >> >> For example. All the libraries subscribe to one journal, The Chronicle of >> Higher Education, but since this is a paid subscription with >> authenticating >> links, the users of each library need to select a different link in order >> to be able to authenticate. >> >> From previous experience we know that these different links need to be >> extremely obvious! >> >> Currently it looks as if Koha offers two options. >> 1. 856 links that can be highlighted, or called out in various ways >> through >> modification of the template. >> 2. Adding Item Types for each link - although in this case the URL itself >> is displayed (rather than any display text) >> >> Does any one have examples of how they are handling this? and making the >> links, and who should click where, really obvious? >> >> All input is greatly appreciated! >> >> Kelly Drake >> >> Kelly Drake >> HELM Project Manager >> >> ke...@flo.org | 617.442.2384 >> ___ >> Koha mailing list http://koha-community.org >> Koha@lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > > ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Multiple but different URLs for the same item
Hi all, We are a consortia of 7 academic libraries just setting up on Koha and have a question on how folks are handling items that have multiple, but different URLS for the same item. For example. All the libraries subscribe to one journal, The Chronicle of Higher Education, but since this is a paid subscription with authenticating links, the users of each library need to select a different link in order to be able to authenticate. From previous experience we know that these different links need to be extremely obvious! Currently it looks as if Koha offers two options. 1. 856 links that can be highlighted, or called out in various ways through modification of the template. 2. Adding Item Types for each link - although in this case the URL itself is displayed (rather than any display text) Does any one have examples of how they are handling this? and making the links, and who should click where, really obvious? All input is greatly appreciated! Kelly Drake Kelly Drake HELM Project Manager ke...@flo.org | 617.442.2384 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
