SIG Priorities-20161031-DRAFT
Original Sender
The following document was created by Hkaplanian and emailed to the Product Council on 2016/10/31. The original document is attached.
- RM - Resource Management
- This involves the management of all library holdings which include at the minimum:
- E-journals
- E-Books
- Print books
- Print journals
- Video & images
- Music and sound recordings
- Institutional repositories
- Equipment
- Acquisitions & Financial Management – What happens when a title is purchased (for example)? The record/holding should be available within the system automatically. What should that look like? Does this become a part of RM?
- Multi-library configurations
- What key opportunities exist here for linked data?
- Holding deletion & deactivation – What is the ideal feature set & workflow
For all of the above and any others that become apparent, where should we be at 5 and 10 years from now?
- Search needs
- This involves the management of all library holdings which include at the minimum:
- User management (rename LSP Rights Management on the Wiki)
Matrix of permissions (functions in FOLIO apps) and roles (logical groupings of permissions that can be assigned to users)
- Controlling access to applications
- Controlling access to features
- Circulation rights
Handle external identity sources (Shibboleth, LDAP, OAUTH, etc), including a process for mapping attributes from external identity sources to FOLIO roles and groups and merging identities from multiple external sources and a local-to- FOLIO user database. Should this exist under “Access Management”?
Local-to- FOLIO user database (could be used for community borrowers or other temporary users)
Batch loading and overlaying users into a local-to- FOLIO user database from external sources
- Batch operations for managing users into the system
- Security/privacy needs worldwide
- Super users/administrators
- Search needs
- User expirations and related operations
- Temporary users
- Staff vs Students
Batch operations – Think about having 60,000 students. How could the above operations happen in batch? Which of those could occur during record loading? How are IDs, passwords dealt with?
- Multi library situations. Could be staff in one library and student in another
- Access Management
What are the key attributes for a great circulation system (Speed, hands free operation, mouse free operation) ?
- Required key transaction types – loans, renewals, holds, etc
- Exceptions/overrides
- Downtime/ offline use
- Changes and corrections to users & items
Barcodes/RFID/theft protection – Do libraries still apply these for physical items? Do these have any impact on the FOLIO solution and workflows?
- Transaction history & reporting
- Configurability
- Multi-library configuration
- Borrowing between libraries
- Search needs
- Standards Compliance
Metadata Management - Cataloging/metadata management – how often does this actually happen in the current ILS? Doesn’t the current ILS mostly import records from OCLC, national unions, consortia, e-Book vendors? Is this still a key part of a library management system?
- Record loading & Export
Bibliographic data and data types - This include a consideration of what is really needed to manage holdings in a world of Knowledge bases and systems that can interoperate.
- Holding deletion & deactivation – What is the ideal feature set and workflow
- Matching/duplicate detection
- Required metadata formats while considering content types listed in the RM section
- Using record loading & matching as a tool for batch updates
- Reporting needs
- What about patrons/users?
- Multi library setups
Authority Control - Make use of shared authorities (e.g. from national libraries, from VIAF, etc.) and establish local authorities. Should this be a shared knowledgebase?