That's what I suspected. In this situation, the serials stuff isn't doing anything more than dumping the existing text strings that describe your holdings. That code has changed a lot since I last poked at it, but I suspect that changing the way text holdings records are displayed so that they're nicer will require patching the code in the serials module.
- David On Fri, May 27, 2011 at 12:31, Tara Robertson < [email protected]> wrote: > Hey David--thanks! > > I don't think I explained things clearly enough. This is an issue with > summary holdings that we (actually the amazing Mark Bucholtz) migrated > into Evergreen. > > Here's how Dwell displays in Horizon: > > http://jupiter.eciad.ca/ipac20/ipac.jsp?session=1306X1347H614.1223046&profile=lib&uri=link=3100006~!294353~!3100001~!3100002&aspect=subtab43&menu=search&ri=1&source=~!emily&term=Dwell.&index=ALTITLE > > Each bit of the run displays on separate lines. There are no MFHD > statements for what was migrated from Horizon. > > Maybe Mark can chime in with what he's tried to make the holdings summary > more readable. > > tara > > > > On Fri, May 27, 2011 at 5:29 AM, David Fiander <[email protected]> wrote: > >> Your first example, "Dwell", is odd. It should be compressed down to >> >> v. 3 no. 8 (Sep 2003), v. 3 no. 9 (Oct 2003) missing, v. 4 no. 2 (Nov/Dec >> 2003) - v. 5 no. 5 (Apr/May 2005), v. 5 no. 6 (Jun 2005) missing, v. 5 no. >> 7 (Jul/Aug 2005) - v. 6 no. 5 (May 2006), v. 6 no. 6 (Jun 2006) missing, v. >> 6 no. 7 (July 2006) - v. 10 no. 10 (October 2010), v. 11 no. 1 (November >> 2010) - v. 11 no. 6 (May 2011) >> >> at least. Without seeing the MFHD statements for this journal, I can't >> tell if there's a problem with the display code, or if that's just what was >> migrated from the old catalogue. >> >> Are the issues marked as "missing" issues that you might have received in >> the past but are now gone, or did you never have them? Either way, if you >> have given up on them, you could remove the missing issues, simplifying >> again to a list that describes just what you have: >> >> v. 3 no. 8 (Sep 2003), v. 4 no. 2 (Nov/Dec 2003) - v. 5 no. 5 (Apr/May >> 2005), v. 5 no. 7 (Jul/Aug 2005) - v. 6 no. 5 (May 2006), v. 6 no. 7 (July >> 2006) - v. 10 no. 10 (October 2010), v. 11 no. 1 (November 2010) - v. 11 >> no. 6 (May 2011) >> >> Unfortunately, the NISO standard for displaying serials holdings is VERY >> detailed and requires close reading to figure out if the particular issue >> you want is available or not. On the plus side, at least it's possible to >> tell from the catalogue holdings statement whether it's worth going to the >> stacks or not. MPOW uses an older standard, which only indicates that a >> volume in incomplete, so one doesn't know if the issue one wants is >> available without actually going into the stacks. >> >> On Thu, May 26, 2011 at 15:39, Tara Robertson < >> [email protected]> wrote: >> >>> I'm wondering if any other libraries who are using serials, or have >>> migrated serials holdings into Evergreen have figured out a way to make the >>> holdings summary look OK. >>> >>> We are now on Sitka (yay!) and this would help us out a lot. >>> >>> Here's two examples in our catalogue, as you can see it's pretty hard to >>> read: >>> >>> >>> http://catalogue.bclibraries.ca/opac/en-CA/skin/BVAVSA/xml/rdetail.xml?r=101107854&ol=610&t=dwell&tp=title&l=610&d=2&hc=7&rt=keyword >>> >>> >>> http://catalogue.bclibraries.ca/opac/en-CA/skin/BVAVSA/xml/rdetail.xml?r=103448772&ol=610&t=artforum&tp=title&l=610&d=2&hc=3&rt=keyword >>> >>> BTW--thanks KCLS for sharing your PAC skin, and James Fournie (Sitka) for >>> doing a whole bunch of work so that we can pilot it. >>> >>> Cheers, >>> Tara >>> Emily Carr University of Art + Design >>> >>> >>> On Thu, Mar 17, 2011 at 6:54 AM, Mark Bucholtz (Project Sitka) < >>> [email protected]> wrote: >>> >>>> Hi There >>>> >>>> When you receive issues in Serials the software builds the subscription >>>> summary screen by adding the new volume information from left to right with >>>> no line breaks (see attached screenprint). If there are lots of entries it >>>> becomes difficult to read. >>>> >>>> Is there any way to get the volume information to display on separate >>>> lines when there are breaks in the subscription run? >>>> >>>> Thanks in advance. >>>> >>>> Mark Bucholtz >>>> >>>> >>> >> >
