Closed cbleek closed 7 years ago
Very good!
Concerning the last point: I do not believe we need to "remember" (which would mean: log) which job was already sent to which subscriber. At greenjobs.de we keep for each subscription, when the last check for suitable jobs was done and when the last e-mail was actually sent. This way we can easily search for the jobs that were published (or changed - if that is wished) since the last check. Keeping both the check- and the send-timestamp allows us to track, which subscriptions have not received an e-mail in the last x weeks (which happens usually because the search criteria were to narrow). We can then send them e-mails to let them know that they may want to widen their search criteria.
I do not say that YAWIK has to do it the same way. But logging each job for each subscription seems too much overhead for such a simple task.
NB: We also send out news/info with the Job-Emails. While we currently apply the same logic (current news, which were published after the last check), we sometimes wish, we had a logging mechanism here, which would allow us to e.g. "send this news item up to 3 times to the same subscriber".
Why easy if complicated is another option:-)
We'll implement it the way you described.
Am 04.04.17 um 20:33 schrieb Miroslav Fedeleš:
- How should be a language determined for an email sent via the cron?
We'll save the language in the search profile entity. If the user creates a search profile using the "german" language, we save "german" as language to use when creating the mails
- How should be displayed facets checkboxes (there may be tens of checkboxes.) in the lightbox form?
We'll use hidden fields. Selected facets should be listed.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/cross-solution/YAWIK/issues/342#issuecomment-291592007, or mute the thread https://github.com/notifications/unsubscribe-auth/AA0aEkM-3oi32WJKz3WwTZNrXT00_LPtks5rso0LgaJpZM4MSLKt.
-- Cross Solution, Carsten Bleek Tel: 069-71910361 Fax: 069-71910369 bleek@cross-solution.de http://cross-solution.de
@cbleek Great, I would solve the both points the same way.
Documentation will be created at:
http://yawik.readthedocs.io/en/latest/modules/jobs-by-mail/index.html
a JobsByMail module should offer a form which gives an anonymous user the possibility to enter his email Adresse and a job search. The formular should implement the CustomizableFieldsetInterface.
It should be possible, to open the formular in a lightbox.
It should be possible to prefill the job search data. That means, if a user has done a job search and clicks on a "Jobs By Mail" Link, the formular is prefilled with the last search.
It should be possible to prefill the users email address. If an authorized user clicks on a "Jobs By Mail" Link, the email field should be prefilled with.
a cronjob should do the search. The timestamp of the last search has to be stored in the subscribers profile
The Jobs, which have been sent have to be remembered, to avoid sending Mails for a job twice.The module should be created in the repository https://github.com/yawik/JobsByMail
Example of possible "Jobs per Mail" Feature integration.