2018-07-30 - Data Migration Subgroup Agenda and Notes

There is a wiki page available to track schedules for completion of gap analyses. The page is here

-Charlotte: inventory gaps for Users is done

-Sharon: Chris Manly said Users SIG had reviewed the data elements, but needed more broad representation

-Patty: Work is iterative, may be fine to follow up on gaps in users later

-Several: we need to make the best data model, how easily can it be modified/updated?

-Wayne: if we are talking about schema changes, we should not wait for it to be perfect, updating a schema is not hard but removing data elements is a "breaking" change, but adding data elements is not because it doesn't impact data

-Tod: Perhaps have a different representation for the work on the schedule

-Dale: Loans data elements Gaps Analysis will be due August 13

Discuss gap analysis for loans and handoff to RA sig. Here is a link to the spreadsheet.

Uschi: Concerning the gap fields "date of previous reminder" and "number of reminders":
I have noticed that so far only overdue notices / overdue fines are taken into account. Reminders (with reminder fees) are configured for the majority of German libraries; this is specified in the state-wide fee regulations.
In the "Glossary of terms" (lines 476/477) I have added two definitions: https://docs.google.com/spreadsheets/d/17kRyXflyV-TZyS2sUbS1zTY1mZ83QUT6JxHJnr0w7hs/edit#gid=1426404785
The topic concerns not only the data fields, but also the procedure of patron notices.

Jana (RA SIG) already informed Andrea about this.

-group reviewed "gap" worksheet on composite_to_folio_loan spreadsheet; see worksheet for details

-reviewed reminders/overdue notices

-how should historical loan information be stored? should it go into the data warehouse?

-what is our overall plan for historical data archives?

Look at that state of the gap analysis for Requests, and see what is still needed. Here is the spreadsheet