Some respondents suggested a Primo ‘audit’. Cmte. not planning to take a comprehensive audit on at present. A possible solution would be listing people who are willing to help other campuses on the wiki. This, along with improved documentation, could help the campuses that struggle to keep up to date with Primo release features.
Campuses other than the main testing group may begin to critique Primo VE sometime in March/April 2021. Precise timeline TBD based on decisions from brandon dudley (Unlicensed) & David Walker and further information from Ex Libris.
Each VE instance will be parallel to current production Primo/PBO. Until it is ready, it will be visible only to staff for testing in parallel with the existing Primo. When the migration is complete and fully tested, traffic will be directed to the new Primo VE. Primo VE is deployed on dedicated servers within the Alma platform.
Ex Libris has some migration benchmarks/tests that they will ask us to perform. Further details and the extent of ExL-directed testing is forthcoming.
SJSU has this in production, contact Christine Holmes for details. See ‘Follow up to HathiTrust ETAS discussion.pdf’ for examples.
If consortial membership is obtained, DFC will put up documentation on the wiki about implementing the UMN Libraries HT module.
Action items
Decisions
Primo VE Analysis Area Shepherds have been determined. Speed/load time - Paul Hottinger; Back end usability - Christine Holmes; Front end usability - Cathy Outten; Results/relevancy - Andrew Carlos