Skip to end of banner
Go to start of banner

2022-07-25 - Data Migration Subgroup Agenda and 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

Version 1 Next »

Date

Attendees



Meeting Link

Link to Recordings

Discussion items

Time

Item

Who

Notes


Optimisitic locking workarounds


Could disable all through testing phase, and always set _version = 1.  Or at least could test this.  Did anyone (especially Stanford) try this?


Migration status/checkin



Loading loans

For renewals, Have you tried migrating the loans as though they were were new and then changing both the loanDate and the dueDate via PUT, along with renewals count? That should avoid the immediate age-to-lost issue, and you don't have to create historical calendars to cover all of you possible loanDates. Your loan action history will indicate the change, but you should also be able to add an action comment when you make the update indicating that it was a migrated loan. This is roughly the technique used in folio_migration_tools .









Action items

  •  
  • No labels