https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43638 Bug ID: 43638 Summary: Add core support for scheduled/automated patron image import Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs@lists.koha-community.org Reporter: martin.renvoize@openfifth.co.uk QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle@bywatersolutions.com Target Milestone: --- Depends on Bug 43637 (refactor patron image upload into a reusable engine class and background job), which this builds on. This bug is the scheduling half of that work: automatically importing patron images from a remote/local file source on a schedule, the same way Bug 43616 added scheduled/automated patron record import on top of the existing, unmodified Koha::Patrons::Import engine. Planned approach: - New patron_image_import_accounts and patron_image_import_log tables, plus Koha::PatronImageImportAccount(s)/Koha::PatronImportLog(s) object classes, mirroring Bug 43616's own account/log model (name, file transport, matchpoint, active flag, per-(account, filename) idempotency). - A new Tools page ("Schedule patron image imports") for configuring accounts - a smaller option surface than the patron-import case, since image import has no equivalent of default values or preserved fields. - A new misc/cronjobs/patron_image_imports.pl cronjob polling each active account's configured Koha::File::Transport, calling Koha::Patron::Image::Import->import_batch (from Bug 43637) for zip archives it finds, and also handling loose image files sitting directly on the transport (matched by filename stem against the account's chosen matchpoint) - not just zips, since an unattended feed may not always package images into an archive. No code has been written yet for this bug - filing it now to track the plan and its dependency on Bug 43637 before design/implementation begins. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.