"- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) ""- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "- What would it mean to implement a consortium within a single tenant? - What would be the pros and cons of implementing a consortium as a single tenant vs multi-tenant? - Do we want to prioritize the work needed to support single-tenant consortia? May depend on discussion below. - What would need to change to make that possible? Would we need to scope/put limiters on: -- Users -- Permissions (e.g. should people only be able to edit calendars associated with a given service point or location?) -- Settings scoping (notifications, print slips, controlled vocabs etc - go through Settings and discuss all) -- Inventory/catalog scoping -- Funds -- Payments -- Consortial borrowing (may need a separate meeting for this) -- Etc. - What else would need to be considered? Review roadmap (consortia tab) "