Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

All functionality implemented in Round II & MVP

Performance

  1. Ability to load 1,000,000 - 5,000,000 records in a reasonable period
  2. Ability to operationally load (including match, and merge) records in a reasonable period (50,000-100,000 records)
  3. Circulation performance at acceptable rates for check-in, check-out, renewal. (3 items per second or better.)

Upgrade in place

  • Ability to upgrade without having to reload all the local data

Custom Fields

  • Ability to store custom fields in the LDP

Improved Search

  • Further improved call number search and sort
  • Call number search outside of inventory 
  • Improved or fielded user searching
  • Normalized searching for title/call number

Metadata Management

  • Batch and global updates
  • Exports (generalized beyond basic exports in Round II and MVP)
  • Batch delete of inventory records
  • Transfer holdings and items (i.e. transfer holdings to a different instance record, transfer items to a different holdings record) 
    Jira
    serverFOLIO Issue Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-137
  • Data import: more sophisticated matching and overlay
  • Data import: import of delimited files
  • On-the-fly records 
    Jira
    serverFOLIO Issue Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1057

Acquisitions Requirements

  • Financial transaction accounting 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-2295
  • Fiscal Year Rollover capability 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1149

Donor recognition and tracking - touches multiple modules

Resource Access

  • LTI support from Courses App for integrations with external LMS and discovery layer systems
  • CAIASoft integration
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-498
  • Basic Needed For implementation (Item State)
  • Basic Process Implementation (Item State)
  • Circulation Log / Audit History
  • Notices: view history
  • Allow request policies to control fulfillment options
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1561

Documentation

Chicago Gaps

This section is meant to facilitate discussion. This includes items that are intended for development but we are concerned could slip.

Some gaps may appear more than once as they affect different areas.

Big Issues

Cross-app entanglement between Orders and Inventory: Orders links to Inventory at both the item and instance level. The consequence is that moving an item to a new holding in Inventory now much account for and update that linking data in Orders. Can Orders just use the item, and use that to get to the instance when needed? Can Inventory ease this access in the API?

Some features cannot be worked around, but there may be some critical component that would be enabling of workarounds outside of FOLIO. In Imports, if we could configure the protection of fields on a per-tenant and content-sensitive basis, that might allow us more flexibility. For sites with remote storage or automated storage systems, a storage retrieval request could enable those integrations.

Functional Areas

Acquisitions

  • Fiscal Year Rollover (no Q): 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1149
  • Donor information (Q3): 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1018
  • Financial Transactions (Q2) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-2295
  • Import/export fund updates (blocker? Q3) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-199
  • Import Orders/Invoices from MARC (Q?, do we think this is in jeopardy for MVP?)

Integrations

  • Discovery Layer
    • Export for Discovery Layer
  • Storage systems
    • Storage Retrieval Requests

Metadata Management

  • Edit MARC records in SRS (quickMARC, Q2): 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-2263
  • Global updates (no Q for in-place; export/transform/import is proposed workaround)
    • Ability change, add, or delete administrative instance data (status, statistical codes, etc), holdings, or item data in Inventory.
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-141
       (Q3)
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-142
       (Q3)
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-977
       (no Q)
  • Batch delete of inventory records (no JIRA)
    • Needed to recover from bad data loads? (e.g. vendor sends file with bad data)
  • Batch Exports (Q varies by sub-feature?) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-652
    • Might need more analysis to identify specific priority features
    • Use cases
      • Export to discovery layer (workaround for OAI-PMH), full exports and deltas
      • Export for OCLC, HathiTrust, and other forms of record exchange
      • Critical to workaround expected lack of global updates, will need to export, transform, and reload records in order to do records maintenance at scale
      • For more examples and details, see Export Use Cases
    • Central go-live needs
      • Export of bibliographic records in MARC and/or MARCXML based on selection criteria
      • ability to include holdings and items data with bib data
      • Schedule defined export jobs and launch as needed
  • Batch Imports (no Q) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-47
    • There is a critical problem in the area of protecting bib fields from being written over. Currently there is some hard-coded functionality, but does allow for basing decisions on tenant-specific data, such as the presence of a library's OCLC code in a field. This needs to be configurable on a per-tenant basis, and the APIs should have an option to override this protection.
  • OCLC Holdings 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyREP-252
    • Ability to automate setting of OCLC holdings via OCLC API when local record conditions are met.
    • Q: Could we do this from LDP?
  • Change Item Status (no Q) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1731
  • Item status - Not Available (Q4) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-2127
    • What problem is this solving?
    • Straw man: To support discovery layer/Z39.50/ILL discovery (and possibly other cases), we need to the item APIs to include a flag that indicate whether an item is available. This information is used in discovery to set expectations for users. The flag would be computed from item statuses. A site would configure Statuses like "not charged" or "recently recently returned" to show up as available, and statuses like "charged" or "missing/lost" to be not available.  A more precise description might be "item available/not available flag".
  • Acquisitions details visible in Inventory (no Q)
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1607
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1925
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1995
  • Custom item statuses (no Q, Q2 for withdrawn items only)
    • Ability to create item statuses that are not represented by the default item statuses (Withdrawn, Withdrawn BTAA-SPR, Analytic - need workarounds for these statuses.)
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1995
  • Transfer items/holdings to another instance (Q3) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-137
    • Should be trivial within Inventory, but needlessly complicated by Orders
  • Preview data import (Q3) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-669
    • Ability to review import results before committing an import. Alternately, need a test system with current data (within one day) to run imports before running in production.
    • Question: is this meant to include previewing loads that would affect areas outside of inventory, like Orders?
  • OCLC - single record update (Q3) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-211
    • Dealing with outside of main project resources
  • Normalized call numbers (Q4)
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-2002
    • The purpose of this feature is to generate and store a machine-sortable call number for the purposes of sorting lists such as Loans and Fees/fines. The machine sortable call number will also be available for inclusion in reports (both in-FOLIO and external to FOLIO).
  • Migrate analytic and bound-with data (Q4) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1856

Resource Access

  • Interlibrary Loan integrations with Relais, ILLiad (MVP? Need to confirm in live systems)
    • Z39.50 support (for ILL discovery, Q2?) 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-560
  • Aged to Lost (Q4) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-87
  • Patron block overrides (Q4) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1130
  • Item block overrides (no JIRA?)
  • Fee/fine notices (Q2) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1391
  • Patron blocks – automated creation (Q2) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-82
  • Patron notice errors (Q3) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-2382
  • Cash drawer balancing (Q4) 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-845

Round IV - Post MVP

Cornell University

Five Colleges

Duke University

Texas A&M University

University of Chicago