Change Details

We should investigate adding a queue-running system, similar to what we built for #eventmetrics, for WSExport. This would mean that users would submit a request for an ebook, it'd be added to the queue, and they'd get a status page indicating the progress. The queue would first generate the epub, which would then be available for download, and then it'd generate the derivative formss (PDF etc.) and make those available when done. This would help with errors such as T250614. This system would also effectively give us a cache (e.g. if two people request the same ebook, only one queue process would need to run). Task for that: T222936.

As a Wikisource user, I want the team to investigate a queue-running system, so it can be determined if a) such a system would improve reliability to a meaningful degree, and b) if the work would be manageable and within scope for the team. **Background:** We should investigate adding a queue-running system, similar to what we built for #eventmetrics, for WSExport. This would mean that users would submit a request for an ebook, it'd be added to the queue, and they'd get a status page indicating the progress. The queue would first generate the epub, which would then be available for download, and then it'd generate the derivative forms (PDF etc.) and make those available when done. This would help with errors such as T250614. This system would also effectively give us a cache (e.g. if two people request the same ebook, only one queue process would need to run). Task for that: T222936. **Acceptance Criteria:** * Investigate the primary work that would need to be done in order to implement a queue-running system, similar to what we built for #eventmetrics, for WSExport. * Investigate the main challenges and risks associated with implement such a system * Provide a general estimation/rough sense of the level of difficulty of effort required in doing such work

We should investigate adding a queue-running system, similar to what we built for #eventmetrics, for WSExport. This would mean that users would submit a request for an ebook, it'd be added to the queue, and they'd get a status page indicating the progress. The queue would first generate the epubAs a Wikisource user, which would then be available for downloadI want the team to investigate a queue-running system, and then it'd generate the derivative formss (PDF etc.) and make those available when done.so it can be determined if a) such a system would improve reliability to a meaningful degree, Thisand b) if the work would helpbe manageable and with errors such as T250614in scope for the team. **Background:** We should investigate adding a queue-running system, similar to what we built for #eventmetrics, for WSExport. This would mean that users would submit a request for an ebook, it'd be added to the queue, and they'd get a status page indicating the progress. The queue would first generate the epub, which would then be available for download, and then it'd generate the derivative forms (PDF etc.) and make those available when done. This would help with errors such as T250614. This system would also effectively give us a cache (e.g. if two people request the same ebook, only one queue process would need to run). Task for that: T222936. **Acceptance Criteria:** * Investigate the primary work that would need to be done in order to implement a queue-running system, similar to what we built for #eventmetrics, for WSExport. * Investigate the main challenges and risks associated with implement such a system * Provide a general estimation/rough sense of the level of difficulty of effort required in doing such work