Skip to end of banner
Go to start of banner

2019-08-05 RPWG Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Date

Attendees

Discussion items

ItemWhoNotes
Attendance
Update Attendee List
Action Items
Review and update Action Items
New Strategy for LDP Data Architecture RolloutNassib
  • reporting issues with technical dependencies on FOLIO core development ("blockers") will not be resolved in time to support an LDP January 2020 Go Live with functionality we would like (i.e., star-based schema, api schema changes, api documentation support)
  • new plan proposed to wait on star-based schema and deliver LDP in a different way
  • mirror Folio's JSON data in the LDP database, while still retaining historical data by adding row_effective and row_end date/time stamps, and a row_current flag to make it easy to filter out old versions
  • pull out the most useful fields as relational columns, to make them available to reporting tools
  • provide immediate access in LDP to all data from FOLIO apps
  • impact on data analysts
    • using PostgreSQL's JSON query syntax on mirrored FOLIO JSON data
    • SQL requires working with fields in nested tables
Next Reporting Data Models to DeliverAll

Sharon suggests we ask Nassib to build these reporting data models first (using the new approach):



Questions:

What do RPWG members think of this as our first priorities?

Would the prototype developers like to develop the SQL queries for each of these once the data models are done?

For our next meeting...

Future Topics:

Next meeting date:


MARC Data Proof of Concept in LDPNassib


Action items

  •  Angela to work with small group to look at Resource Access clusters
  •  Sharon to work with small group to look at Resource Management clusters





  • No labels