cds-snc / cds-snc/platform-forms-client

Explore retaining high-volume responses within GC Forms

Open
#7,798 0 comments 0 reactions 0 assignees View on GitHub
needs discussion responses
Dominant language
TypeScript
Stars
46
Forks
16
Avg merge
1d 8h
Merged PRs (30d)
85

Description

### Description:

As part of the high-volume response pilot, explore whether we could support higher-volume use cases by retaining responses within GC Forms, rather than building a mechanism to move or remove high-volume response data from GC Forms.

This could also consider how this approach might connect with the CRM CDS is building and whether it could help us manage or track work related to these clients.

#### Need to explore policy implications:
- [ ] Security/privacy risks of retaining responses longer-term
- [ ] CDS’s overall comfort with holding this data long-term
- [ ] Any retention, storage, or policy constraints we would need to account for

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by mapping how GC Forms currently handles high-volume responses, then investigate long-term retention, storage, security/privacy, policy constraints, and how the approach could connect with CDS’s CRM. Done means a documented feasibility assessment and a clear decision or recommendation.

Written by the indexing model from the issue text.

Assessment

Domain
databases, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.