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.

 

  1. RM - Resource Management
    1. This involves the management of all library holdings which include at the minimum:
      1. E-journals
      2. E-Books
      3. Print books
      4. Print journals
      5. Video & images
      6. Music and sound recordings
      7. Institutional repositories
      8. Equipment
    2. 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?
    3. Multi-library configurations
    4. What key opportunities exist here for linked data?
    5. Holding deletion & deactivation – What is the ideal feature set & workflow
    6. For all of the above and any others that become apparent, where should we be at 5 and 10 years from now?

    7. Search needs
  2. User management (rename LSP Rights Management on the Wiki)
    1. Matrix of permissions (functions in FOLIO apps) and roles (logical groupings of permissions that can be assigned to users)

      1. Controlling access to applications
      2. Controlling access to features
      3. Circulation rights
    2. 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”?

    3. Local-to- FOLIO user database (could be used for community borrowers or other temporary users)

    4. Batch loading and overlaying users into a local-to- FOLIO user database from external sources

    5. Batch operations for managing users into the system
    6. Security/privacy needs worldwide
    7. Super users/administrators
    8. Search needs
    9. User expirations and related operations
    10. Temporary users
    11. Staff vs Students
    12. 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?

    13. Multi library situations. Could be staff in one library and student in another
  3. Access Management
    1. What are the key attributes for a great circulation system (Speed, hands free operation, mouse free operation) ?

    2. Required key transaction types – loans, renewals, holds, etc
    3. Exceptions/overrides
    4. Downtime/ offline use
    5. Changes and corrections to users & items
    6. Barcodes/RFID/theft protection – Do libraries still apply these for physical items? Do these have any impact on the FOLIO solution and workflows?

    7. Transaction history & reporting
    8. Configurability
    9. Multi-library configuration
    10. Borrowing between libraries
    11. Search needs
    12. Standards Compliance
  4. 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?

    1. Record loading & Export
    2. 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.

    3. Holding deletion & deactivation – What is the ideal feature set and workflow
    4. Matching/duplicate detection
    5. Required metadata formats while considering content types listed in the RM section
    6. Using record loading & matching as a tool for batch updates
    7. Reporting needs
    8. What about patrons/users?
    9. Multi library setups
    10. 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?