| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Category | Function | The Why: Notes / Examples | Associated SIG | Leverages existing or requires new functionality? | Interest Level or count? | Notes | ||||||||||||||||||||
2 | General | Dropdown List Config | Ability to Centrally set contents or add contents to configurable dropdown lists; Parameters can be set in one place for all modules involving a particular parameter | App Interaction, UX Slack | Existing | ||||||||||||||||||||||
3 | General | Hierarchical configuration | Libraries in group can inherit "from above" (cascading) and locations are aware of properties "from below" and use this for scoping/batch function options | Bulk Edit SIG | New | Is this out of scope? | |||||||||||||||||||||
4 | Tenant Management | Admin User Creation | User who can set up user privileges for users from different tenants and assign them cross tenant rights if needed | New | GBV | ||||||||||||||||||||||
5 | Tenant Management | Permissions Auditing | Function to display admin and other cross tenant roles | New | GBV | ||||||||||||||||||||||
6 | Tenant Management | Workflow Mangement | Configuration of tenant, permissions, and roles | App Interaction | Existing | Z Sasyk, EBSCO, Stanford hbz, GBV | |||||||||||||||||||||
7 | Tenant Management | Integrations | Centrally managed ERP (SAP/Banner) for financials, system settings for batch import/export with FOLIO | Bulk Edit, Acquisitions | Existing | Z Sasyk, EBSCO, Stanford hbz, GBV | |||||||||||||||||||||
8 | Tenant Management | Tenant Configuration | Centrally standardized configurations, policies, settings. Ability to "change once" and apply across tenants, configuration audit report functions | App Interaction | New | Z Sasyk, EBSCO, Stanford hbz | |||||||||||||||||||||
9 | Tenant Management | Library configuration | Moving locations to a different library by changing just one entry in the configuration | Bulk Edit | Move to bulk edit | GBV | |||||||||||||||||||||
10 | Circulation - Borrow/Request | Notices | Ability to customize notifications based on the patron home library | Resource Access | |||||||||||||||||||||||
11 | Circulation - Borrow/Request | Load Balancing | Centrally managed load balancing for unmediated hold requesting | Resource Access | New | FLO | |||||||||||||||||||||
12 | Circulation - Borrow/Request | Title/Item/Volume Request | Functionality for both + ability to set any relevant configuration settings centrally; request specific volume but perhaps not copy | Resource Access | New | FLO | Need volume level. Currently item level hold only - working on Title level | ||||||||||||||||||||
13 | Circulation - Borrow/Request | Borrowing Limit | Ability to create distinct groups of tenants for requesting wtihin a multi-tenant configuration (ex. Public libraries in one group; Academics in another) | Resource Access | New | Z Sasyk, EBSCO, FLO | |||||||||||||||||||||
14 | Circulation - Borrow/Request | Request routing + logic | Ability to set system configuration to allow "moving" requests as needed or workflows/logic for directing requests when required to fulfill via other systems | Resource Access | New | Z Sasyk, EBSCO, FLO | |||||||||||||||||||||
15 | Circulation - Borrow/Request | Integrations | Ability to configure integrations with other systems across tenants/centrally (Discovery, External Resource Sharing System, Campus Financial Systems) | Existing | Z Sasyk, EBSCO, Stanford, FLO, GBV | ||||||||||||||||||||||
16 | Circulation - Borrow/Request | Patron Prioritiy | Libraries can determine priority of patrons (local vs. consortial) perhaps multi-tiered scopes of tenant libraries | User Management / Resource Access | New | Z Sasyk, EBSCO, FLO | |||||||||||||||||||||
17 | ERM | eHoldings Data | Interest in pushing data from central office to one or more tenants (eHoldings app) that then populates 3rd party tools (KBs, authentication systems like OpenAthens, etc.) | ERM | New | Z Sasyk, EBSCO, GBV | |||||||||||||||||||||
18 | ERM | Dropdown List Config | Ability to push items into library defineable dropdown lists within ERM module | ERM | Existing / New | Z Sasyk, EBSCO, GBV | |||||||||||||||||||||
19 | ERM | License Terms | Ability to push encoded license terms to tenants | ERM | Existing / New | Z Sasyk, EBSCO, GBV | |||||||||||||||||||||
20 | ERM | KB | Ability to push knowledge base files to local tenants via Local KB Admin | 0 | Existing / New | Z Sasyk, EBSCO, GBV | |||||||||||||||||||||
21 | ERM | Open Athens | Configuring FOLIO tenants as target for Open Athens authentication eg. ability to log in with credentials via OpenAthens | ERM / App Integration | Is this consortial? | Z Sasyk, EBSCO | User Stories needed - different statuses; who is using multiple patron banks, and roles Is ERM involved with this? Could this apply to resource remote access testing/consortia group purchases? | ||||||||||||||||||||
22 | ERM | Authentication Links | Authentication link configuration for individual tenants to shared or group purchases (eg. eBook packages) | ERM | New - Can we define and submit this as JIRA? | Z Sasyk, EBSCO, GBV | |||||||||||||||||||||
23 | Batch Process | Batch Monitor | Status of batch processes + automated tasks, warnings for incomplete/failed jobs | Sysops / Management / App Interaction / all? | New | GBV | |||||||||||||||||||||
24 | Bulk Edit | Bulk Edit Logs/Errors | Status of bulk edits | Bulk Edit | New | GBV | |||||||||||||||||||||
25 | Bulk Edit | Scheduling | Ability to schedule bulk edits | Bulk Edit, App Interaction | New | GBV | |||||||||||||||||||||
26 | Batch Process | Batch Scheduling | Ability to schedule batch processes (patron loading, removal of users and patrons, removal of lending requests, creation and update of search index) | Sysops / Management / App Interaction / all? | New | Z Sasyk, EBSCO, Stanford, GBV | |||||||||||||||||||||
27 | Batch Process | Scheduling of offline jobs | Schedule and run statistics of local library system's offline (ie Consortia Admin Tool) jobs (example: WebSMM|APCC, which is the tool from OCLC|PICA LBS in use at GBV. It is now integrated in the UI but only accessible as admin) - Use cases: volume (barcode) update from catalogue to lending app; create acq orders offline and send them by email; all kind of reminders (acq: open orders, open issues of subscriptions; loan: overdue loans); printing address labels; fiscal year rollover routines; importing orders and invoices from vendors; fixing of inconsistent data in different tables) including warnings; email communications | App Interaction | GBV | ||||||||||||||||||||||
28 | Bulk Edit | Preview | Preview of results of bulk edit change | ||||||||||||||||||||||||
29 | Bulk Edit | Patron Attributes | User loads, patron expiry, blocks, etc. | Bulk Edit | GBV | ||||||||||||||||||||||
30 | Bulk Edit | Record updates | Changing vendor/resource URLs, Record updates ie. 856 | Bulk Edit | Z Sasyk, EBSCO, Stanford, GBV | ||||||||||||||||||||||
31 | Batch Process | Bib updates/imports | Authority, Bib records | Entites Management (?) | First dependent on where folio goes to address this and implement the feature for a single tenant. Then perhaps central admin tool would perform the function at the consortium level. | ||||||||||||||||||||||
32 | Batch Process | Bib batch export | OCLC, HathiTrust, Discovery Holdings | Z Sasyk, EBSCO, Stanford | Follow up on this functionality for existance for individual institutions - See 11 - perhaps related but not this case specifically | ||||||||||||||||||||||
33 | Bulk Edit | Items | Item status / availability changes (ex. Setting availability for items during covid and group circulation); renewals, checkin/out, withdrawls, item properties | See 1,2,3,4,5,11,...58 | |||||||||||||||||||||||
34 | Batch Process | Acqusitions | Orders (status, export/imports), reminders - include note about consortial ordering - ability to push to all tenants due to consortial agreement/contracts (possibly single tenant or multilibrary system) | Acquisitions | Z Sasyk, EBSCO, GBV | Not included: clarify | |||||||||||||||||||||
35 | Bulk Edit | Acqusitions | Orders record issues for corrections or other order record elements; include note about consortial ordering - ability to push to all tenants due to consortial agreement/contracts (possibly single tenant or multilibrary system) | Acquisitions | Z Sasyk, EBSCO, GBV | ||||||||||||||||||||||
36 | Batch Process | Financial | Bursar communications of transactions, patron fees/fines, budgets, invoices, EDI; automate data import | Acquisitions, Resource Access | Admin Role | Z Sasyk, EBSCO, GBV | Not included; clarify | ||||||||||||||||||||
37 | Bulk Edit | Logic/Conditions | Calculations for patron expiry, Changes based on conditions such as patron status changes with certain circumstances (if fines exceed certain date, drop fines from account), triggers for processes | Resource Access | Function; not included | ||||||||||||||||||||||
38 | Batch Process | Logic/Conditions | Calculations for patron expiry, Changes based on conditions such as patron status changes with certain circumstances (if fines exceed certain date, drop fines from account), triggers for processes | Resource Access | Function; not included | ||||||||||||||||||||||
39 | Documentation | User documentation | Application documentation for “key users” with background information, automatically distributed, | Documentation WG | C Tobias (DOCS WG) | Documentation for docs.folio.org | |||||||||||||||||||||
40 | Documentation | Institutional Information | Profile information; Contacts, correspondence & tracking, harware info, networking details, statistics identifiers, etc. | ||||||||||||||||||||||||
41 | Documentation | Mail log | Maintain log of library / patron communications | FLO, GBV | |||||||||||||||||||||||
42 | Documentation | Central Admin | Firewall configuration, schedule of all batch processes, runtime stats of processes and offline jobs, status | GBV | |||||||||||||||||||||||
43 | Documentation | Integration | Integration of documentation and documentation of interactions may be legally required for some groups | ||||||||||||||||||||||||
44 | System Monitoring | Health Checks | |||||||||||||||||||||||||
45 | System Monitoring | Batch process dashboard | Batch processing checks - warnings for incomplete/failed jobs | GBV | |||||||||||||||||||||||
46 | System Monitoring | Version change | Version change notes, information | ||||||||||||||||||||||||
47 | System Monitoring | Consistency checks | |||||||||||||||||||||||||
48 | System Monitoring | Restore | System restore, rollback to earlier state, disaster recovery | GBV | |||||||||||||||||||||||
49 | Mailing | User information | Uses mail addresses from ILS user accounts | FLO | |||||||||||||||||||||||
50 | Mailing | Templates/configuration | Highly configurable, can provide listings of items, fees etc. to the patrons | FLO, GBV | |||||||||||||||||||||||
51 | Mailing | Language | Supports multiple languages | GBV | |||||||||||||||||||||||
52 | Mailing | Communication flexibility | Used for regular mails not supported (yet) by the ILS and also one time mails - for instance during a pandemic | ||||||||||||||||||||||||
53 | Data management | Syncronization | Synchronize accounts between ILS and union catalogue (currently every two hours) | Batch Process | |||||||||||||||||||||||
54 | Data management | Fine/Fees | Remove time-barred fees and fines (example: on January, 1st using cron) | Resource Access | Add to bulk edit | ||||||||||||||||||||||
55 | Data management | User deletion | Remove “obsolete” users | Resource Access | Add to bulk edit | GBV | |||||||||||||||||||||
56 | Data management | User management | Prolong expiration of many or all user accounts (during pandemic, may have side effects that only admins can treat properly) | Resource Access | Add to bulk edit | ||||||||||||||||||||||
57 | Data management | Transmission of fees | Transfer of “no longer acceptable” fees and fines “to the bursar” in conjunction with blocking the patron in the ILS. (example: monthly using cron) | Resource Access | Batch Process | ||||||||||||||||||||||
58 | Circulation | Self service | Enhanced circulation via virtual self service machine (using SIP2) | Resource Access | |||||||||||||||||||||||
59 | Circulation | Auto Renewals | Automated renewals “within” loan rules - if nothing (fees, status etc.) prevents them | Resource Access | |||||||||||||||||||||||
60 | Circulation | Custom renewals | Infinite renewals in contrast to the previously used “giant/infinite” loan period - no more recalls and transparent loan periods | Resource Access | |||||||||||||||||||||||
61 | Data Warehouse | LDP (consortia case) | Reports are constructed with SQL (Postgres) queries; Index data may be at work? | Reporting | GBV | ||||||||||||||||||||||
62 | Data Warehouse | API | API connection management | System Operations and Management? App integration? | GBV | ||||||||||||||||||||||
63 | Data Warehouse | LSP data push/feed | FOLIO data push connection | System Operations and Management? App integration? | |||||||||||||||||||||||
64 | Data Warehouse | Harvest | Harvesting and storing data across tenants | System Operations and Management? | GBV | ||||||||||||||||||||||
65 | Data Warehouse | Exports | Technical export of data | Reporting | GBV | ||||||||||||||||||||||
66 | Data Warehouse | Admin Reports | Predefined “Admin Reports” | Reporting | GBV | EOM note: In-app "reports" are not covered by Reporting. Reporting currently focuses on querying the database directly on specific data fields, either within a module or across modules. They are building a repository of sample queries, but there's not really "predefined reports" in the sense there may be in other LMS | |||||||||||||||||||||
67 | Data Warehouse | Reconciliation Reporting | Reporting for reconciliation | Reporting | EOM note: reconciliation of intraconsortial borrowing? | ||||||||||||||||||||||
68 | Authority | Change push | Ability to connect with authority provider to send new catalog records and push changes through to associated library bib records - deduplication | Metadata Management | |||||||||||||||||||||||
69 | Authority | Group Authority Process | Generate a list of new MARC records across the consortium, deduplicated, to authority service and reinsert records into the assocated institution(s) catalog | Explore HRID impacts and ability of data loader to accommodate multple HRIDs in records | |||||||||||||||||||||||
70 | Authority | Linked Data | Consider utilizing URIs/Linked Data to build in relationships between records and authority | Metadata Management | Raise for awareness with Metadata Management | ||||||||||||||||||||||
71 | Sandbox | Configuration | General central configuration | ||||||||||||||||||||||||
72 | Sandbox | Data selection | Initiate sandbox with test data, not live | ||||||||||||||||||||||||
73 | Sandbox | Data / Settings Refrech | Refresh with data from live environment | ||||||||||||||||||||||||
74 | Sandbox | Scheduling/Batch | Schedule data refresh | ||||||||||||||||||||||||
75 | Sandbox | Target Tenants | Ability to target or select tenants for sandbox CRUD | ||||||||||||||||||||||||
76 | Sandbox | Sandbox lifecycle | Perpetual access vs. temporary point-of-need | ||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||
100 |