Forum topic

Ideally the update form would show the following details:

Fields available for confirmation to be automatically updated:

Given Name
Middle Name
Family Name
Date of Birth
Gender
Nationality
Ethnicity (picklist into Student>HESA>Student Values>Ethnicity)
Disability (picklist into Student>HESA>Student Values>Disability)
Religion or Belief (picklist into Student>HESA>Student Values>Religion)
Denomination (picklist into Student>Personal Info> Profile>Person Denomination)
Student Finance Support Number (picklist into Student>HESA>Student IDs>SSN)
Primary Email Address
"Primary"-type Address field.
Home Telephone Number
Mobile Telephone Number
--
Emergency Contact Information (to be inputted into Student>Personal Info>Emergency Info:

Contact Name
Relationship to You
Home Phone
Mobile Phone
Address

Tickbox: I consent to authorised staff of Cliff College storing my emergency information, for use in an emergency, to be shared only with relevant authorised individuals, including members of the emergency services.
--
Fields to display from the record with a tickbox for 'details incorrect' to flag:

Major Degree Track (for non-completed degree tracks)
Major Degree Track Start Date
Classification
Email Address
Student>HESA>Student Engagements>Highest Qualification on Entry of highest number Engagement Entity

--

Tickbox with the tag: "I understand and agree that the information included on this form, with the exception of my email address, will be shared with the University of Manchester as the Awarding Body, and by submitting this form attach my electronic signature." 

------

The ideal would be that this form is accessible once per Year (e.g. 2020-2021) for students, and once it is submitted it would close again until the next year. However, if that's too difficult, it could be permanently open.

I'll send to gnecsishelp by email a doc copy of Cliff's annual student registration form, so you can see what we're aiming to replace.

Thanks!
 

This is excellent, thank-you!

I think how we envision this being most useful is to replace yearly registration forms - that is, there are certain demographic details we need to give students the opportunity to update each year, and at the moment the way we do that is having them fill out a form, and then manually updating that data in GNECsis. If students were able to use the Request Change function to edit/confirm these details directly in the system each year, all that manual entry would become as simple as scanning down a list of proposed changes and accepting them.

I think the system could work pretty much as currently implemented, with a couple of possible additions:

1. It might be useful to have most of these new fields (mostly the demographic ones) locked in a 'once-a-year' subsection - that is, once they update them for an academic year, they don't appear again until the next academic year. That's not a deal-breaker, it might just be helpful. Alternatively, just in a subsection of their own on the Request Changes form marked 'Registration Data' or something similar, so people generally know to leave them alone except at Registration.

2. A way to check who has and has not completed a Request Changes for that academic year, against those enrolled for the year.

3. A way to limit entries: at least until we can Inactivate/Historical items from PickLists, the PickLists for these fields will contain legacy items we don't want in the system; it works fine for Admin staff to have "(INACTIVE - DO NOT USE)" tags on these items, but you know for certain students will still use them if they're there.

Thanks! I realise these may be a while off, but it's great to see the in-system Profile Update in action, it's a great improvement.

R