...
a mini-project to fix them. Here is a link to our documentation for Making a Pull Request for FOLIO Analytics
| Table Name | Priority | Status | Who is Fixing/Updating | Notes | PR link |
|---|
| agreements_package_content_item.sql |
available
| restored | Stefan? | no records for CUL |
|
| feesfines_accounts_actions.sql |
availableavailable| HIGH | restored, needs update | Joanne/Sharon | PR submitted |
Next Step: Sharon to run by Ann, then submit PR; Not impacted by Poppy; needs updating onlyavailable
| restored | Sharon/Ann |
|
|
| holdings_electronic_access.sql |
not availableNatalya | | Corrie | Corrie to put in a PR to update the derived table and will send us instructions to fix our data. From Corrie: The holdings_electronic_access table issues are related to https://folio-org.atlassian.net/browse/UIIN-2787. Essentially, if an empty relationshipId exists when Metadb expects a UUID, the table will fail to build. Until we can fix the derived table, we've addressed it for Chicago by adding the appropriate UUID value. |
|
| holdings_ext (metadb) | HIGH | needs update | Vandana, Joanne, Linda | -(Linda) The holdings_supress field needs to be cast as Boolean. It is currently cast as varchar. (Joanne) The json extract for ill_policy_id also needs to be cast as UUID. -(Christie) the holdings_ext table is bringing in the created by userid rather than the updated_by_user_ud for the updated_by field. The location of the data being pulled needs to be updated so that the updated_by_user_id is what is being pulled from the json. | -PR submitted for Metadb version |
Next Step: Sharon to reach Stefan and Nassib for help with this one |
| holdings_statistical_codes.sql |
availableavailable
| restored | Joanne/Vandana |
|
|
| item_ext.sql |
| needs update | David Bottorff, Joanne | The folio_derived.item_ext table in metadB is storing status_date as long text rather than as date/time. Need to check all date fields for this. (Joanne) would also be good to have effective_shelving_order field from folio_inventory.item table | https://github.com/folio-org/folio-analytics/issues/860 |
| items_holdings_instances.sql |
available | |
| restored, needs update for both LDP and Metadb versions | Natalya | (LDP) in the items_holdings_instances table, the column instance_hrid is showing the same value as the holdings_hrid instead of the instance's hrid (Metadb) instance and holdings HRIDs need to be added; effective call number also missing | -PR submitted for LDP version |
Joanne/Vandana |
| loans_renewal_dates.sql - both LDP and Metadb | HIGH | low records | Joanne | Next Step: Joanne to first work on LDP version and give to Sharon/Vandana for PR -will rewrite so that inflated counts of renewals are not made -each step of processing is counted as a renewal, when it should |
be using the folio_circulation.audit_loans__ table for the source, not the folio_circulation.loan table; CR184Ajust be one -should discuss with Reporting SIG | -PRs submitted for LDP and Metadb |
| openaccess_checklists.sql |
not available
| restored |
| Next Step: Sharon to ask Stefan to fix this one
low priority - no data in CUL FOLIO Prod |
|
| openaccess_publication_request.sql |
not available
| restored |
| Next Step: Sharon to ask Stefan to fix this one
low priority - no data in CUL FOLIO Prod |
|
| po_instance.sql |
available| (metadb) | HIGH | restored, but needs update | Natalya/Joanne | Next Step - Natalya to update |
LDP Metadb version and submit PR |
need to verify if better to point to derived table po_lines_locations instead of extracting holdings id and locations id from JSON; see -updated to extract holdings and locations ids from JSON rather than pointing to a derived table | https://github.com/ |
culitcul-blob/main/review/po_instance.sql| issues/851 |
| po_line_fund_distribution_transactions.sql |
available
| restored | Sharon/Ann |
|
|
| po_lines_vendor_reference_numbers.sql |
available
| restored | Sharon/Ann |
|
|
| po_lines_eresource.sql |
available
| restored, needs update | Natalya | -will update with CASE WHEN to show deleted_holdings |
|
| po_lines_locations.sql |
available
| restored, needs update | Natalya | -will update with CASE WHEN to show deleted_holdings |
|
| po_organization.sql |
available -update submittedavailable
| restored | Joanne/Vandana |
|
|
| users_groups.sql |
available
| restored, needs updates to LDP and Metadb tables | Joanne/Vandana | -low priority Next step: Joanne to fix these after other tables get fixed
LDP: the first subquery (creating the user_departments table) uses the users_departments_unpacked derived table, but doesn't specify "folio_reporting" as the schema. The department information from the custom fields (of the user_users table) is not properly extracted. MetaDB: the code does not specify the folio_derived schema for the user_departments subquery. Also, the MetaDB version is lacking the "user_tags" and "user_custom_fields" fields that are in the LDP version. |
|
| loan_renewals_counts |
| reviewed | Joanne | Joanne reviewed this table and it is fine |
|
