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