Roadmap 24.11

=== What is the roadmap? ===
For each release the community, especially the development team, will define milestones/goals that they aim to reach.
There is no guarantee that all of these will make it into a release. In some cases progress on certain projects will be made over multiple versions or projects will have to be postponed.
But it helps us to get a common understanding about important tasks and to work on achieving them together. Also, roadmap project will be prioritized in certain circumstances.
=== Schedule ===
*Deadline for project proposals: 2024-07-02 (existing entries can be amended/updated, no new projects should be added)
*Discussion: 2024-07-03 at the Development IRC meeting 3 July 2024
=== How to use this page ===
We will change things a little after some discussion we had at the Marseille hackfest. The roadmap is now split into 2 sections:
*Community development projects
*Individual development projects
Please see the sections above the tables for more information on the requirements for each table.
Columns
*Schedule: This can be used to indicate a time frame for the implementation of the project or any scheduled dates concerning it.
*Status: For now the status should be "Proposed". Later we will move to "Accepted", "In progress" etc. and then hopefully to "Done".
*Category: Categories to help a bit with sorting. Examples: Infrastructure, Feature, Architecture
*Project lead: First point of contact, coordinator, might also be main developer.
*Supporters: Supposed to help with testing, developing, QA etc. The more the merrier, but putting your name equals commitment to actively work on the project.
*Link/Bug: This should be a link to where interested parties can find more information. It can be a bug, pad, taiga issue, etc.
*Project description: Short description of the goals of the project. What's included and what's not? Please try to make it easy to understand without requiring to read code ;)
===Proposed community projects===
Proposing a project
There are no requirements for proposing a project, but it will need to meet some criteria to be accepted as a community project. Community projects are bigger projects that we need to achieve together. They might require extensive work and need wider support and planning. They might even require scheduling and freezing or slowing down main for an agreed on time frame.
Requirements are at least one project lead and 2 supporters, all from different organizations. 
We will discuss the proposed community projects at the Development meeting. We may prioritize and postpone projects depending on the resources they require and that can be made available. 
Supporting a project
You can add yourself as a supporter, if you are able to support the project actively during this cycle. This can include development, testing, and code review. Please don't add yourself if you won't be able to contribute.
Important: Please use the roadmap_24_11 keyword in Bugzilla to highlight any bugs/patches related to these projects after they have been accepted.
Schedule	Status 	Category 	Project lead 	Supporters 	Link/Bug 	Project description
 	Pushed to main 	Templates 	Owen Leonard 	Martin Renvoize
Paul Derscheid	35402 	Update the OPAC and staff interface to Bootstrap 5
 	Partially pushed	ILL 	Pedro 	ByWater
PTFS Europe
Tomas	35604 	Interlibrary Loans Rethink
 	In progress 	New feature 	Pedro 	PTFS Europe
Paul Derscheid	 	Add a fully fledged plugin store to Koha
 	In progress 	Project processes 	Tomás Cohen Arazi	Jonathan, Mason 	 	CI pipeline for running tests > building packages > building official container images
 	In progress 	Architecture 	Marcel 	Nick, Tomas, Paul, Martin	30888
20271 	Decide on how to handle Tombstone tables in the database
 	In progress 	New feature 	Martin Renvoize 	Matt Blenkinsop 	 	Enhance overdue notice triggers to allow item type level rules
 	BLOCKED 	New feature 	- 	PTFS Europe 	 	Add support for ILL as a supplying entity
 	BLOCKED 	Acquisitions 	Tomas Cohen 	ByWater 	19358 	Linking purchase suggestions with orders
 	? 	Codebase internals/API	Tomás Cohen Arazi	 	 	Migrate to OpenAPIv3. Caveats are plugin support needs to be thought about.
 	Proposed 	Holds 	Nick Clemens 	 	20747 Crowdfunding Page	Allow LocalHoldsPriority to fill by hierarchical groups
 	Proposed 	Administration 	Kyle Hall 	 	37248 	Power to the Users
 	Proposed 	Templates 	Jake Deery 	PTFS Europe
Owen Leonard 	37240 	Settle on a consistent style for data search and filter displays: discussion
Come up with a clear guideline, create a template component that can be re-used and then work through the codebase migrating existing implementations to the template
===Proposed individual projects===
Proposing a project
There are no requirements for these projects. You can use this table to advertise work you have planned for this development cycle. Please include enough notes/information on what this project is about and a link where interested parties can find more information. This could be a bug, pad, taiga issue, etc. 
Supporting a project
You can add yourself as a supporter, if you are able to support the project actively during this cycle. This can include development, testing, and code review. Please don't add yourself if you won't be able to contribute. 
Schedule	Status 	Category 	Project lead 	Supporters 	Link/Bug 	Project description
 	Pushed to main 	Searching 	Brendan Lawlor 	CLAMS 	Bug 14322 - Can't link to an item search	Add a button to item search results page to copy a shareable link. When the shareable link is visited the item search form is prefilled. Bonus if the link can include the current state of the data table too.
 	Great progress 	Infrastructure 	Martin Renvoize	Katrin 	Dashboard 	Enhancing the community dashboard and encouraging more use of it for selecting bugs to work on
 	Partially pushed	Circulation 	Martin Renvoize	ByWater, PTFS Europe, Biblibre	Dependency tree 	Continued work on the bookings functionality
 	In progress 	Acquisitions 	Matt Blenkinsop	ByWater, PTFS Europe 	 	Rethinking Acquisitions from the ground up
 	In progress 	Enquiry management	Martin Renvoize	PTFS Europe 	Dependency tree 	Enhance catalog concerns to become a general ticketing/request/enquiry management solution
 	In progress 	Refactoring 	Emily Lamancusa	 	15278 	Port default notices from bespoke syntax to Template Toolkit
 	Proposed 	Inventory 	Nick Clemens 	ByWater, PTFS Europe 	12733 Crowdfunding Site 	Create an interactive inventory tool
 	Proposed 	Displays 	Nick Clemens 	ByWater 	Document 12141 	Create a new module for handling displays of items
 	Proposed 	Acquisitions 	Tomas Cohen 	ByWater 	31024 	Switch to the REST datatables for suggestion management
 	Proposed 	Acquisitions 	Kyle Hall 	ByWater 	35465 
Crowdfunding Site 	Ability to select multiple funds for a single order
===Questions===
You can add any questions about the projects above here.