2018-03-26 - Data Migration Subgroup Notes

2018-03-26 - Data Migration Subgroup Notes

Date

Mar 26, 2018

Attendees

  • @Tod Olson

  • @Wayne Schneider

  • @Anne L. Highsmith

  • @Ingolf Kuss

  • @Uschi Klute

  • @Charlotte Whitt

  • @Christopher Creswell

  • @Dale Arntson

  • @Lina Lakhia

  • Matt Harrington

  • @Michelle Suranofsky

  • @Sharon Markus

  • @Theodor Tolstoy (One-Group.se)

  • @Wayne Schneider

Goals

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

5min

Determine note taker



@Anne L. Highsmith (first draft from @Tod Olson)

5min

Review related issues from Reporting SIG meeting today:

  • Data integrity

  • User Management (thanks, Anne!)

@Tod Olson



45min

Review composite spreadsheet to compare field terms, note any questions on discussion thread. Determine whether FOLIO has missing fields.

Links:

 @Anne L. Highsmith

 Will scrap question in discuss about what elements can be left behind, sites will make that call.

Review of data elements, start about line 48:

  • Patron Title (Mr., Mrs., Dr., Prof., etc.) - serveral systems have this.

  • Patron SSN - let's make that red, plan to not have in FOLIO because is quite dangerous.

  • How many external IDs? Already have 3.

  • Home location - where did the patron date come from?

    • was this created manually or by batch load?

    • Chicago finds operational use in knowing the source of the patron, manually entered or from campus IdM feed?

    • Some places report out stats on where users were created.

  • patron modify operator ID - do we need to migrate this last-modified-by? Some places may want this to be the last change in the old system.

  • patron modify location - where what this record last modified? Can probably leave behind.

  • patron current charges - migrate from old system or calculate in FOLIO?

    • Resource Access has a stake

    • There's a sense dangerous to migrate data that may have different values in the new system.

    • May not belong in the Patron data, does not contain all of the info to justify the amount.

    • The following seem to follow the same logic:

      • patron note count

      • patron current hold shelf

      • patron recalls placed

      • patron holds placed

      • patron items recalled

  • patron historical charges - running count of loans,

    • historical loans will be purgable by patron

    • Question for Resource Access

  • Other not migrate, very Voyager-specific:

    • patron counter reset down to patron self-shelved db

  • patron PIN - Good question

  • patron suspension data, patron demerits - Voyager-specific

  • patron SMS number - seems identical to patron mobile phone

  • Reporting demographics, may want to migrate:

    • patron Major

    • patron Department

    • Patron statistical code

  • Patron note: differnt types of notes in different systems, need a discussion

    • some may be notes to staff, or to staff, or to

    • Lehigh uses patron notes to store a lot of info from the IdM system, including Major!

    • Generally used by staff

Ended part way through Sierra, row 100

2min

Who convenes next week?





  • 2 April, day after Easter, is a holidy for many people

  • Next meeting in two weeks, 9 April.

  • @Dale Arntson volunteered

3min

Future meeting topics



  • Finish review of user data Composite spreadsheet

    • Matt Harrington will review user priviledges and add to spreadsheet

  • Document areas of data integrity concern, communicate with Reporting SIG

  • How do we deal with historical

Action items