Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

, 10am-11:30am

...

Discussion items

DISCOVERY VISION: We strive to design and implement the best possible discovery and delivery experience for our end users using data-driven decision making. We envision a network zone experience that will allow users to discover library materials across UC collections without sacrificing relevant results. As such, the default search and results interface should prioritize the success of typical users while providing additional functionality for more advanced users.

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Updates from other SILS groups

Share relevant items

10 min

Josephine

Sarah

EUOS: they will be making a list of different places UC-eLinks are placed in preparation for our decision of what UC-eLinks will be renamed.

Checking in with EUOS and others for clarification on using this in the interface proper.

  • Our timeline does have a line for this kind of work

  • we’ll want to consider where to put this in context of the interface, considering navigation within Primo and out to other pages, and the process for configuration

2

Configuration Recommendations Workbook

Decide which recommendations are ready for sign off

30 min

All

Configuration Recommendations Workbook

Discussion highlights:

Label for location: not clear what this means to users. Once option is to have three or five showing, so it becomes immediately clear to a user what we mean by that. Could also change facet name, but want to avoid long descriptive label. Preference for the first option/approach for these facets we choose to include.

Facets configurable by search profile slot. Facet group names will need to be the same, but you can choose to configure what shows differently across search profiles/slots.

Library Facet: some may choose not to display this. If you do, you might want consider what to label it, and how to order it in the display in the context of other facets like, UC Libraries and Location.

Discussed usefulness of facets Location and Library. We have some first impressions, but will test on this during this phase.

Rename “Available Services,” to something more clear, like, “Check availability.” The current workbook has this issue slightly misidentified/confused with another “May be Available” holdings/item language, elsewhere.

Relabel “Resource Sharing” to Request through Interlibrary Loan. Brings up context of the other types of request links. Consult with the ILL and Fulfillment group. They’ve done some thinking around this and one of the CDL developers created a “Request Lite” version that would help there not be more than one form for users.

ILL subgroup recommends using “enable without login” configuration option to that ILL links before people have been signed in. The alternative is, people have to be logged in/authenticated before seeing the ILL link appears. This will appear to all user groups, even those who do not have ILL permissions. Consider ease of use for main users vs. a bit of confusion for smaller groups like community users. Consider adding helpful language under this option (UCSC includes info about ILL service times) could add a bit about audience here if desired.

MARC fields configuration decisions: LA/Berkeley working on some documentation from their local conversations, and will share. Irvine has similar, really helpful documentation for their current, production environment.

Recommendations:

  • Remove Other Libraries

  • During test phase,

  • Use facet data drawn from Alma-already campus to help inform thinking, and review these during test phase.

  • Discovery FG may make some recommendations for Go-Live that harmonize, as well as others that end up reading like, “be sure to consider facet label order and name in context of other facets ____ and ____ .”

Jess Waggoner will add configuration decisions to our chart, and will start a new document to track our shared knowledge discussions.

3

Testing Plan

What can we provide as an answer

20 min

All

Test Phase Timeline

4

Boosting Planning

Discuss plans for boosting

15 min

All

Some testing scripts - could share information amongst ourselves, to help others in their own searching/configuration. Might include things like, find a local collection, find local holdings of books, etc. Will help locals campuses as they check whether their institution boosting levels are set to liking.

Jess Waggoner will start a document

5

WorldCat Testing Planning

Discuss which campus will test what

15 min

All

  1. WorldCat in search profile scope: UCSD, UCSC, SF

  2. WorldCat only in Advanced search: UCB, UCSB

  3. WorldCat icon in results facet (Northwestern model seems to be 1 +3 SF may do this)

Different campuses focus on different configuration options, bring this together and review. ILL/Fulfillment invested in this - include in discussions and testing.

Campusus decide and communicate which of these approaches you plan to set up for test phase.

6

Homework

Prepares team for next meeting

All

7

Parking Lot/Q&A

Save these issues for future discussion & comments

 

 

  • FRBR/Boosting

  • Main Menu (pull up config workbooks)

  • Facets

  • Libguides

  • Testing plan

  • Delivery and Fulfillment

  • Minimum Viable Product

  • WorldCat

  • Ebook ILL lending as it relates to discovery and limiting to availability.

  • UC-eLinks (re)naming

  • What will help links be called and where will they be in the interface?

Questions/comments:

  • SFX Journal Search Tool (moved notes to UC eLinks section)

  • Third party integrations

    • Browzine & LibKey

  • Ebook ILL lending: problematic with Melvyl; keep in mind to test in Test phase

...