Versions Compared

Old Version 7

changes.mady.by.user Sharon Wiles-Young

Saved on

compared with

New Version Current

changes.mady.by.user Charlotte Whitt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Date

Charlotte Whitt ~ 20


Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on AWS from 2022 onwards: https://recordings.openlibraryfoundation.org/folio/metadata-management-sig/

Discussion items

NotetakerAlissa Hafele 


Announcements


No meeting December 22 or 29

FOLIO Prioritization and Roadmap Working Group is looking for volunteers Convener: Jesse Koennecke

Reporting SIG - Looking for new members. Interested? please reach out! Convener: Angela Zoss

PC update

Sharon Wiles-Young 

SIG updates today at PC meeting; Some highlights:

  • Jesse is calling for volunteers for the Roadmap and Prioritization group;
  • Implementers Group Tara Barnett will be the new convener of the SIG;
  • App interaction has opened the slack channel and are looking at workflow tools and how other institutions are using workflow tools;
  • RA SIG have another PO leaving; looking for more
  • Reporting SIG Sharon B. will help to co-convene this SIG and call for more members on this SIG
  • PC report- Next meeting discuss the Evaluation Process for New FOLIO modules <insert link> Sharon Wiles-Young ; January 12th will be a cross council meeting PC,TC,CC
  • Results of Nolana BugFest very positive

Kristin shared the summary of SIG conversations and action items

  • Action items for PC- Improve communications PC-SIG; make the SIG updates more useful such as needs of SIGs for example- reporting needs across FOLIO; balance needs and visions of each SIG-maybe Roadmap will help with this; Project needs to have something to replace sprint reviews; resources needs and gaps and expectations example courses (reserves development); need for better test data and work on reference environment; onboarding working group help with connecting people resources with the needs and gaps in development and help with participants to feel empowered and to speak up up; Transparency in allocation of development resources. Clear relationship between SIG effectiveness and satisfaction and PO/developer resources given to the areas of concern. 



Jennifer Eustis 


MM SIG Release Note & Other Highlights

  • LDP Updates - can use snapshot. Talk with Nassib for access
    • Ldpmarc 1.6 released
    • Small working group on data normalizations
  • In transit report failed in Nolana bugfest - still in progress
    • Work currently deferred to Orchid
Effective call number get mixed up when using Hebrew or Arabic characters
Martin Scholz 

Charlotte Whitt 

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIIN-2236
 

Demo by Martin Scholz.

may be of interest for understanding RTL in Unicode: http://unicode.org/reports/tr9/#Formatting and https://unicode.org/reports/tr9/#Markup_And_Formatting

  • Found during Nolana bugfest, Test - "Display effective call number string on item record".
  • Assumed scripts with left to right are used in call number fields. If you use, e.g. Arabic or Hebrew, the fields get mixed up.

Image Added

  • Stems from how unicode defines how right to left characters should behave when inline with left to right.
  • Per rules it is correct, but results in wrong order of when effective call number is computed
  • Are there any use cases for this? Is this required to fix?Not likely in German libraries
    • Not likely in German libraries
    • Cornell - no
    • 5C - no
    • Chinese libraries using FOLIO? not likely an issue due to directionality
    • Felix will ask HBZ
  • Further discussion
    • Flexibility in general would be desired, e.g. customizing effective call number
    • Having the ability to omit fields like the enum./chronology from effective call number would be interesting as well
    • Charlotte will file a ticket <insert link> Charlotte Whitt 
    • Would be good to consider consortium and have this at, e.g. the campus level






Chat:

08:31:27 From Felix Hemme (ZBW) to Everyone:
    Link to agenda: https://folio-org.atlassian.net/wiki/x/pjhH
08:31:53 From Alissa Hafele to Everyone:
    I can do it
08:32:15 From Felix Hemme (ZBW) to Everyone:
    Thank you Alissa
08:32:36 From Alissa Hafele to Everyone:
    No problem!
08:57:48 From Laura (she/they) to Everyone:
    we don't use these scripts in our call number data, just the bibliographic/instance data
08:58:13 From Felix Hemme (ZBW) to Everyone:
    I will ask Christin from the hbz library consortia about potential use cases. I've heard they are in contact with a special library with a large hebrew collection.
08:58:14 From Jennifer Eustis (she/her) to Everyone:
    It's not a use case here in the 5C as far as I know. Our call numbers are either LC, cutter and don't use the scripts
08:58:20 From Felix Hemme (ZBW) to Everyone:
    But IDK about the call numbers
08:59:27 From Sharon Wiles-Young to Everyone:
    sorry I have to run to another meeting. Thanks
08:59:29 From Lynne Fors to Everyone:
    Do any of the Chinese Folio libraries use non-Latin characters in their call numbers?
08:59:37 From Lisa F. (Cataloging) to Everyone:
    It's the series/serials - if there were a case where the numbering caption was in a script - but I don't think anyone does that, we use the latin captions for numbering (we wouldn't have been able to print labels otherwise)
09:00:03 From Charlotte Whitt to Everyone:
    I’ll also talk with Peter Murray who works with Massoud M. AlShareef
09:05:15 From Felix Hemme (ZBW) to Everyone:
    Having the ability to omit fields like the enum./chronology from effective call number would be interesting as well
09:09:29 From Jennifer Eustis (she/her) to Everyone:
    Thank you Charlotte
09:09:43 From Alissa Hafele to Everyone:
    Please add me as well
09:11:05 From Lisa F. (Cataloging) to Everyone:
    Sorry, I wasn't clear: there are classed together series where the call number on the individual piece record is actually in the form of 'R12 .B38 no. 1'  - I suppose it's possible for numbering to be non latin, but I've never seen one.
09:11:11 From Charlotte Whitt to Everyone:
    Yes, I’ll do that Alissa