darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2025-12-11 15:52:21 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
7ca62ce4cfc3f93719c94e2e5e367ed483a11d6e
notifications-api/migrations/versions/0261_service_volumes.py

33 lines
861 B
Python
Raw Normal View History

Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete.
2019-02-13 14:00:52 +00:00
"""
Bump migration version
2019-02-15 10:09:44 +00:00
Revision ID: 0261_service_volumes
Revises: 0260_remove_dvla_organisation
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete.
2019-02-13 14:00:52 +00:00
Create Date: 2019-02-13 13:45:00.782500
"""
from alembic import op
from itertools import product
import sqlalchemy as sa
Bump migration version
2019-02-15 10:09:44 +00:00
revision = '0261_service_volumes'
down_revision = '0260_remove_dvla_organisation'
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete.
2019-02-13 14:00:52 +00:00
Also store consent to research against a service It makes most sense to collect this at the same time as the estimated volumes. Which means we need to store it somewhere; we can’t put it straight into the ticket.
2019-02-14 23:57:08 +00:00
TABLES = ['services', 'services_history']
CHANNELS = ['volume_{}'.format(channel) for channel in ('email', 'letter', 'sms')]
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete.
2019-02-13 14:00:52 +00:00
def upgrade():
Also store consent to research against a service It makes most sense to collect this at the same time as the estimated volumes. Which means we need to store it somewhere; we can’t put it straight into the ticket.
2019-02-14 23:57:08 +00:00
for table in TABLES:
op.add_column(table, sa.Column('consent_to_research', sa.Boolean(), nullable=False, server_default=sa.false()))
for channel in CHANNELS:
op.add_column(table, sa.Column(channel, sa.Integer(), nullable=True))
Add fields to record a service’s estimated volumes When a service go live we ask people for their estimated sending volumes. At the moment we only put this in the ticket, and store it in a spreadsheet. This means that a service can - say they want to go live - say they are sending 100,000 emails per year - not have created any email templates - still see ‘create templates’ as ‘completed’ in the go live checklist If we store this data against the service we can collect it earlier, and then use it to determine automatically what kind of templates the user needs to create before their go live checklist can be considered complete.
2019-02-13 14:00:52 +00:00
def downgrade():
Also store consent to research against a service It makes most sense to collect this at the same time as the estimated volumes. Which means we need to store it somewhere; we can’t put it straight into the ticket.
2019-02-14 23:57:08 +00:00
for table in TABLES:
op.drop_column(table, 'consent_to_research')
for channel in CHANNELS:
op.drop_column(table, channel)
Reference in New Issue Copy Permalink