dpla-monthly-emails

Generate and distribute monthly DPLA hub scheduling emails from i3.conf.

35|12|Updated Jan 10, 2017

Search Tags:#automation #workflow #email #scheduling #notification #hub #monthly

Ready to run

npx skills add https://github.com/dpla/ingestion3 --skill dpla-monthly-emails

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dpla-monthly-emails
Source: https://github.com/dpla/ingestion3/tree/main/.cursor/skills/dpla-monthly-emails
Command: npx skills add https://github.com/dpla/ingestion3 --skill dpla-monthly-emails

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, and includes scripts (resource) components.

What problem does it solve?

Automates the generation and distribution of monthly hub scheduling emails to DPLA partners based on i3.conf.

Core Features & Use Cases

Preview and draft: Produce a month-specific email outline including the hub list and date range, ready for review.
Send automation: Send the final scheduling email via AWS SES with CC’d recipients as specified.
Config-driven scope: Reads hub schedules from i3.conf to determine inclusion and supports per-month activation.

Quick Start

Run the scheduling_emails tool to generate and preview the monthly hub summary email for a chosen month.

Frequently Asked Questions about dpla-monthly-emails

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate monthly scheduling emails to partners?▼

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.

Can I preview an email draft before sending it to partners?▼

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.

Do I need AWS SES to send automated notification emails?▼

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.

How does config-driven scheduling determine which hubs receive emails?▼

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.

What's the best way to generate a month-specific email outline for a hub list?▼

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.

Are there limitations to the monthly email automation workflow?▼

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.