| Summary: | Create runtime parameters on the fly | ||
|---|---|---|---|
| Product: | Koha | Reporter: | George Williams (NEKLS) <george> |
| Component: | Reports | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | cbrannon, dcook, jonathan.field, kebliss, lisette, martin.renvoize, rcoert, sbcornell |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Crowdfunding goal: | 0 |
| Patch complexity: | --- | Documentation contact: | |
| Documentation submission: | Text to go in the release notes: | ||
| Version(s) released in: | Circulation function: | ||
+1 Maybe a variation of this would be something like:
WHERE biblio.title LIKE CONCAT("%", <<Choose one|["Coeur d'Alene Library|COEUR", "Liberty Lake Library|LIBLAKE", "Post Falls Library|POSTFALLS"]>>, "%")
This iteration would allow you to define what the options look like in runtime, and what value is actually being used.
+1 - I'd love to see this functionality added to Koha. I would also love to see this implemented. I think there are couple of other bugs related to runtime parameters, but they are from 2020. |
I was just thinking how helpful it would be if we could create runtime parameters inside of a report. What I'm thinking is something like this WHERE biblio.title LIKE CONCAT("%", <<Title contains one of these words|["good", "box", "friend"]>>, "%") creating a drop-down that has the three options: free, good, box. Being able to create parameters would open up a lot of new options with writing reports.