Primo VE User Interface for Vanguard

Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Status	IN PROGRESS
Scope	IMPLEMENTATION
Description	Decide how will UC Libraries brand the 10 campus Primo VE user interface and 1 Primo VE for the NZ
Decision	See below
Owning group	Discovery FG Josephine Tan and Jess Waggoner, co-chairs
Approver	CoUL
Stakeholders	R = Discovery FG A = CoUL C = SILS WG I = Cohort, All staff (SILS News)
Decision-making process	Discovery FG will review branding options based on the experiences of recently migrated campuses, UX data, and other existing or new data about discovery system branding and best practices. CONSULT: Discovery FG will consult with UC campuses who have migrated to Primo, and other institutions as desired Discovery FG will consult with stakeholders to understand their needs (TBD) Discovery FG will gather relevant data about discovery system branding and best practices Others TBD RECOMMEND: Discovery FG will recommend how the UC Libraries should brand Primo VE REVIEW: Discovery FG will make a draft recommendation to the SILS WG. SILS WG will offer feedback. Discovery FG will make a final recommendation. APPROVE: SILS WG will approve. CoUL will make the final approval.
Priority	Mandatory before Go-live
Due date	TBD by Discovery FG

Recommendation

Reasoning

Background

The SILS Working Group was charged in phase 4 to “Consider systemwide/shared branding of the SILS and when changes should be made (i.e. before or after implementation)”. The Working Group is charging the Discovery FG with Primo VE branding.

Proposal: Discovery FG should make a recommendation on Primo VE branding for the UC Libraries based on evidence (stakeholder interviews, etc.)

Working assumptions:

SILS is the name of the overall service (includes Alma, Primo, etc.) and that doesn’t change.
Melvyl as a name/brand should be retired. CoUL has agreed to this.
It would be helpful to gather lessons learned from the 5 campuses who already migrated and made decisions about their Primo.
Alma is not in scope for branding since it’s a back-end tool.
Determining the default view (NZ view or IZ view) is not in scope for branding

Dependencies

Understand dependencies – are there any? Or can this decision be made anytime before go-live?

Questions to consider

What do we call Primo?

What does it look like (design, colors)?

Will the name/design be the same for every campus and the NZ, or will each campus make its own decisions?

What additional branding options does Primo allow for?

What accessibility factors should be considered, e.g., color contrast?

Action Log

Action/Point Person	Expected Completion Date	Notes	Status