PC action items from 2023 Things that Could be Better About FOLIO

	A	B	C
1	Name	Feedback Item	Possible actions/Notes
2	Alexis Manheim	Courses app: get a PO; have it more tightly integrated with inventory, where statistics can be kept; improve workflow efficiency.	How to facilitiate work on Courses and other orphaned apps
3	Alexis Manheim	SIGs.. I think they need a clear charge and direction from the councils.	See #17 under Governance
4	Kristin Martin	SIG reviews - maybe WOLFCon or an upcoming SIG meeting in the fall would be a good opportunity to see if our revamped SIG relationships have improved things. Given where FOLIO is in development, are SIGs still the best way?
5	Kristin Martin	Review of new implemented institutions where we don't have much contact. Could PC/CC members reach out to say hello, see how things are going, encourage more involvement?	Like a mentor/metee relationship
6	Martina Schildt	Lack of participation, onboardnig new members, more institutions participating in the community: as POs, in SIGs/Councils, as developers and testers.	Better calls for specific roles and SIG needs List vacancies on wiki page Revive onboarding group
7	Martina Schildt	Prioritization	Continue evaluating new voting process (tested ni ACQ SIG) - is in progress Extend to other apps
8	Charlotte Whitt	FOLIO needs to actively work on being organization neutral. The FOLIO community should be a place where the focus is the good and future of the FOLIO project. Not favoring a particular vendor or library.	Maybe reserve a % of development resources, which can be allocated to work being proposed by SIGs
9	Charlotte Whitt	The library community should fund and run a development team.	We used to have developers hired by the library community. This could be reintroduced.
10	Owen Stephens	Governance: 9. FOLIO discussions are dominated by a nonrepresentative and internally focused group	Look at a programme to encourage participation in SIGs and PC, focussing on under represented parts of the Folio community. Options to consider could include: mentorship, bursaries (either for general participation, or for specific purposes such as attendance at WolfCon), alternative methods of contributing/raising topics (e.g. written submissions)
11	Owen Stephens	Documentation: 1. Hard to find accurate information	Expend effort on: Fixing wiki indexing issues, Standardising Jira labelling practices and language used, Understanding what level of end user documentation is required beyond the docs currently at docs.folio.org
12	Jennifer Eustis	Reporting (12). This also fits in with Market Fit and Maturity (8). Libraries expect to be able to run reports.	How do we address this issue where there is really no central reporting solutions?
13	Jennifer Eustis	Data Import (14)	Follow up on ARLEF meeting and with PO. How can we fund more development time?
14	Jennifer Eustis	Market Fit and Maturity (8) point on excessively focused on legacy systems and spending time on old workflows.	I've heard from many that it is frustrating to work with eResources in Inventory. Many feel that Inventory was only designed for print. How do we ensure that FOLIO is adaptable to new workflows and that these are cross app if necessary?
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100