It would be really effective if existing fields could be selected for inclusion in Student Registers when creating custom registers, and fields created in Student Registers could be available to complete in other areas of the system eg the Admissions portal forms.
This would limit duplication of fields/data and reduce manual updates to a range of areas throughout the system.
For example, when setting up a custom Student Register to track pupil immigration status, fields already exist for nationality, birth country in Student Manager, but it isn't currently possible to include these existing fields into the register, so that the data is only updated within the one field, within one location, for teams that only require access to that particular register and may not need full access to a student record.t
It would also be great if fields from Student Registers could be included in other areas of the system, such as when creating an application /enquiry form for the Admissions portal. At the moment, to custom fields have to be set up within Admissions/Student Manager in order to be included and completed via the Admissions forms on the website.
This would also be very helpful for us. We are also setting up an EAL Register and are coming across the same issues. We are able to provide the information to users in the form of a report, but what users would really like to see is the information in the Register. Re-keying data seems counter-productive and likely to create a variance in information.
If fields that are elsewhere could be shown as a read-only in a Register that would be super helpful. This would also extend to custom fields.
See also https://ideas.isams.com/ideas/MIS-I-1739
This is really very important.
I've just started with Registers and the first thing I looked at was our EAL provision. The key things we need to know are: Enrollment Date, Nationality, SEN flag. All of this is already held elsewhere and I don't want to have duplicate fields. I know that they can be exported from various places, but I wanted to have an EAL Card visible in Student/Pupil Profiles, and this data needs to be there as part of that.
We also want to create workflows in Registers to complement our Admissions process that will replace some of the many Custom Fields we have created in Student/Pupil Manager and, again, it would be useful to view the relevant Pupil/Student fields there too.