2017-03-10 Internationalization SIG Meeting Invitation and Agenda

TimeItemWhoNotes30 minI18n tab in 2018 DocumentCatePage layout responsive to text direction for selected language moved to v1 because it's being considered in FOLIO UI componentsAdded row clarifying that FOLIO won't translate user-generated content (e.g. Notes) or library resource metadata (unless translation is supplied in source data)25Discussed other tab themes in document to see if any had I18n implicationsAnn-MarieMiscellaneous other international implications (not necessarily i18n - most should be covered by other tabs)What EDI standards are used in the middle east? Edifact is default standard. Between that and API communication, we should be covered globallyNeed to have flexibility in Acquisitions workflows, and even allow FOLIO use without AcquisitionsThere are many libraries that have campuses/branches in different countriesThey are getting by today in one way or another (separate systems, single system in English, other?) but FOLIO needs to do betterWill one language per tenant really be sufficient (even just for v1)?Implications for the consortia discussionThere are international considerations for data privacySome countries require data centers to be in a certain locationSome customers are satisfied if they can just get local backup5Planning for next meetingCateWe'll synch with Peter and rest of team by email to see if anyone has any additional agenda items for next weekIf not, we may pause meetings until we have something more to discuss (e.g. implementation options, handling of Asian languages etc.) Action items Cate will see if internationalization needs should be added to the consortia research questionsCate will send Harry a link to these notes so he can process anything that isn't already included in the other tabs