<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 10854 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 197, Issue 10<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Terminology: addition of "use restriction, not debarment"<br> (Victor Grousset/tuxayo)<br> 2. Vote: Use Vue3 for the new ERM (Electronic Resource<br> Management) module (Victor Grousset/tuxayo)<br> 3. Re: How to apply Lending Restrictions (Michael Hafen (TECH))<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 20 Apr 2022 17:04:53 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Terminology: addition of "use restriction, not<br> debarment"<br>Message-ID: <0ac43574-a4cc-620c-359b-9fdcf33b94b6@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi :)<br><br>After last dev meeting of the 6th, the following addition has been done:<br>https://wiki.koha-community.org/w/index.php?title=Terminology&action=historysubmit&diff=30449&oldid=30265<br><br>Whole page: https://wiki.koha-community.org/wiki/Terminology<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 20 Apr 2022 18:37:53 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Vote: Use Vue3 for the new ERM (Electronic<br> Resource Management) module<br>Message-ID: <bc12e6a2-d5f0-49e2-d19e-897bfeecd3dc@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi :)<br><br>At last meeting, today, it has been voted to give a go to have Vue3 JS <br>framework be used for the new ERM module.<br><br>Here is the same question to have a wider reach than only the people <br>that were able to attend.<br>So, agreed with that? Or any objections?<br><br>Let's wait a few days and if no major objection, Jonathan will be able <br>to continue the ERM module knowing Vue won't be a problem for the patch <br>acceptance in Koha.<br><br>meeting logs: http://irc.koha-community.org/koha/2022-04-20#i_2416969<br><br>Email asking for the vote and listing all the resources about the ERM <br>project <br>https://lists.koha-community.org/pipermail/koha-devel/2022-April/046998.html<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 20 Apr 2022 11:20:34 -0600<br>From: "Michael Hafen (TECH)" <michael.hafen@washk12.org><br>To: "Ms. Naveen Ali" <naveen@neduet.edu.pk><br>Cc: koha-devel@lists.koha-community.org, koha@lists.katipo.co.nz<br>Subject: Re: [Koha-devel] How to apply Lending Restrictions<br>Message-ID:<br> <CAAh7Ud=s8zVPBWaHckx5oQCvdK84H5XVCz0DxFT6ZnU1T6_30A@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>It may be a bit drastic, but if this is the only library on this Koha<br>system you could try turning each section into a branch and turning on<br>independent branches.<br>Separate branches would allow for different rules without drastically<br>increasing the number of item types, and staff would be at a certain<br>branch. Turning on independent branches would effectively restrict them to<br>their section. You could even hold the independent branches setting for a<br>bit to see if it works to have each section as a separate branch.<br><br><br>On Tue, Apr 19, 2022 at 11:15 PM Ms. Naveen Ali <naveen@neduet.edu.pk><br>wrote:<br><br>> Dear members,<br>><br>> I would like to put forward the following scenario.<br>><br>> Our library has three sections where books are loaned and they each have<br>> different policies. All library members have access to all sections.<br>><br>> I would like to implement the library policy where<br>><br>> 1. staff of one section can issue books of that section only<br>> 2. books should also be returned to the same section.<br>><br>> There is no general rule; just specific rules for each section.<br>><br>> This is what I am doing.<br>><br>> I have provided Permanent Library of all book items as the main library<br>> name and the Current Library as the section library.<br>><br>> I am trying to use the following global parameters to implement our<br>> library policies, but am not successful.<br>><br>><br>> - AllowReturnToBranch<br>><br>> Allow items to be checked in "Only at the item the library is from" (I<br>> understand this to be the current library)<br>><br>> - AutomaticItemReturn<br>><br>> Don't automatically transfer items to their home library when they are<br>> checked in. (I understand the home library to be the permanent library)<br>><br>><br>> - CircControl Use the calendar and circulation rules of "the library<br>> the item is from" (I understand this to be the current library)<br>><br>><br>><br>><br>> - HomeOrHoldingBranch<br>><br>> Use the checkout and fines rules of " the items holding library" (I<br>> understand holding library = current library and home library = permanent<br>> library)<br>><br>> *It seems that CircControl and HomeOrHoldingBranch paramter are same.<br>><br>> I also can't find how to restrict a library staff member from Setting his<br>> library to any that he wants by using the "Set Library" Option available.<br>> Also how to prevent staff from issuing books belonging to other libraries.<br>><br>><br>> *With best regards,*<br>><br>> *Naveen Ali*<br>><br>> **<br>> *ITM-JE (EAKL)*<br>> *Inst Representative for *<br>> *HEC Digital Library Resources.*<br>> *NEDUET, Karachi.*<br>><br>><br>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br><br><br>-- <br>Michael Hafen<br>Washington County School District Technology Department<br>Systems Analyst<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220420/a2a20ce8/attachment-0001.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 197, Issue 10<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>