National data uploader

This is all design and workshop material around the uploader: MVP, Post MVP, and Process

Workshop: MVP, Post MVP, and Process

	MVP	How do we meet this need/considerations	Post MVP
FE (Front End)	Secure log in	User Interface Key cloak/Azure (Authentification)	Blank sheet – Validation occurs once uploaded
	View of data sets due + time frames	User Interface - User interaction/table	Pre-formatted sheet – Validation occurs on an excel sheet
	Ability to upload CSV or XLSX files during submission	User Interface Validation	Online form
	Only upload current data	User Interface Validation
	Agreement with data sharing and use (IG)	User Interface Policies and Cookies acceptance prompt
	Interaction only for a user with data from their associated HEI	User Interface User permissions/roles
	Report on passed/failed validation	User Interface for initial user feedback Final validation for data sets possibly required We may also wish to set up an alert that lets HEE Admins know something has happened on a submission?
	Upload area – Status of data submitted, a report from the last upload, download template/guidance	User Interface
FE Validation	Confirm whole numbers	This needs to be clear for the devs to implement
	Starters must be more than 0	This needs to be clear for the devs to implement
	Makes logical “mathematical” sense (E.g. total number of starting students add up when factoring completions and leavers)	This needs to be clear for the devs to implement
	Values in fields agreed from a list of values, data types	This needs to be clear for the devs to implement
	Check current submissions against previous and flag any change to allow HEI to validate	Needs investigating
	Warn if a number of starters are higher than plan	Needs investigating
BE (Back End)	Uploaded data “passed” stage 1 validation lands in the staging area (How long+ how/when)	This needs to be worked out with the BE and NDW team/specialists	Design reports submissions like HEE admin but for local office only
	Placement activity in weeks (+0.5 partial)
	HEE teams have agreed on access to data sets for 2^nd validation
	Dev access to data in the staging area after initial validation
	Reference data is maintained/available for comparison
	Data to be amendable and adjustable
	Access to the latest data at any time across functions
Process/Parking	Link to previous submissions at uploader stage
	Dropdown list for placement providers
	Course length in months
	Consistent definitions
	Agreement from end-users on data types, fields and values
	Known email address for each contact
	Placement tariff
	Testing in Jan with go live in March
	Automated reminders for outstanding data
	Testing with education providers
	Ability to liaise with ETL dev for on onboarding
	Verified emails and passwords
	Assurance that the tool is secure
	Information schedule dictates what information is required for
	Caveats to data visible to those users responsible for reporting
	Users notified when new data is available
	Timely access to agreed info reports
	Decisions on what is reported (Finance, quality, RTT)
	Dropdown list for qualification, the course title, pathway and mode	Can you copy and paste if the value is in the drop-down?

Workshop: MVP, Post MVP, and Process

Requirements Master Document with Acceptance Criteria

Wireframes: https://projects.invisionapp.com/freehand/document/vwzjW1cVy

Prototype: https://invis.io/5FRAS8JRM9K#/379486209_IG_-_Data_Acceptance