Re: [OPEN-ILS-GENERAL] Evergreen 2.3 alpha around the corner
Bibliomation would want 1,3, and 4. There may be other wishes, but I wanted to add a vote for Janet's items. Mary -Original Message- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Janet Schrader Sent: Friday, June 15, 2012 12:05 AM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Evergreen 2.3 alpha around the corner I believe that CW/MARS libraries would like: 1.) Public notes display. This was a feature we lost when we migrated to EG. 2.) Bib records with no items display in PAC. 3.) Cross-references are another feature we'd like to see in PAC. 4.) Ability to scope 590 and 690 fields for local notes and subject headings using subfield '9' as the 856 fields do. Janet Janet Schrader Bibliographic Services Supervisor C/W MARS Inc. 67 Millbrook Street Suite 201 Worcester, MA 01606 tel: 508-755-3323 ext. 25 fax: 508-787-7801 jschra...@cwmars.org From: open-ils-general-boun...@list.georgialibraries.org [open-ils-general-boun...@list.georgialibraries.org] on behalf of Kathy Lussier [kluss...@masslnc.org] Sent: Thursday, June 14, 2012 10:21 PM To: Evergreen Discussion Group; Bill Erickson Cc: Evergreen Development Discussion List; Evergreen General Discussion List Subject: Re: [OPEN-ILS-GENERAL] Evergreen 2.3 alpha around the corner Hi Bill, Do you have opinions on these items or think some items are missing? Let your voices be heard. It's safe to say this will be the shortest feature development cycle of any major Evergreen release. Within the next month or so, we'll have a pretty good sense of everything that's making the cut. In six weeks, we hit the feature freeze. Now is the time to effect change. Thanks for asking the question! Since jspac is scheduled to be deprecated as of 2.3, I think it might be useful to identify which of those unsponsored pending features from http://open-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:planrev= 1339016264 should be addressed before jspac is phased out. There are two that jump out at me: * Display of public copy notes - it might seem to be minor, but public notes aren't really public if the public can't see them. * Check for password strength at login and force change if password is weak. There are several other items on that list that I would like to see eventually incorporated into tpac, but the above two features are basic things I think should be available before tpac becomes the default catalog for Evergreen. Also, I didn't see the new xulrunner branch (https://bugs.launchpad.net/evergreen/+bug/942134) in the links you sent out. Is that something that might be tested and committed in time for 2.3? Thanks! Kathy =
[OPEN-ILS-GENERAL] Acquisitions claiming set-up
Hi all, I'm hoping someone can help me get my mind around how to set up claims for acquisitions. There are so many pieces and I'm not sure I understand what part does what. Does anyone have an example they'd be willing to share of the following: claim policy, claim type, claim event, and claim policy action, and how they are implemented? Thank you, Mary
Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen 2.3 alpha around the corner
On Thu, Jun 14, 2012 at 10:21:59PM -0400, Kathy Lussier wrote: Hi Bill, Do you have opinions on these items or think some items are missing? Let your voices be heard. It's safe to say this will be the shortest feature development cycle of any major Evergreen release. Within the next month or so, we'll have a pretty good sense of everything that's making the cut. In six weeks, we hit the feature freeze. Now is the time to effect change. Thanks for asking the question! Since jspac is scheduled to be deprecated as of 2.3, I think it might be useful to identify which of those unsponsored pending features from http://open-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:planrev=1339016264 should be addressed before jspac is phased out. There are two that jump out at me: * Display of public copy notes - it might seem to be minor, but public notes aren't really public if the public can't see them. Copy notes could easily be displayed in search results - we're already grabbing them, just not displaying them - but as search results and record details currently use different methods to retrieve essentially the same bib record / call number / copy information (unapi SQL function for search results, json_query Perl method for record details), we would need to add the 'acpn' (copy note) field to the json_query in OpenILS::Application::AppUtils::basic_opac_copy_query(). Shouldn't be very hard to go this route. At some point, though, we should settle on one really complex way of grabbing this info, rather than having two really complex ways. I had been working towards that with unapi, but ran out of time to accomplish that for the 2.2 deadline.
Re: [OPEN-ILS-GENERAL] Evergreen 2.3 alpha around the corner
* Display of public copy notes - it might seem to be minor, but public notes aren't really public if the public can't see them. Public copy notes are important if you use these for donor information and it's the equivalent of the bookplate. Always good to show appreciation to donors! The lack of scoped call number browsing is also a real issue here. (See https://bugs.launchpad.net/evergreen/+bug/973618) The other things we really want are the group formats and editions for both searching and holds, more advanced limiters including local copy locations. I also greatly prefer the way facets display in the JSPac, which has a more structured approach to grouping, for example, the Subject facets together. I also like the way the JSPac lists the top five items for each facet, with a More button to display the full listing. TPac lists the first ten, with no option to see the full list. (If there's a way to change this in TPac, please let me know!) -- Elizabeth Thomsen, Member Services Manager NOBLE: North of Boston Library Exchange 26 Cherry Hill Drive Danvers MA 01923 E-mail: e...@noblenet.org
Re: [OPEN-ILS-GENERAL] Missing on holds shelf items
I believe in master (and I think 2.2) this has been resolved. Said items should still appear on the hold shelf (and the expired view thereof) until checked in again. Thomas Berezansky Merrimack Valley Library Consortium Quoting George Tuttle gtut...@prlib.org: Does anyone else have or had the problem of items with the status of on holds shelf but the hold is canceled, the item can't be found, and there is really no clue where the item might be? George Tuttle Computer Services Librarian Piedmont Regional Library System 770-867-2762 x113 770-891-0654 (cell) 770-867-7483 (fax) mailto:gtut...@prlib.org gtut...@prlib.org
Re: [OPEN-ILS-GENERAL] Evergreen 2.3 alpha around the corner
On Thu, Jun 14, 2012 at 10:21:59PM -0400, Kathy Lussier wrote: Hi Bill, Do you have opinions on these items or think some items are missing? Let your voices be heard. It's safe to say this will be the shortest feature development cycle of any major Evergreen release. Within the next month or so, we'll have a pretty good sense of everything that's making the cut. In six weeks, we hit the feature freeze. Now is the time to effect change. Thanks for asking the question! Since jspac is scheduled to be deprecated as of 2.3, I think it might be useful to identify which of those unsponsored pending features from http://open-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:planrev=1339016264 should be addressed before jspac is phased out. There are two that jump out at me: * Display of public copy notes - it might seem to be minor, but public notes aren't really public if the public can't see them. * Check for password strength at login and force change if password is weak. Good suggestions. I didn't find any matching LP tickets for these. (Perhaps I'm just missing them?). Kathy (or anyone), would you mind opening a couple of LP tickets? There are several other items on that list that I would like to see eventually incorporated into tpac, but the above two features are basic things I think should be available before tpac becomes the default catalog for Evergreen. Also, I didn't see the new xulrunner branch (https://bugs.launchpad.net/evergreen/+bug/942134) in the links you sent out. Is that something that might be tested and committed in time for 2.3? I've updated this ticket to target the 2.3 series. I have plans to poke at this some and I see some testing has already occurred. Clearly, this is a change that would benefit more than most from a diverse groups of testers. -b -- Bill Erickson | Senior Software Developer | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 877-OPEN-ILS (673-6457) | email: erick...@esilibrary.com | web: http://esilibrary.com
[OPEN-ILS-GENERAL] This week in development
Evergreen 2.2.0 is released! This is the long-awaited, first stable release of the 2.2 series with the new Template Toolkit-based OPAC and all the other new features. 2.1.2 RC2 and 2.0.12 were also released. All of this week's releases contained security fixes, so sites should upgrade to the latest release in their series with due haste, or see here for instructions on applying the security fixes without going through the whole upgrade process: http://evergreen-ils.org/blog/?p=776 Dan Scott has been selected as a Fedora Linux packager. He'll be adding and updating several of the standard Perl modules that Evergreen relies on to Fedora. This means that sites using Fedora Linux should see the Evergreen installation process get easier. The same improvements should eventually reach Red Hat Enterprise Linux as well. Sites that have recently brought the Template Toolkit OPAC online are bringing attention to bugs that affect them, and the developer community is responding to the call to work out solutions. This is how things get better and better! Some developers have also been working on new SIP-based features for Evergreen, specifically detailed display of user fines and credit card payments via devices that support that. Work has also gone into improvements in: - hold targeting - MARC Record Batch Import/Export (Vandelay to the developers) - command line tools for updating authority records - more! Apologies to anyone whose contributions I have neglected to mention. I don't exactly intend these emails to be comprehensive of all development contributions for the past week, but I just want to give a broad audience an idea of what the developer community is focusing on. Thanks! -- Lebbeous Fogle-Weekley | Software Developer | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: lebbe...@esilibrary.com | web: http://www.esilibrary.com
