Onboarding and Rollout Planning (MOBIUS)

Prioritise onboarding cohorts of member libraries within the consortium, with a view to

The following intelligence for each library (rather than agency or host lms) will help with onboarding and rollout planning to meet these goals:

Size:
- catalog
  - overall size for expected ingest
  - typical weekly or monthly change +/-
- weekly transactions
  - borrowing
  - lending
- typical number of in-flight holds
- patron count
  - overall
  - active (within 3 months)
Current environment and system configuration
- hosting
  - shared (currently on a cluster with other libraries also moving to DCB)
  - mixed (currently on a cluster with other libraries not moving to DCB)
  - standalone (not in a shared hosting environment)
- systems (including system versions)
  - ILS (Sierra, Polaris, FOLIO, other)
  - Discovery System (Encore, Locate, Vega, Classic EDS, New EDS, Primo, other)
  - PAC (PolarisPAC, WebPAC, other)
Environment and system configuration at launch
- hosting (shared, mixed, standalone)
- ILS
- Discovery
- PAC
Service configurations
- uniqueness vs common (at agency and host lms level)
Operational
- operational peaks and quiet periods to avoid or be aware of for
  - patrons (eg, exam time, between terms, planned library events)
  - staff (eg, end of year turnaround, collection refresh)
- operational readiness
- capacity to support or engage with configuration testing
  - named technical / support contact at library
  - names business decision maker
Other considerations
- is a working group member?
- has a test environment?
- appetite for risk (eg, early or late adopter)
- concerns and expectations

No assumption is made as to whether the best plan for MOBIUS is to prioritise users of particular library systems or of a public or academic type.
Standalone libraries that are not migrating to FOLIO (and therefore with fewer implementation dependencies) are likely to be good candidates to onboard sooner rather than later.