A dag_id names an Airflow DAG. Define it when creating the DAG object, alongside settings such as start_date and schedule. With schedule set to None, the workflow can be triggered manually from the Airflow UI. section 2.2
Naming a rocket-launch workflow
A download-and-processing workflow can define its DAG with `with DAG(dag_id="02_download_rocket_launches", ..., schedule=None):`. Tasks such as `download_launches`, `get_pictures`, and `notify` then belong to that named workflow and run in dependency order. section 2.2
