2020-11-05 Metadata Management Meeting notes

Former user (Deleted)

• Laura asked that people check their names in the meeting minutes
• There is still a need for testers for Data Import and Circulation
• Introduction of proposed governance model
  
  • Elections
  • Organizational structure
• Cate Borromeo gave an update on capacity planning team.
  • Honeysuckle - Due to be released November 23.
• Elastic Search discussion and how it relates to FOLIO is being planned. Magda is the PO for Elastic Search
• Still looking for members for the privacy SIG.

Reminder: remember to check your name below (or add your name if it's not there) when you attend

Productivity statistics working group is making progress and will have an update in the next few meetings.

005: "The date and time of the latest record transaction and serves as a version identifier for the record."

• Data Import and QuickMARC are not updating the 005, this is consistence with several systems.
• Optimistic locking comes in to play with this: Are two people trying to edit a record at the same time. If the 005 field 
• The MARC 005 is not the same as the metadata on the FOLIO Instance date/time. 
• There is existing metadata that will show updated data for a MARC record. This is from SRS. Does not always mean MARC data has changed, but that is true 99% of the time. Example:
  
• Should we be updating the 005 in FOLIO?
• Will the LDP be able to query the data above?
  • Situations: Sending out records for authority updates
  • Comparing dates with OCLC's 005
  • We need to be able to know when the MARC record was last changed, regardless of where it was changed. The more precise we can be, the better off we'll be (Christie)
  • In chat -
    • Jen Colt - For Cornell every time we ETL we check the 005 date (Voyager)
    • Raegan Wiechert - In our Sierra we used the bib record status field (but again, people had to pay attention to it)
  • When we export, and updated 005 is the only way to know if there's been a changed to SRS when it comes to reimporting the record.
  • Ann-Marie will write stories to update the 005 on data import and with QuickMARC
  • For institutions that do not want the 005 to change, it can be corrected. The protected field settings will be honored and extend to the 005.
  • Jenn Eustis (chat) - "Isn't this the audit system that we talked about way back when? I was thinking that having an audit system that had versions of the record associated to a trigger of the type of change. The only analygoy I can find is that when you commit to GitHub there's a commit message. In our cases, this could be authority update, marc field update, etc."
  • Lisa Furubotten (chat) - " Is there a point where tracking so many changes is a data load burden on the system?"

Slides

Felix Hemme

Theodor Tolstoy