LDP Known Issues

Preserving Circulation Demographic data

Preserving Circulation Demographic data

• patron id is wiped from circulation tables when items are checked in, which results in losing connection to demographic data in custom fields for reporting
• cul derived local table to grab and save demographic data daily
• need something like the circulation_transaction_stats table we had in Voyager
• take snapshot of loans_items, then save demographic (custom fields) data before the patron id is wiped

unresolved,  workaround in progress

Call Number Order on Holdings-Level Call Numbers 

Unresolved

Orchid Breaking Changes for Subjects and Series

Breaking changes for Orchid release: updates to instance records (subjects and series) to capture changes associated with authority control

Cornell goes to Nolana - end of Feb, beginning of March

Cornell goes to Orchid - hopefully before Fiscal Year Rollover

• • https://folio-project.slack.com/archives/C210RP0T1/p1672757167354339
  • https://issues.folio.org/browse/MODQM-276

• subjects field will be converted from an array of strings to an array of objects.
• series field will be converted from an array of strings to an array of objects.
• alternativeTitles field object will be extended with authorityId field

The changes are mainly related to two fields: 
subjects field is now an array of objects: 
 

"properties": { 
  "value": { 
"type": "string", 
"description": "Subject heading value" 
  }, 
  "authorityId": { 
"type": "string", 
"description": "UUID of authority record that controls a subject heading", 
"$ref": "uuid.json" 
  } 
} 

series field is now an array of objects: 
 

"properties": { 
  "value": { 
"type": "string", 
"description": "Series title value" 
  }, 
  "authorityId": { 
"type": "string", 
"description": "UUID of authority record that controls an series title", 
"$ref": "uuid.json" 
  } 
} 

Finance_Budgets table issue

• on the public.finance_budgets table for LDP1, several fields are not getting calculated properly due to the way the calculations are done in the FOLIO application fields

Finance_Budgets table issue

• on the public.finance_budgets table for LDP1, the following fields are not getting calculated properly due to the way the calculations are done in the FOLIO application fields:
• allocated
• cash_balance
• total_funding
• available
• unavailable
• over_expended
• over encumbrance
• see submitted LDP issue 226 on this for more details
• see details from FOLIO developer Serhii Nosko
  • https://github.com/folio-org/mod-finance-storage/blob/master/src/main/java/org/folio/utils/CalculationUtils.java#L61.
  • They are calculating each time a budget is retrieved (by budget id or by some query).
  • I created a story to calculate them on updating or saving budget, rather than doing it on get which is how it is working now.
  • https://issues.folio.org/browse/MODORDERS-837
  • For LDP to resolve their issue without waiting for this story to be released – they could use the API to retrieve finance budget data. Or as an workaround – make a request to retrieve necessary budgets before collecting data as after this all fields will be updated in DB.
• Yes, these fields are calculated on the fly, here is a list of these fields in code that fully matches list provided by LDP (line 61-67):
• these fields can be calculated in individual queries, but this is cumbersome
• the data might be able to be extracted from the finance transactions table
• Axel suggests we create a daily script to run against our LDP that will find every budget updated by the FOLIO API in order to trigger a daily update to the fields on the finance_budgets table
• reports impacted: CR122, CR157, CR165, CR132
• dashboards are not impacted

Workaround in place

Bug submitted, to be fixed in Poppy release

• discrepancy is between data in FOLIO and data shown the Fund Detail Tableau dashboard
• The issue is when the FYRO was run at the end of FY22 – the balances were moved forward under the transaction type Rollover transfer.  When capturing the Group view, the programmers didn’t take into account the Rollover transfer within the Net transfer on the Group view.  This has been submitted as a bug.  Unfortunately, this will not be addressed until the Orchid release.
• see https://issues.folio.org/browse/MODFIN-299
• Until FOLIO is updated – When looking at your Team information, please rely on the Tableau dashboard created by Nancy Bolduc.

• Cornell goes to Nolana - end of Feb, beginning of March

  Cornell goes to Orchid - hopefully before Fiscal Year Rollover

Unresolved 

Bug submitted, to be fixed in Orchid release

Cast all ids from tables that connect to srs_marctab as "::uuid"

Example code when joining srs_marctab AS sm to srs_records AS sr

        LEFT JOIN srs_marctab AS sm ON sr.id::uuid = sm.srs_id 

The srs_marctab table can be connected to the public.inventory_instances table via hrid, and the instance_id can be brought in from the inventory_instances table.

Example code:

SELECT
    ii.id AS instance_id,
    ii.title AS title,
    substring(sm."content", 7, 2) AS "format_type"
FROM 
    public.inventory_instances AS ii
LEFT JOIN srs_marctab AS sm
    ON sm.instance_hrid =ii.hrid

WHERE sm.field = '000'

Another way to get data from the srs_marctab table and insert a correct instance_id is via the srs_records table.

Example code:

SELECT
        sr.external_id AS instance_id,    
        substring (sm.content,7,2) AS format_code
FROM
        srs_records AS sr
        LEFT JOIN srs_marctab AS sm ON sr.id::uuid = sm.srs_id 
 WHERE sm.field = '000'     

  --NOTE that all ids in the srs_marctab table have been cast as uuids, so cast the OTHER table's id as ::uuid