Versions Compared

Key

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

...

Table NameStatusWho is Fixing/UpdatingNotesPR link
agreements_package_content_item.sqlavailableStefan?no records for CUL
feesfines_accounts_actions.sqlavailableNatalyafixed for data types, submitted PRhttps://github.com/folio-org/folio-analytics/pull/846
finance_transaction_purchase_orderavailableJoanne/SharonNext Step: Ann has approved changes, so Sharon to run by Ann, then submit PR; Not impacted by Poppy; needs updating only
finance_invoice_transactions.sqlavailableSharon/Ann

holdings_electronic_access.sqlnot availableNatalyaNext Step: Sharon to reach out to Stefan and Nassib for help with this one
holdings_statistical_codes.sqlavailableNatalyafixed for data types, submitted PRhttps://github.com/folio-org/folio-analytics/pull/844
instance_ext.sqlavailableJoanne/Vandana

items_holdings_instances.sqlavailableJoanne/Vandana

loans_renewal_dates.sql - both LDP and Metadblow recordsJoanne

Next Step: Joanne to first work on LDP version and give to Sharon/Vandana for PR

should be using the folio_circulation.audit_loans__ table for the source, not the folio_circulation.loan table; CR184A


openaccess_checklists.sqlnot available 
Next Step: Sharon to ask Stefan to fix this one

low priority - no data in CUL FOLIO Prod

openaccess_publication_request.sqlnot available 

Next Step: Sharon to ask Stefan to fix this one


low priority - no data in CUL FOLIO Prod


po_instance.sqlavailableNatalya/Joanne

Next Step - Natalya to update LDP 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.sqlavailableSharon/Ann

po_lines_vendor_reference_numbers.sqlavailableSharon/Ann

po_lines_eresource.sqlavailableNatalya

po_lines_locations.sqlavailableNatalya

po_organization.sqlavailable -update submittedJoanne/Sharonfixed for data types and extracted more from JSON, submitted PRhttps://github.com/folio-org/folio-analytics/pull/842
requests_items.sqlavailableJoanne/Vandana

users_groups.sqlavailableJoanne/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.