<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On 30/04/18 11:55, FNPS Library wrote:<br>
    <blockquote type="cite"
cite="mid:CAE-W8Vb260A1Yqocs1BSDP9qd9c7O_63pE=9xON8-kSA55D1=A@mail.gmail.com">
      <div dir="ltr">
        <div>Hi Bob,</div>
        <div>Thanks for the tip about sort 1/sort 2 categories. Looks
          like it does exactly what I want, but I'll be duplicating
          the info in the 'added attribute' parameter only so it shows
          up in the patron info sidebar at checkout.</div>
      </div>
    </blockquote>
    That's an insight, thanks Michael. We have a request afoot to
    display those parameters at a couple of places at Circulation. Your
    method could make that unnecessary. I'll check it out.<br>
    <blockquote type="cite"
cite="mid:CAE-W8Vb260A1Yqocs1BSDP9qd9c7O_63pE=9xON8-kSA55D1=A@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>I'm having an issue with editing patron information and
          creating new patrons (save button isn't responding), so I'll
          test it out once I've worked out how to save and modify my
          patrons. (patron list is populated because csv batch import
          worked fine, it's individual records I can't create or
          modify).</div>
        <div><br>
        </div>
        <div>I have submitted details of the issue to the koha-community
          bugzilla page, so I'll hopefully get some answers soon.</div>
      </div>
    </blockquote>
    I've not come across that one. Do you have any javascript in your
    intranetuserjs sys pref that might be misfiring? The user has
    permissions for that module?<br>
    <br>
    OK, I found your <a moz-do-not-send="true"
      href="https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20680">bz</a>.
    Sounds like a bug but if so others should have come across it by
    now. I have to move on. Let's see what response you get.<br>
    <br>
    Cheers,<br>
    Bob <br>
    <blockquote type="cite"
cite="mid:CAE-W8Vb260A1Yqocs1BSDP9qd9c7O_63pE=9xON8-kSA55D1=A@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Thanks for the advice,</div>
        <div><br>
        </div>
        <div>Cheers,</div>
        <div>Michael.<br>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On 28 April 2018 at 20:00, <span
              dir="ltr"><<a
                href="mailto:koha-oz-request@lists.koha-community.org"
                target="_blank" moz-do-not-send="true">koha-oz-request@lists.koha-community.org</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">Send
              Koha-oz mailing list submissions to<br>
                      <a href="mailto:koha-oz@lists.koha-community.org"
                moz-do-not-send="true">koha-oz@lists.koha-community.<wbr>org</a><br>
              <br>
              To subscribe or unsubscribe via the World Wide Web, visit<br>
                      <a
                href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-oz"
                target="_blank" rel="noreferrer" moz-do-not-send="true">http://lists.koha-community.<wbr>org/cgi-bin/mailman/listinfo/<wbr>koha-oz</a><br>
              or, via email, send a message with subject or body 'help'
              to<br>
                      <a
                href="mailto:koha-oz-request@lists.koha-community.org"
                moz-do-not-send="true">koha-oz-request@lists.koha-<wbr>community.org</a><br>
              <br>
              You can reach the person managing the list at<br>
                      <a
                href="mailto:koha-oz-owner@lists.koha-community.org"
                moz-do-not-send="true">koha-oz-owner@lists.koha-<wbr>community.org</a><br>
              <br>
              When replying, please edit your Subject line so it is more
              specific<br>
              than "Re: Contents of Koha-oz digest..."<br>
              <br>
              <br>
              Today's Topics:<br>
              <br>
                 1. Re: Koha in schools: group patrons by class? (Bob
              Birchall)<br>
              <br>
              <br>
              ------------------------------<wbr>------------------------------<wbr>----------<br>
              <br>
              Message: 1<br>
              Date: Sat, 28 Apr 2018 17:10:58 +1000<br>
              From: Bob Birchall <<a href="mailto:bob@calyx.net.au"
                moz-do-not-send="true">bob@calyx.net.au</a>><br>
              To: <a href="mailto:koha-oz@lists.koha-community.org"
                moz-do-not-send="true">koha-oz@lists.koha-community.<wbr>org</a><br>
              Subject: Re: [Koha-oz] Koha in schools: group patrons by
              class?<br>
              Message-ID: <<a
                href="mailto:54f814df-86b4-184e-54e0-34c77343b3d6@calyx.net.au"
                moz-do-not-send="true">54f814df-86b4-184e-54e0-<wbr>34c77343b3d6@calyx.net.au</a>><br>
              Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
              <br>
              Hi Michael,<br>
              I didn't see that you received a response to this post. If
              you did but I <br>
              missed it, I'm sorry.<br>
              <br>
              Defining an additional patron attribute is a valid way of
              achieving your <br>
              goal. However if it is the only additional attribute you
              will have, <br>
              there are times it might feel cumbersome. For example,
              when you need to <br>
              use the parameter in a report, you'll need to join the
              additional <br>
              attributes table - by no means a game breaker, but a
              consideration.<br>
              <br>
              An alternative approach that some schools have taken is to
              use the Sort1 <br>
              or Sort2 fields in the borrowers table. You can define
              your classes as a <br>
              set of Authorised Values for the chosen field if you wish.
              And if you <br>
              feel the need, you can re-name the field using a little
              js.<br>
              <br>
              I hope this helps, despite the delay.<br>
              Bob Birchall<br>
              Calyx<br>
              <br>
              On 21/03/18 11:02, FNPS Library wrote:<br>
              > Hello everyone,<br>
              ><br>
              > I work in a primary school library in Melbourne, I'm
              looking at <br>
              > transitioning our library system from Oliver Junior
              to Koha. We have <br>
              > set up a test system to play with settings and so on,
              and I was hoping <br>
              > someone might have an idea for this.<br>
              > I want to be able to group students by class (e.g.
              56A, 56B, 56C, <br>
              > etc.) for the purpose of finding them for checkout,
              and for grouping <br>
              > overdue notices.<br>
              ><br>
              > I thought of using a custom patron parameter, but I
              was wondering if <br>
              > anybody had a more elegant solution available.<br>
              ><br>
              > Thank you,<br>
              ><br>
              > Kind regards,<br>
              ><br>
              > Michael Barry.<br>
              ><br>
              ><br>
              > ______________________________<wbr>_________________<br>
              > Koha-oz mailing list<br>
              > <a href="mailto:Koha-oz@lists.koha-community.org"
                moz-do-not-send="true">Koha-oz@lists.koha-community.<wbr>org</a><br>
              > <a
                href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-oz"
                target="_blank" rel="noreferrer" moz-do-not-send="true">http://lists.koha-community.<wbr>org/cgi-bin/mailman/listinfo/<wbr>koha-oz</a><br>
              <br>
              -------------- next part --------------<br>
              An HTML attachment was scrubbed...<br>
              URL: <<a
href="http://lists.koha-community.org/pipermail/koha-oz/attachments/20180428/cd2362c3/attachment-0001.html"
                target="_blank" rel="noreferrer" moz-do-not-send="true">http://lists.koha-community.<wbr>org/pipermail/koha-oz/<wbr>attachments/20180428/cd2362c3/<wbr>attachment-0001.html</a>><br>
              <br>
              ------------------------------<br>
              <br>
              ______________________________<wbr>_________________<br>
              Koha-oz mailing list<br>
              <a href="mailto:Koha-oz@lists.koha-community.org"
                moz-do-not-send="true">Koha-oz@lists.koha-community.<wbr>org</a><br>
              <a
                href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-oz"
                target="_blank" rel="noreferrer" moz-do-not-send="true">http://lists.koha-community.<wbr>org/cgi-bin/mailman/listinfo/<wbr>koha-oz</a><br>
              <br>
              <br>
              End of Koha-oz Digest, Vol 56, Issue 2<br>
              ******************************<wbr>********<br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Koha-oz mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-oz@lists.koha-community.org">Koha-oz@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-oz">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-oz</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>