***Please excuse cross-posting***

Dear colleagues,

The MARC Formats Transition Interest Group 
(MFTIG)<https://connect.ala.org/core/communities/community-home?CommunityKey=bfdc5746-8b0b-4d09-a1b5-042f7f95abdd>
 is pleased to hold TWO sessions during the 2024 ALA Core IG 
Week<https://www.ala.org/core/continuing-education/interest-group-week>, 
featuring SIX stellar presentations to explore the current state of the MARC 
formats and their transition in the linked data environment.


Session Title: MARC and Its Transition in the Linked Data Environment


Pt.1: MARC & BIBFRAME -- Wednesday, 3/6/2024 (3-4pm EST/2-3pm CST/12-1pm PST)

#1. “Creating a Hybrid Sustainable Environment for MARC and BIBFRAME” by Adina 
Marciano, Ex Libris

#2. “MARVAlous: LC’s BIBFRAME Journey with FOLIO” by Paul Frank, Library of 
Congress & Doug Loynes, EBSCO Information Service

#3. “Transition Complications” by Jodi Williamschen & Nate Trail, Library of 
Congress

Registration link for Pt. 1: 
https://ala-events.zoom.us/meeting/register/tJArf--trz4qGNKRTwbYdOqiRLgeCTUvDR5c#/registration


Pt.2: MARC to Linked Data - More Possibilities -- Friday, 3/15/2024 (2-3pm 
EST/1-2pm CST/11am-12pm PST):

#1. “Integrating Linked Data into Cataloging Workflows” by Anne Washington, OCLC

#2. “Everything You Wanted to Know About 'Linky MARC' (and Were Definitely Not 
Afraid to Ask, Being Librarians)” by Abby Dover, Northwestern University

#3. “Using Linked Open Data to Build a Culture of Collaboration at Yale 
University” by Timothy A. Thompson, Yale University Library

Registration link for Pt. 2: 
https://ala-events.zoom.us/webinar/register/WN_8W3jzHC_QuStcNIsIcyg3A#/registration

See more details at the ALA Core IG 
Week<https://www.ala.org/core/continuing-education/interest-group-week> 
website. We will record the sessions and post slides and related materials in 
our IG Connect site after the sessions.

Best wishes,

MFTIG Co-Chairs:
Keiko Suzuki ([email protected]<mailto:[email protected]>)
Sai Deng ([email protected]<mailto:[email protected]>)

Reply via email to