2021-01-27 ACQ/ERM FG Meeting notes

Date

Jan 27, 2021 11AM-12:30PM (may be shorter)

Zoom:

See calendar item or inquire with Chair for Zoom details.

Attendees

@Lisa Spagnolo , UC Davis (co-chair)
@Mark Hemhauser (Unlicensed) , UC Berkeley (notetaker)
@Paula Pascual , UC Irvine (timekeeper)
@Stacy McKenna , UCLA
@Sarah Sheets , UC Merced
@Carla Arbagey , UC Riverside (co-chair)
@Judy Keys , UC San Diego
@Lisa Wong , UC Santa Cruz
@Holly Eggleston (Unlicensed) , California Digital Library
@Susan Boone , UC San Francisco
@Maricel Cruz (Unlicensed) , UC Santa Barbara

Not Attending

Future agenda items

Discussion items

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions
1	Assemble	Getting situated, reviewing agenda, roles	5
2	Admin Items	Announcements Action Item Checks	5	Lisa S.
3	Updates: specifically from PPC (and other SILS groups)	Shared understanding of PPC and other SILS group activities, including what is routing to/affecting our FG.	10	Lisa S. / others	No PPC Meeting 1/22 Other groups. CDI, ILSDC, IC, etc. how to request special meetings RMFG considering access permissions for the NZ, setting parameters sandbox--premium ones come after go Live Theses and dissertations are at the Escalation group--how will things get in from eScholarship? Open Access resources are another topic being discussed beyond our group (being discussed in Public Services and will likely go to JSC) CDI--no activity from Discovery; CDL--Ex Libris proposes “Easy Active” instead of “Fully Flexible” AEFG will need to work closely with Discovery on this because of the back end and user end implications How do things connect with the CZ? Long term ExL wants to phase out Fully Flexible option		@Lisa Spagnolo will check with PPC to see how we want to get our heads around CDI Fully flexible vs easy active
4	Fiscal Close Document	Review and approve language for AEFG Fiscal Close communication.	10	All	See Fiscal Close document at https://docs.google.com/document/d/1BCK1ggY33QYAMoTF8UIiK_QvDMpxu73uCW4ddAYuVH0/edit Related question to confirm: should we expect technical freeze date to be the same for all campuses, migrating and already-Alma? AEFG may host a UC-wide session on how to extend fiscal year to reconcile payments better can open a past ledger and use fund rules to record a payment in a previous fiscal year per UCSB Technical service freeze affects Acq and Cat		@Lisa Spagnolo to ask Christine/Lena to include clarification of all campuses vs. migrating/already-Alma for technical services freeze/cutover date(s). @Lisa Spagnolo we should add more info in our document for extending the fiscal year, so everyone can back date CDL recharges in particular
5	Training placeholder	Address training-related infrastructure/ coordination, as distinct from other MVP columns / issues.	20	All	As component of MVP build-out? Possible sessions: fiscal close prep, outbound linking (needs confirmation of SFX availability		LS Review AEFG training folder identify what we need to schedule for training
6	MVP spreadsheet	Structuring continuation of testing from decision pages, shaping path for full test load / go-live phases. Finalize for PPC review on 1/29.	20	All	Continued discussion of Minimally Viable Product, and expectations for go-live (Day 1, Month 1, etc.) for consortial functionality. How to shape test load stage, and policy/practice level discussion in AEFG. See PPC spreadsheet in progress Have our sheet built out as much as possible by next Tuesday, meeting option for this Thursday at 3:30		ALL: By next meeting (1/27) Look over AEFG tab to confirm there are no gaps. Complete cells. @Lisa Spagnolo to follow up with our MVP overlap with other groups
7	Wrap-up	Identify/confirm next actions	5	All	May have a session on import profiles		@Lisa Spagnolo will touch base with Liz on this
8	Parking Lot	To save for future discussion	75/75		Circle back to Shared Vendors outcomes - from 12/9 meeting notes (https://uc-sils.atlassian.net/l/c/dFGWARAe ) Licensing discussion: Need to build out timeline, investigate what data can be exported, what we need to have in place.