Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Attendees
Not attending
Discussion items
| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
---|
1 | Check-in / updates | Information sharing and problem-solving | 5 | All | | | |
2 | Decisions | Discuss and approve proposed decisions A list of standardized tags | 15 | | | | |
3 | Test Load | When can we share the document Collaborative Workflow Testing and with whom (cohort and beyond)? Scheduling the work, especially those needing cross-FG coordination | 10 | All | Collaborative Workflow Testing Focus on migration decisions first and workflow decisions second. Migration decisions should be made by end of April. Check back on this and MVP document in April. PPC should confirm all priority 1 - set by the end of March. Can be shared with cohort. Available in the PPC folder. Confirm FGs will be using the timeline / spreadsheet for scheduling testing and cross-FG coordination.
| | - Christine Barone (Unlicensed) ask Marci about why workflows need to be completed by end of May? Are there dependencies with the project that dictate that timeframe? Please clarify.
|
4 | Topics for next week’s cohort chairs meeting | CDI: There are two model: Easy Active and Fully Flexible OCLC: Decide how to facilitate the conversation at cohort chairs meeting | 35 | All | CDI Want to get a better understanding of the pros and cons of EasyActive v. FullyFlexible, especially its impact on end users. Discovery: their understanding is that from the patron perspective, campuses can do what they currently do with the PCI and limit the data that’s visible (i.e. eliminating everything that is not full text). UCI does not limit by availability and would need to use the facet to limit the search. DFG asked ExL about the difference between EasyActive and FullyFlexible. EasyActive leaves the metadata available to search and the ability to limit by availability. Without limiting by availability, end user could experience numerous results which would be overwhelming Here is what Marci said on Basecamp: https://3.basecamp.com/3765443/buckets/15553579/messages/3398528891 "The roadmap of CDI product development is all new ALMA customers should be on EasyActive model. Fullyflexible model is a transitional model for PCI customers to move CDI, and eventually they will move to EasyActive model in the future" (Note: it is possible to move from FullyFlexible to EasyActive, but not from EasyActive to FullyFlexible) Focus should be on the impact on end users over work - unless amount of work is really tremendous How could we present this topic at SILS Chairs?
OCLC Impossible to process large packages in OCLC. Davis addressed this by adding records to the CZ Are people worried about records in the NZ that lack an OCLC #? RMFG will lead this discussion
| | - Jess Waggoner to send a couple of sentences about CDI to shape the discussion
- Elizabeth Miraglia to send a couple of sentences about CDI to shape the discussion
|
5 | PM Update | Awareness of what’s happening / coming soon in the project | 0 | Christine | Meetings: List of meetings on Basecamp Mon Mar 22: Using OCLC with Alma - UC-led meeting Thu Mar 25: Fiscal Close - UC-led meeting Thu, Apr 1: E-Resources Data Cleanup in Alma w/focus on P2E Mon, Apr 12: AFN Configuration Review (who should name that functionality, FFFG or DFG?)
| | |
6 | Homework | | | | | | |
7 | Parking Lot | | | | April: Revisit MVP and Collaborative Workflow Testing Future meeting: AEFG questions that came up were re: coordination of Analytics (cross-function?) and... how the Selector role in Alma is changing (people will care, prob fits w/ AEFG, but overloads us....)
For future meeting: CDL shared services In progress | | |
8 | | TOTAL | 70/90 | | | | |
Future agenda items