The correction in Summon to index parallel titles as titles (instead of as subtitles) was welcomed; however, the resulting elimination of parallel titles in search results displays was not. In the current iteration of Summon, which parallel title appears in the catalog is solely left to chance, and whichever appears first in a bibliographic record. However, if Summon can display all other title subfields and information in search results, including subfields B, N and P, it should include parallel title information as well. The lack of parallel titles is problematic for patron search and retrieval. For example, a patron searching for “Pasqualino settebellezze” in our local catalog might think our DVD is the only available copy, since the title they searched for is not visible in our streaming video information. Summon should still display the parallel titles in search results; preferably exactly as Primo does, with an equals sign between the two parallel titles. Information encoded into bibliographic records is meant to assist patrons with search and retrieval of items, and therefore should be fully visible in search results in our catalogs.

One persistent problem we have between Summon and EBSCO is abstracts indexed as articles in Summon. Some journals index these abstracts as individual titles, which is why they get pulled into Summon as standalone full text articles, but EBSCO (which is where we have full text) does not index them at all. So not only does the openURL break, if you search for them in EBSCO you often get zero hits. Since we have so much full text in EBSCO, this accounts for a good many of our bad urls in Summon and it is frustrating and confusing for librarians and users.

Make display of all 5xx note fields the default in Summon in the Catalog Detail page, results screen and elsewhere. These fields already appear in Primo, with various labels (General note for 500, Language note for 546, Awards note for 586, Bibliography for 504, etc.). With these omitted from Summon, patrons are missing vital, helpful information from bibliographic records, such as: accessibility features for patrons with disabilities (532, 546); detailed language information--not just the languages themselves, but whether they’re for subtitles, described video, certain articles in anthologies, etc. (546); awards won for picture books, Academy Award winning movies, etc. (586); translation information (500, 546); DVD special features (500); “based on” information for movies, graphic novel or mass market adaptations, etc. (500); issues included in collections (vital for graphic novel reader continuity) (500); target audience for reading levels, content advisories, etc. (521); cast and crew of movies (511/508); dissertation information (502); open access information (506); whether bibliographies are included (504); and so on. We include this information when creating bibliographic records to be helpful to patrons; having it invisible in Summon is counterproductive.

Make display of all subfields from the 300 physical description field the default in Summon for all types of materials, in the catalog detail screen, results screens, and elsewhere. Currently, Summon only displays 300 MARC physical description information for books in search results and catalog detail pages; and even for books, only subfield “a” (pagination) is included. This means that patrons can’t see information like: number of DVDs or CDs in a set; whether movies are in black-and-white or color; playing time of DVDs or CDs; any accompanying materials like booklets with DVDs or CDs in book-and-CD sets; types and amount of illustrations; etc. This makes selection of desired materials more difficult for patrons. Please map and display subfields, including $a, $b, $c, $e, $f, $g, $3 from the 300 field.

We're delighted that we could integrate SpringShare Chat functionality into our Summon interface. However, we feel it could be improved by delaying the appearance of the chat prompt message for this functionality on screen.

As you can see from the file, a message appears asking users whether they'd like to chat to one of the Library Team - that's great! - but the speed of which it appears is almost instantaneous and often before users have had chance to look at their results.

Is there any way that you could make a fix for Summon to delay this slightly so it doesn't bombard the user straightaway, i.e. have it appear in 1-2 minutes after the search results have loaded?

This would be better for the user experience - they'll really value the message (and many users may want to use it, so that's great UX) but they'll also want to pause and take stock of what they've searched for as well before considering whether to use the chat functionality (and some may not need to use it or wish to use it at all!).

Please take information for the “Language” field in Summon and the Alma Display Services page from the 546 language note bibliographic field, instead of the 041 language codes bibliographic field. The 546 language note contains more detailed information about the languages included in a resource than the 041, including whether they’re for subtitles, described video, summaries as opposed to full articles, translations, etc. The current information in the Language display is not helpful for patrons. Not only does it not give details about how the languages appear in a resource, the displayed languages aren’t consistent with the language of the rest of the bibliographic description.