Heh, wrong link. Here's the one... https://bugs.launchpad.net/evergreen/+bug/1718225
Terran McCanna PINES Program Manager Georgia Public Library Service 1800 Century Place, Suite 150 Atlanta, GA 30345 404-235-7138 tmcca...@georgialibraries.org On Tue, Jan 23, 2018 at 2:55 PM, Terran McCanna < tmcca...@georgialibraries.org> wrote: > +1 on the expire_date - a lot of our libraries were using that in the xul > client. (Open ticket http://git.evergreen-ils.org/? > p=evergreen/pines.git;a=shortlog;h=refs/heads/rel_3_0_2_library_info_links > ) > > > > Terran McCanna > PINES Program Manager > Georgia Public Library Service > 1800 Century Place, Suite 150 > Atlanta, GA 30345 > 404-235-7138 <(404)%20235-7138> > tmcca...@georgialibraries.org > > > On Tue, Jan 23, 2018 at 2:44 PM, Boyer, Jason A <jbo...@library.in.gov> > wrote: > >> I'm basically done with https://bugs.launchpad.net/evergreen/+bug/1737540 >> but before making a potential privacy faux-pas or leaving out anything >> potentially useful I wanted to get some opinions. (My hope is that no >> library uses the whole prefix, first, middle, last, suffix anywhere, but >> prefix + last, just first, or first +middle initial might be useful) >> >> >> >> Here's what I'm planning to add to a patron object in checkout receipts: >> >> >> >> prefix >> >> first_given_name >> >> second_given_name >> >> family_name >> >> suffix >> >> barcode >> >> money_summary.total_owed >> >> money_summary.total_paid >> >> money_summary.balance_owed >> >> expire_date (can be used with ng-show to give a little reminder that your >> account will expire soon) >> >> alias >> >> has_email (a boolean for use with ng-show; "Have you signed up for our >> newsletters?" or "Have an email? Add it to your account to get >> notifications about your holds!" etc.) >> >> has_phone (same) >> >> >> >> I'm duplicating the patron_money information because there's no need for >> a separate patron and patron_money objects. In the interest of not breaking >> existing templates the patron_money object would still be in place; just >> not mentioned anywhere. I considered usrname but couldn't see a use case. >> >> >> >> Are there any strong opinions about adding more fields or removing some >> of these? I figure it's better to knock this out all at once rather than >> poking at it repeatedly with tiny changes. >> >> >> >> Jason >> >> >> >> -- >> >> Jason Boyer >> >> MIS Supervisor >> >> Indiana State Library >> >> http://library.in.gov/ >> >> >> > >