ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
PriorityFeatureDescriptionJIRANotes
2
Single Tenant featuresImportant for consortia with a large number of libraries
3
1Cataloging units/teamsCRUD Cataloging teams with assignement to libraries and collections
4
2Units & teams in licenses, agreements & users & CoursesUsers can be edited and viewed by home library only unless permissions granted otherwise.UXPROD-2137
5
3Units for organizations
6
Notes and tagsNotes and tags separation per organization per EBSCO KB subscriptionUXPROD-2377
7
Finance systems integrationNeeds to connect to/exchange data with multiple finance systems (e.g. one financial system per consortial member)UXPROD-800I feel like this should be higher priority than Cataloging units/teams. -sdoljack
8
Patron data restrictionsStaff without appropriate privileges can be restricted from editing and/or viewing patron data belonging to other consortium members.
9
Access/permissions control to FOLIO apps/modulesSetup and define access/permissions to FOLIO apps/modules based on my library type's structureUXPROD-2426
10
Integration with external ILL systemsNCIP & ISO-ILL supportUXPROD-557, UXPROD-991These tickets are both closed and in production already. -sdoljack
11
12
Multi-tenant features
13
1Circulation:
Borrowing, requesting, loan management (who do we bill?)
Unmediated Borrowing - Resource sharing		Most multi-tenancy issues are really just circulation related. Inn-Reach asks "where are you from"? Inn-Reach is unmediated exclusively
Patron initiated
14
Patrons can borrow/request/hold/recall/renew items directly from non-home member libraries (unmediated & cross tenant) with which their library has a resource sharing relationship. Ability to set borrowing rules.UXPROD-795
15
Patrons can view loans and other account information for all consortial libraries online via a single account/login within a FOLIO instance, across FOLIO instances, and with non-FOLIO systemsUXPROD-797
16
Can load patron information from multiple sources (1+ per consortial member) with conflicts/errors (both across consortium members and with a single consortium member) reported for manual resolutionUXPROD-798Needs review - title of JIRA does not match notes. This may be two separate functions. 1. Multiple IdP's / patron loads per insitution and 2. Handling staff/consortial user accounts with access to multiple institutions (this should be handled through permissions not through loading multiple copies of the same user information.
17
Needs to support multiple IDs per patron, with at least one ID field not needing to be uniqueUXPROD-805Is this so ID of multiple institutions can be in one user record? User records would be merged/combined? -drueda
18
If item is returned at non-owning library location, library can configure (at the collection or service point level) how the return is handled: possibilities include automatically put in transit to owning library, set a temporary location, shipping, etc.UXPROD-816
19
4Rota - Part of unmediated borrowing. Requests management, borrowing list & load balancing
20
Integration with external ILL systems, NCIP & ISO-ILL supportUXPROD-557, UXPROD-991
21
2Consortia Discovery, Union Catalogs - Cross tenant discovery to include fed search, etc. Multi-tenant - De-suplication such as Inn-Reach. Availability is key here. Key to multi-tenant features. Is it possible to conduct ILL without this? This is traditionally the search place. This can provide the single index, or this can be a federated search. Some have one, some don't. Shared cataloging crossover here. UXPROD-293, UXPROD-1434
22
Users need to view availability centrally
23
Records need to flow to and from tenants
24
Record de-duplication on central transfer
25
Ability to establish reference record to be used by all libraries
26
Filter by library and location when searching
27
Union Maintainence - Import, export, cataloging of holdings, items, instances, authority
28
Integration with OPAC and Discovery
29
Suppress from Discovery
30
Holdings and item support across multiple libraries
31
Mechanisms to enable member libraries to indicate and track consortial retention agreementsUXPROD-825
32
Staff with appropriate privileges can edit and/or view bibliographic/inventory data belonging to other consortium members.UXPROD-1761
33
3eHoldngs - HLM need to change, agreements & licenses tooPurchases from the consortia level can be managed by central management for all members.
34
Central Office, appropriately privileged staff can manage consortially-licensed resources at the consortium level (all phases of ERM)UXPROD-813
35
Mechanisms to enable member libraries to compare overlaps/gaps in holdings with other consortial partnersUXPROD-824
36
5MARC records and holdings transfer, Non-Union CatalogCopy cataloging is included here. Centralized cataloging (alma style, nice to have). The catalging unit. Record protection.
37
Each member library's bib records can be used as a KB by the other librariesUXPROD-807
38
Possibility for restricted cataloguing (just locally usable, e.g. grey literature, internal documents) besides shared cataloguingUXPROD-818
39
6Authentication & authorization across tenants
40
Patrons able to authn using multiple authn systemsUXPROD-808, UXPROD-822
41
Network/central office systems staff can see every library's data with a single loginUXPROD-810
42
Shared/central technical services staff with appropriate privileges can manage resources for any library within the consortium, preferably with a single login.UXPROD-811
43
Restful APIs need to be available to each member library, restricted to operations pertaining to their data as well as to consortium administrators across all member librariesUXPROD-814
44
Multiple consortial relationships need to be definable for each individual libraryUXPROD-820
45
Consortia relationships with other consortia need to be definable at the consortial levelUXPROD-821
46
7Mediated Borrowing = ILL BorrowingHow to identify patrons across tenants?
Can be patron initiated when asking for titles that don't exist in patron facing discovery
47
8Login into my FOLIO tenant and toggle to the consortial settingBe able to fill in reqests by patrons - Users and financials should be hidden
48
Network/central office systems staff can administer each library's presence seamlessly (ideally one account for access to all libraries). Tasks that systems staff need to perform are permissions/role management, data cleanup, configuration modification...UXPROD-809
49
9e-Borrowing/CDLControlled digital lending. Scanning and license management. Licensing does not translate to the real world. What does this do for librarians? TBD
50
10AcquisitionsPretty strong right now with Units, but needed everywhere else. We need central ordering & budgets support.
51
Vendor data (address, etc.) should be definable at the consortial level for any member library to referenceUXPROD-803
52
Acquistion shall be possible in a shared environment (one central dept. for all) or decentralized (each library for itself)UXPROD-806
53
Vendor data import (orders, invoices) needs to be targetable across multiple FOLIO instancesUXPROD-817
54
Centralized/shared management of financial operations and data should be possible.UXPROD-823
55
Staff with appropriate privileges can edit and/or view financial data belonging to other consortium members.UXPROD-1762
56
11Centralized reportingFor circulation, purchasing, budgets, cataloging and everything above. Used to justify why a library needs to be a member
57
Data needs to be available to evaluate both individual library contributions to the consortium and value received from the consortiumUXPROD-815
58
Consortial level statistics need to be produced by aggregating data from individual librariesUXPROD-819
59
Data ExportData export needs to be targetable across multiple FOLIO tenants (i.e. member libraries)UXPROD-826
60
Tasks/WorkflowsCentral staff and member libraries need to be able to or be restricted from assigning tasks in workflows to staff at other member librariesUXPROD-827
61
Data ImportData import needs to be targetable across multiple FOLIO tenants (i.e. member libraries)UXPROD-1419
62
Patron DataStaff with appropriate privileges can edit and/or view patron data belonging to other consortium members.UXPROD-1763
63
LocalizationMultiple Language and Localization settings per institution (was Multiple timezones per institution)UXPROD-592
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100