The following derived tables are not getting created in Metadb Test because data types need to be fixed. Here is the status of
a mini-project to fix them. Here is a link to our documentation for Making a Pull Request for FOLIO Analytics
| Table Name | Status | Who is Fixing/Updating | Notes | PR link |
|---|---|---|---|---|
| agreements_package_content_item.sql | restored | Stefan? | no records for CUL | |
| feesfines_accounts_actions.sql | restored | Natalya | fixed for data types, submitted PR | https://github.com/folio-org/folio-analytics/pull/846 |
| finance_transaction_purchase_order | restored, needs update | Joanne/Sharon | PR submitted | https://github.com/folio-org/folio-analytics/pull/848 |
| finance_invoice_transactions.sql | restored | Sharon/Ann | ||
| holdings_electronic_access.sql | missing | Natalya | Next Step: Sharon to reach out to Stefan and Nassib for help with this one | |
| holdings_ext | Christie | |||
| holdings_statistical_codes.sql | restored | Natalya | fixed for data types, submitted PR | https://github.com/folio-org/folio-analytics/pull/844 |
| instance_ext.sql | restored | Joanne/Vandana | ||
| items_holdings_instances.sql | restored | Joanne/Vandana | ||
| loans_renewal_dates.sql - both LDP and Metadb | 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 just be one -should discuss with Reporting SIG | |
| openaccess_checklists.sql | restored | Next Step: Sharon to ask Stefan to fix this one low priority - no data in CUL FOLIO Prod | ||
| openaccess_publication_request.sql | restored | Next Step: Sharon to ask Stefan to fix this one low priority - no data in CUL FOLIO Prod | ||
| po_instance.sql | restored, but needs update | Natalya/Joanne | Next Step - Natalya to update 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 https://github.com/cul-it/cul-folio-analytics/blob/main/review/po_instance.sql | |
| po_line_fund_distribution_transactions.sql | restored | Sharon/Ann | ||
| po_lines_vendor_reference_numbers.sql | restored | Sharon/Ann | ||
| po_lines_eresource.sql | restored | Natalya | ||
| po_lines_locations.sql | restored | Natalya | ||
| po_organization.sql | restored | Joanne/Sharon | fixed for data types and extracted more from JSON, submitted PR | https://github.com/folio-org/folio-analytics/pull/842 |
| requests_items.sql | restored | Joanne/Vandana | ||
| users_groups.sql | restored | Joanne/Vandana | -low priority Next step: Joanne to fix these after other tables get fixed 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 | needs review | Joanne | need to review this table |