Open albig opened 3 years ago
Unlike the old module, (re-)indexing has to be done asynchronous, because of the rather long runtime. I suggest implementing an indexing task for the TYPO3 scheduler (see #454). The backend module could trigger this task and provide parameters (i. e. which document/collection to index).
Good point. I remember this odd behaviour. Of course this must be done somehow asynchronously. The solr extension may be a starting point. It shows progress bar in the scheduler task list.
Description
Up to Kitodo.Presentation 2.x we had a very basic TYPO3 backend module. It was possible to
The functionality was the same as the CLI jobs. But the big difference is, that you can give TYPO3 backend users (editors) the rights to use this module. But you cannot enable editors to use the CLI jobs.
This module should be added again to make the daily work with Kitodo.Presentation easier and smoother. It should be the central point for editors and administrators.
The following functions should be provided:
The backend module should be written with Extbase/Fluid using Bootstrap which is already present in TYPO3 backend for this purpose.
Expected benefits of this development
Estimated Costs and Complexity
This is my rough estimation of costs in PT (day work):
sum: 5-8 PT
It's a mid range development project.
Related Issues