dpla-monthly-emails

You can automate monthly scheduling emails by running a script that reads hub configurations and generates date-specific email drafts for partner distribution. The workflow produces previewable drafts in the scheduler/emails directory before sending.

Yes, you can preview an email draft before sending. The workflow implements a deterministic preview step that generates a month-specific outline with the hub list and date range, storing it as an artifact for review prior to final dispatch.

Yes, you need AWS SES configured to send the final automated notification emails. The script relies on the boto3 library to interface with AWS SES for dispatching the scheduling emails and managing CC'd recipients as specified.

Config-driven scheduling determines email recipients by reading the i3.conf configuration file. This file specifies hub inclusion lists and schedules, ensuring the generated emails contain the correct date ranges and hub lists for the selected month.

The best way to generate a month-specific email outline is to execute the scheduling_emails tool, which reads hub lists from configuration and automatically produces a draft summary with the correct date range for your chosen month.

A limitation of the monthly email workflow is its strict dependency on the i3.conf file for environment configuration and hub scheduling data, meaning incorrect configurations will directly impact the generated date ranges and recipient lists.