Continuation of discussion about the future of the working group: At our last meeting, the group agreed to individually review the existing charge to determine if it still seemed appropriate or needed revision. We agreed that its tenets are broad enough for continued application, so an overhaul of charge is not needed at this time. The group also agreed that the current structure of the group continues to be relevant and workable; it seems advisable to continue to maintain some leadership and a committed core group of investigators and advisors for SUNY discovery issues. We would like to support greater transparency and communication, encouraging more involvement of any interested SUNY colleagues. To accomplish these goals, we will:
Share minutes to SLC LibGuides in a timely fashion and announce the availability of new minutes to the SUNY Basecamp;
Welcome participation in Discovery WG meetings by all, not just group members, and encourage this participation by announcing the meetings and sharing Zoom info via SUNY Basecamp, for example, on the Monday prior to the Friday meeting;
Support the idea of a SUNY Community of Practice devoted to discovery issues and be open to how new developments may shape the future of the working group.
In terms of membership, we have two members rotating off:
Erin Rushton, stepping down after serving as chair since the committee began (thank you, Erin!);
Rebecca Nous, on sabbatical until December 2020 (thank you, Rebecca, and congratulations!)
The group agreed that it would be desirable to seek additional members. We will consult the LSP Advisory Board and Jennifer Smathers, requesting outreach for two new members.
Nancy demonstrated how she has been using the info from CDI collections to find and troubleshoot records in Primo. In a nutshell, the CDI collections include a field, DB ID, that can be searched by keyword in Primo VE. To find the DB ID, search for a collection in Alma, then "Edit Collection" to view collection details, such as Provider package code (DB id). For example, Gale Academic OneFile has Provider package code (DB id) = IAO.
Collection info for Gale Academic OneFile, including DB id
106 KB
View full-sizeDownload
The DB id can be searched as keyword in Primo VE. You will likely find a lot of extraneous hits, but you can also use the Collection/Database filter to narrow results to the desired collection.
Primo VE search results for IAO, displaying Gale Academic OneFile in Collection/Database filter
158 KB
View full-sizeDownload The Collection/Database filter can be applied and locked to make it easier to focus in on these records, explore the record ID number, source record, links, etc. The searching doesn't always work, especially because of the use of merged master records in the CDI, but it can be helpful with troubleshooting a specific collection. Note: you can also find the DB id within a records CTO; search for DB_ID.
Heidi shared on Basecamp that the URL for SUNY's individual campus CDI holdings files is: http://na05.alma.exlibrisgroup.com/rep/getFile?institution_code=01SUNY_XXX&file=cdi_institutional_holding where XXX is the unique campus code. Some of the files are very large and hard to open, even after unzipping; Notepad++ seems to work.
Some campuses are receiving many more problem reports from users than they experienced with PCI.
Incorrect availability statements and/or linkage seems to be a major problem in CDI.
CDI results can be very mysterious and troubleshooting very difficult.
Amanda shared a mysterious CDI record where a seemingly unrelated contributor appears as a subject in the record for a book review; this may be related to a mistake in metadata, with headings for different works being matched inappropriately (?).
Sometimes the CDI is matching on search terms that don't appear within the record metadata but instead are included in the external full text of a book/article or in related field in authority records. The relevancy for these results often seems off, with matches within record metadata not necessarily appearing at the top of relevancy ranking. The issue of authority records is an Alma issue in addition to CDI; SUNY is addressing FAST subject heading problems (as discussed on Basecamp).
We have several tickets open with Ex Libris.
Both Alma-L and Primo-L are good sources; lots of CDI discussion, questions, suggestions.
Other Primo issues recently include general system slowness and OpenURL lag (the latter noted specifically at UBuffalo). We will document and open tickets as much as possible.
Zoom recordings for DWG The Zoom schedule for upcoming working group meetings has been moved over to UBuffalo's platform; the schedule is set through December 2020. Meetings have been automatically recorded for the past few months. The group discussed recordings and agreed that there is not generally a need for them, as long as minutes are taken, and everyone may speak more freely when not being recorded. We therefore agreed that we will generally not record our meetings unless there is a specific request to do so (for example, if a member can't attend live and would request a recording rather than simply minutes).
