Versions Compared

Old Version 50

changes.mady.by.user Sharon Helen Markus

Saved on

compared with

New Version 51

changes.mady.by.user Sharon Helen Markus

Saved on

Key

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

...

  • Given increasing concerns about data privacy, is data anonymization on the roadmap and how will it workmetadb software development roadmap? If so, when do you expect it to be released?
  • There is some loan anonymization functionality in FOLIO settings and there are plans to do the same for Requests
    • Is metadb anonymization being developed with that interdependence in mind, or is it going to be an independent feature?
  • Will there be a feature to make patron identifiers (e.g., user_id, requester_id) NULL in historical rows?
  • If we need to recover from our data anonymization processes, what will be required and what are our losses?Should we take snapshot of the database every time we run update scripts to anonymize data by replacing patron identifiers with NULLmight we lose?

User Permissions

  • Support for more granular permissions has been added in Metadb 1.4: see https://gist.github.com/nassibnassar/9e8e63383db1dac0634b0cf371254dec
  • Are there ways that this new functionality can support our goal of removing access to patron identifiers in our Metadb reporting database? 
  • Does this mean we can use postgres permissions, groups, etc.?
  • Would it be possible to develop user permission functionality for Metadb that corresponds to user permissions in FOLIO?

...

  • When we look at the sets of 3 tables in each application area (e.g., loan__ , loan__t , and loan__t__), we get different totals when we count the id rows. Why would this be? Is this happening because just first level of json fields are extracted into the __t__ table?
  • Is there a relationship among tables during the ETL process? Specifically is the main table , does it work like this, or another way?
    • main table (loan__) the json source
    , then the
    • current and historical table
    is made from main, and the current
    • (loan__t__) is created from the main table  
    • current table (loan__t) is made from the current and historical table (loan__t__)?

History

  • Will there be a feature to turn off the historical row creation for Metadb (as you could for LDP)?

...

  • What is in the zzz_ tables in Metadb?  e.g., zzz___loan__t___
  • Should we remove these


Metadb Links

Metadb Project: https://github.com/metadb-project/metadb

...