Summary: | Add pipelines support to Koha | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
Component: | Staff interface | Assignee: | Jake Deery <jake.deery> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, magnus |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38115 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | |||
Bug Blocks: | 37248 |
Description
Martin Renvoize (ashimema)
2024-12-05 07:51:18 UTC
Interesting! Is this just an idea, or something you plan working on? It's part of an evolving idea.. Jake is working on a specification now. It comes out of a series of 'Power to the user' developments that ByWater are sponsoring us to do which include making a generic FTP configuration page (pulling a lot of the EDI Transport code into a more generic module), and then allowing said (S)FTP setups to be used by Reports, Exports, Imports, EDI, MARCOrdering etc etc. It basically occurred to me that if we created a pipeline builder utilising some of the existing background job infrastructure for describing 'tasks' and added some of my crontab plugin work for setting initial triggers we could have pipelines that trigger at certain times and then use background jobs to, for example, run a report -> FTP the result somewhere... similarly one could trigger a FTP download -> load the downloaded file via patron load, marc import or whatever.. etc, etc. |