Tim, Kathy informs me via IRC that a wishlist bug for copy stat cats applicable to serials already exists! https://bugs.launchpad.net/evergreen/+bug/1078795
So that's good. I would still be interested in knowing whether you agree that, combined with the other features discussed, might save your staff from having to go through Holdings Maintenance at all for a typical serials receiving workflow. Lebbeous On Tue, Jan 15, 2013 at 2:19 PM, Lebbeous Fogle-Weekley < [email protected]> wrote: > Hi Tim, > > I see! Let's suppose for the moment that your staff's need to use parts > for serials could be obviated by two features. > > The first such feature, issue-level holds, reachable through the grouped > serials display, may be serviceable already. The second feature, to > display 866 (and other?) unexpandable holdings from the MFHD, still needs > to be developed. > > If that was taken care of, and if you added one more wishlist serials bug > to enable users to apply some (pre-selected?) copy stat cats at receive > time, could implementation of such features spare your staff from having to > go into Holdings Maintenance at all for the general case, and thereby > improve their workflow? > > Lebbeous > > > On Tue, Jan 15, 2013 at 11:30 AM, Tim Spindler <[email protected]>wrote: > >> Lebbeous, >> >> The grouping might work well in most instances and Kathy told me about >> this yesterday but as she points out there are issues with the 866 in the >> MFHD. For some clarification, I can explain the workflow of our libraries >> using the serials functions now: >> >> >> 1. Receive a serial in Serials Control View creating the copy at >> receiving >> 2. Go to holdings maintenance and to edit the copy record created >> 3. In editing the copy record they do two things: >> - Set 2 copy stat cats that are required >> - Select or create a part of for with the appropriate issue >> information >> >> Part of the reason for assigning a part is they have one call number (e.g >> Magazine) and a copy record with issue information underneath. They also >> want patrons to be able to place a hold on the correct issue. Given the >> display, I am seeing for grouping. This would be possible with serials >> grouping. >> >> Tim >> On Tue, Jan 15, 2013 at 11:04 AM, Lebbeous Fogle-Weekley < >> [email protected]> wrote: >> >>> Kathy, >>> >>> That's a great observation, and to answer your question, no, not >>> currently. However, I would think the development time needed to show >>> textual holdings alongside the grouped serials display would be less than >>> efforts that combine serials and parts (unless I'm missing something). >>> >>> Thanks, >>> >>> Lebbeous >>> >>> >>> On Tue, Jan 15, 2013 at 10:59 AM, Kathy Lussier <[email protected]>wrote: >>> >>>> Hi Lebbeous, >>>> >>>> I won't speak for Tim on the grouped serials display, but I have spent >>>> some time looking at the display and, overall, prefer this display over the >>>> default serials display. However, in my testing, I've found you can't >>>> display a textual holdings statement from the 866 field when using this >>>> display. Many of our libraries like to display a holdings statement that >>>> says "current two years" to give users a quick snapshot of what they have >>>> available. >>>> >>>> Is that something that can be displayed when using the grouped serials >>>> display? >>>> >>>> Thanks! >>>> Kathy >>>> >>>> Kathy Lussier >>>> Project Coordinator >>>> Massachusetts Library Network Cooperative(508) [email protected] >>>> Twitter: http://www.twitter.com/kmlussier >>>> >>>> On 1/15/2013 10:41 AM, Lebbeous Fogle-Weekley wrote: >>>> >>>> Hi Tim, >>>> >>>> In general ordered parts and parts display in the TPAC would be a >>>> very good thing, I'm sure. I am curious, though, about parts' relationship >>>> to serials. >>>> >>>> How are you making your received serials issues into parts? I'm not >>>> familiar with any way that Evergreen would do this for you without special >>>> effort. Maybe through Holdings Maintenance or some kind of scripted >>>> operation? >>>> >>>> Also, have you considered turning on the grouped serials display, >>>> which is at least more sensible than the default copy display? See the >>>> second and third screenshots of this document: >>>> http://docs.evergreen-ils.org/2.3/_displaying_issues_in_the_opac.htmlfor >>>> any example of what that would look like. >>>> >>>> Regards, >>>> >>>> Lebbeous >>>> >>>> >>>> On Tue, Jan 15, 2013 at 10:04 AM, Tim Spindler <[email protected]>wrote: >>>> >>>>> C/W MARS is looking at potential development on this function and is >>>>> looking for community comment. >>>>> >>>>> *Idea:* Ability to set parts order >>>>> >>>>> * >>>>> * >>>>> >>>>> *Description:* Parts are currently appearing in no real discernible >>>>> order. We would like to be able to define the order in which they >>>>> appear. >>>>> >>>>> * >>>>> * >>>>> >>>>> *Expected Functionality* >>>>> >>>>> · From the bibliographic record, provide a menu option on the >>>>> manage parts screen of actions for this record to set the order of parts >>>>> on >>>>> this screen. >>>>> >>>>> · A default sort order will be defined by an alpha sort of >>>>> the label_sortkey in the monograph_part table. >>>>> >>>>> · Parts will display on holdings in the TPAC and holdings >>>>> maintenance in the order defined through the manage parts screen. This >>>>> sort order will occur after sorting by organizational unit, prefix, call >>>>> number, and suffix. >>>>> >>>>> *Use Cases * >>>>> >>>>> A cataloger splits up a title “My Movie Set” into a 12 disk with its >>>>> own part assigned. The parts include and should display in the >>>>> following order. >>>>> >>>>> · Disk 1 >>>>> >>>>> · Disk 2 >>>>> >>>>> · Disk 3 >>>>> >>>>> · ... >>>>> >>>>> · Disk 8 >>>>> >>>>> · Disk 9 >>>>> >>>>> · Disk 10 >>>>> >>>>> · Disk 11 >>>>> >>>>> · Disk 12 >>>>> >>>>> Similarly, we have Woman’s Day with parts for each issue received as >>>>> well as a copy record for each issue that is holdable and would like them >>>>> to display in date order: >>>>> >>>>> · JAN 2013 >>>>> >>>>> · FEB 2013 >>>>> >>>>> · MAR 2013 >>>>> >>>>> See also Field & Stream ( >>>>> https://bark.cwmars.org/eg/opac/record/140662?fi%3Aitem_type=;query=field%20and%20stream;qtype=jtitle;locg=32;) >>>>> as an example of how it is now. >>>>> >>>>> >>>>> -- >>>>> >>>>> Tim Spindler >>>>> >>>>> Manager of Library Applications >>>>> >>>>> [email protected] >>>>> >>>>> 508-755-3323 x20 >>>>> >>>>> >>>>> C/W MARS, Inc. >>>>> >>>>> 67 Millbrook St, Suite 201 >>>>> >>>>> Worcester, MA 01606 >>>>> http://www.cwmars.org >>>>> >>>>> >>>>> >>>>> *P** Go Green - **Save a tree! Please don't print this e-mail >>>>> unless it's really necessary.* >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Lebbeous Fogle-Weekley >>>> | Software Developer >>>> | Equinox Software, Inc. / The Open Source Experts >>>> | phone: 1-877-OPEN-ILS (673-6457) >>>> | email: [email protected] >>>> | web: http://www.esilibrary.com >>>> >>>> >>>> >>> >>> >>> -- >>> Lebbeous Fogle-Weekley >>> | Software Developer >>> | Equinox Software, Inc. / The Open Source Experts >>> | phone: 1-877-OPEN-ILS (673-6457) >>> | email: [email protected] >>> | web: http://www.esilibrary.com >>> >> >> >> >> -- >> Tim Spindler >> [email protected] >> >> *P** Go Green - **Save a tree! Please don't print this e-mail unless >> it's really necessary.* >> >> >> > > > > -- > Lebbeous Fogle-Weekley > | Software Developer > | Equinox Software, Inc. / The Open Source Experts > | phone: 1-877-OPEN-ILS (673-6457) > | email: [email protected] > | web: http://www.esilibrary.com > -- Lebbeous Fogle-Weekley | Software Developer | Equinox Software, Inc. / The Open Source Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
