Page Comparison

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

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>; 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; 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 

Charlotte Whitt 

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
  • Fields are concatenated with white space and follow the unicode rule that says if "neutral" characters eg. numbers, should be treated also as right to left
  • https://unicode.org/reports/tr9/#Markup_And_Formatting

Are there any use cases for this? Is this required to fix?