Page tree

Versions Compared

Key

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

...

  • Most front-end modules don't fetch exact search result count from backend (
    Jira
    serverFOLIO Issue Tracker
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyRMB-673
    ).
  • Estimated search result count has a wording that incorrectly suggests it is a precise number ("8081 records found"). Only numbers below 1000 are precise (details: RMB Estimated totalRecords). (WIP UXPROD-2623 - Wait for POC of Elastic Search - Round estimated search result hit count (totalRecords) Blocked )
  • Some modules fail in Pgpool-II replication (
    Jira
    serverFOLIO Issue Tracker
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyFOLIO-2447
    ,
    Jira
    serverFOLIO Issue Tracker
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyFOLIO-2978
    ).
  • Upgrade might fail for mod-source-record-storage while executing “2020-09-09--15-00-fill-instance-hrid” migration script. It is caused by the presence of MARC_Bib records with double multiple “001” fields in the DB. In order to successfully upgrade, such records should be revised and corrected (use check_001_field_duplicates.sql to find such records). Otherwise, upgrade to Juniper HF#1 version once it is available.

...