Skip to end of banner
Go to start of banner

2018-07-09 - 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

« Previous Version 7 Next »

Date

Attendees


Discussion items

TimeItemWhoNotes
WelcomeDale
  • Volunteer for note taking: Michelle
10 minsInventoryChristie
  • Christie's update on progress in the MM group on the gap analysis:
    • For this review they formed 2 subgroups: Instances and Holdings & Items
    • They'll finish this analysis during their last meeting today (7/9/18)
    • They created two new columns on the 'gaps' tab:
      • MM Sig Review (for comments)
      • Priority (Most ended up being 'go-live', some 'not needed', and some that need further discussion with other SIGs)
    • They will be recommending a new element that was heavily discussed during this meeting:
      • 'Statistical Search Code' – a repeatable element applicable to any instance, holding or item record
      • They found many different uses for this across institutions
      • We wondered about the impact to development
      • How is this element different than tags? → tabs won't be viable for high confidence reporting. The understanding is tags will be more organic and not something for high confidence reporting.
        • If there could be be 'reserved' tags that have an additional layer of control...that might work.
      • The imagined using this field for things like reporting, counting...they need to have a count of titles based on type and items based on type. (just as an example).
      • The data structure doesn't support things we need to know about our data. The Statistical Search Code remedies this.
      • We recognize that data loaders will have to incrementally change as the data model evolves. Once the basic framework of how the data loader will work is established, the changing data model will probably just require changes to the data loader config. (rules).
      • The MM SIG is already having conversations with circ & acqu. SIGs about elements that impact them. (e.g. what does circ need in an item record).
      • Role of Data Migration SIG in all of this? We identified gaps and pass to SIGs. We don't have a hands on role in ongoing conversations as long as SIGs are award of gaps and are making decisions about them...making sure conversations happen where needed.
30 minsData LoaderPatty and TodPatty and Tod have put together a set of user stories for the data loader. They will be a presentation with discussion to follow.

Action item

  • Chris Manly : provide a more detailed description of what LS Tools is used for / what features we need together with the Cornell team.
  • No labels