Attendees
Corrie Hutchinson (Unlicensed)Noah BrubakerLucy Harrison Joe Hkaplanian Margaret Youngberg Stephanie Chinn Darsi Rueda Lloyd Chittenden Elena OMalley
Discussion items
| Time | Item | Who | Notes |
|---|
| 30 mins | Stanford project update | Darsi | - A consortium of multiple libraries coming together on a single tenant
- Libraries are now on one FOLIO system; previously on different ILS
- Went with single tenant to allow Stanford patrons to use/borrow from any Stanford library
- Some internal issues with autonomy between libraries that now share a single tenant
- A real issue is that FOLIO can only send one notice text from a single email address ; doesn't work well in a single tenant with multiple libraries
- Current compromise : sends a list of all libraries and their contacts at the bottom of each notice
- Jira ticket to address issue:
UXPROD-2156
-
Getting issue details...
STATUS
- Overall, going well
- Question/discussion about control of libraries' data, including inventory
- Stanford had separate bibs for each library prior to FOLIO and decided to continue practice for migration
- Users are not affiliated with a single library, but each library can create user records for guests, etc.
- Has special loan policies to address the various patron groups
- Did Stanford consolidate circulation rules?
- Tried to consolidate loan periods where reasonable
- Not able to come to an agreement on replacement costs and practices among the libraries (each requires it's own circ rule)
- Was hoping that 'actual cost' would address the issue, but it's not implemented in a way that works for Stanford
- Stanford uses Blacklight for discovery
- Does not require login
- Single interface for all of Stanford; facet for each library location
- Med Library has it's own discovery environment
- https://searchworks.stanford.edu/
- How are you handling e-resources?
- Complicated because of historical practices, view permissions on resources between libraries, etc.
- Article data coming in via EDS
- How to have a union catalog, but control who sees what?
- Five Colleges has separate discovery views; can see e-resources available only to one library, but are prevented from access
- Stanford has 4 acquisition units
- 2 of them integrate with campus systems to pay invoices
- Libraries are separate organizational units; no 'acquisitions unit' for inventory unfortunately
|
| 15 mins | What enhanced consortial support will be in Poppy? |
| Harry: v.1 major portions will be in Poppy. But recommends libraries don’t adopt it until later in the summer, can test in Poppy. EBSCO setting up a test environment with a large number of tenants, doing performance testing. Still need to test, tune, enhance for May, then get feedback and fix everything. Will be available in Poppy: - User management
- Central Consortia app
- Controlled vocabularies
- Lists app: EBSCO is ready to release it in Poppy, waiting for community approval. Will not include statistical gathering/analytical reports across tenants (yet). Need to figure out how to control access to Acq, Circ, User data across tenants. What can a central admin unit see of other consortia members?
- Authority record sharing (amongst tenants)
- OpenRS isn’t tied to a particular FOLIO release. EBSCO is setting up builds, doing releases, so it will be available to be used with Poppy.
- DI and DE working in Consortial setting
Some features might be useful for single tenants too, but focusing on multi-tenant All of this will be delivered turned off, will need to be turned on in configuration. |
| 15 mins | Lists app uses in consortia |
| What uses for a Lists app in a multi-tenant situation? collection development
e-package analysis, what does each member purchase. Can use to negotiate package deal for all members
usage statistics (anonymized)
sharing templates for reporting amongst tenants Lists app is not just analytics, also tasks manager (list of missing items, finding errors, intransit too long → turn into tasks) We should go back to our past notes and find Consortia uses for Lists app, give that feedback to Harry for possible development. Harry thinks we could revisit the Task app (or Task Manager).
Also interest in a Workflow app (from Coral)
This group could look into this, what would be useful in the context of consortia There’s also the dashboard:
if items meet my criteria, have them show up on my dashboard.
Alerts/triggers to say “you have to do this” would be useful. |
Action items
- Discuss Consortia use cases for Workflow app
- Revisit notes on Consortia use cases for Lists app, reporting needs
- Harry will look for old presentations of Task and Workflow app