Entz commited on
Commit
ae4db06
·
verified ·
1 Parent(s): 342d4c0

Upload 3 files

Browse files
Files changed (2) hide show
  1. tab1.txt +6 -6
  2. tab2.txt +0 -15
tab1.txt CHANGED
@@ -1,21 +1,21 @@
1
- * If "403 Client Error: Forbidden for url" error arises, it is because the backend server is being spinned up. Please stay patient and try refresh the page every 1 minute. It takes 1-3mins to spin up usually. 5mins is a outliner but it happens sometimes.
2
-
3
  Data quality issues have long plagued council databases, burdening W2 workflow teams (e.g. the Assisted Travel Team's dashboard I am working on), data analysts, and engineers with manual cleaning and validation. This pilot explores how AI-driven workflows can address these pain points by streamlining user registration, ensuring accurate data collection, and reducing validation overhead.
4
 
5
- ## What is this Registration System?
 
 
6
  This application leverages **FastAPI**, **LangGraph**, and **AI validation** (**ChatGPT** with **Guardrails AI** and **dspy**) to collect user information (email, name, address, phone, username, password (included only a few for demo purpose)) with optional fields and real-time validation. It uses real-time validation to enforce formats (e.g., addresses, phone numbers), minimizing errors and enhancing data integrity stored in a PostgreSQL database.
7
 
8
- ## How Does It Work?
9
  - **Register**: In the "Registration" tab, users answer a series of questions, with optional fields (address, phone) skippable.
10
  - **Validation**: AI validates inputs (e.g., e.g. address formats, phone numbers, will ask for clarification if ambiguous).
11
  - **Data Storage**: Responses are saved securely in a database for review and editing (currently in a PostgreSQL db in another server.).
12
 
13
- ## Objectives
14
  - Address **data quality** issues by automating validation and reducing errors.
15
  - Enhance **efficiency** in user onboarding processes.
16
  - Explore **scalable**, secure registration systems for public sector applications. The Same logic could apply to Copilot's Agent, and Power Apps.
17
 
18
- ## Prototype
19
  We encourage you to test the system with varied inputs to evaluate its robustness. You will see the input summary in the end of registration. You will be amazed how the system would prompt you for the better answer if too ambiguous, and how capable it is in standardising and cleaning up the data.
20
 
21
  **Last Update**: 30th June 2025
 
 
 
1
  Data quality issues have long plagued council databases, burdening W2 workflow teams (e.g. the Assisted Travel Team's dashboard I am working on), data analysts, and engineers with manual cleaning and validation. This pilot explores how AI-driven workflows can address these pain points by streamlining user registration, ensuring accurate data collection, and reducing validation overhead.
2
 
3
+ * If "403 Client Error: Forbidden for url" error arises, it is because the backend server is being spinned up. Please stay patient and try refresh the page every 1 minute. It takes 1-3mins to spin up usually. 5mins is a outliner but it happens sometimes.
4
+
5
+ ### What is this Registration System?
6
  This application leverages **FastAPI**, **LangGraph**, and **AI validation** (**ChatGPT** with **Guardrails AI** and **dspy**) to collect user information (email, name, address, phone, username, password (included only a few for demo purpose)) with optional fields and real-time validation. It uses real-time validation to enforce formats (e.g., addresses, phone numbers), minimizing errors and enhancing data integrity stored in a PostgreSQL database.
7
 
8
+ ### How Does It Work?
9
  - **Register**: In the "Registration" tab, users answer a series of questions, with optional fields (address, phone) skippable.
10
  - **Validation**: AI validates inputs (e.g., e.g. address formats, phone numbers, will ask for clarification if ambiguous).
11
  - **Data Storage**: Responses are saved securely in a database for review and editing (currently in a PostgreSQL db in another server.).
12
 
13
+ ### Objectives
14
  - Address **data quality** issues by automating validation and reducing errors.
15
  - Enhance **efficiency** in user onboarding processes.
16
  - Explore **scalable**, secure registration systems for public sector applications. The Same logic could apply to Copilot's Agent, and Power Apps.
17
 
18
+ ### Prototype
19
  We encourage you to test the system with varied inputs to evaluate its robustness. You will see the input summary in the end of registration. You will be amazed how the system would prompt you for the better answer if too ambiguous, and how capable it is in standardising and cleaning up the data.
20
 
21
  **Last Update**: 30th June 2025
tab2.txt CHANGED
@@ -1,15 +0,0 @@
1
2
3
- The email address appears to have a typo in the domain extension:
4
- 'yahoo.come.uk' is not a valid domain. Please check and provide a correct email address.
5
-
6
- michael jordan (double spaces)
7
- Name formatted correctly with capitalization.
8
-
9
- r2 123 High Street, London, SW1A 1AA.
10
- The address includes a room identifier, house number, street name, city, and postcode, meeting the required format.
11
- Room 2, 123 High Street, London, SW1A 1AA
12
-
13
- +4407442757070
14
- The phone number is a valid UK mobile number in international format and has been correctly converted to national format.
15
- 07442 757 070