The Database Manager enables administrators to perform the following:
Create New Departments
Create up to 100 subjects for academic or non-academic use.
Edit Shared Fields
Shared fields on Pupil Tracking are managed centrally. Administrators wishing to standardise data entry across all subjects can do so by adding new shared fields.
Edit General Fields
Fields for data specific to the pupil e.g. Gender, CAT scores, SNSA and SMID data can be added as general fields. General fields can be viewed by all subjects at all times. The write access to general fields differs according to establishment type. For secondary schools general fields are writable at administration level only. For primary and nursery schools write access can be given at the subject level.
Edit Subject Specific Fields
In addition to the shared and general fields, subject specific fields may be created to store subject specific data.
Create Select Boxes for Data Entry
By default Pupil Tracking provides text boxes for subject users to manually type the data they wish to enter. However, by adding select boxes for data entry administrators can provide a drop down list of options for users to choose from. This also forces users to enter the appropriate data.
Administrators can make fields read only or read write. The fields available for this option will differ depending on the establishment type. Primary and nursery schools can make both shared and general fields read only or read write. Secondary schools may only control the write of shared fields. Making fields read only is useful if you want staff to view fields but not edit them.
Hide Fields From the User Interface
Administrators can show or hide shared and general fields from the subject user interface. Note that you will need to be logged in as a subject user or teacher to see the effect of these changes. Administrators using Login Directly As... will always see all fields.
Show/Hide Shared Fields En Masse
Every subject on Pupil Tracking must have the shared fields included in their field list. However, shared fields can be hidden from subjects who do not wish to see them. For example, the subject DofE might be created to allow Duke of Edinburgh award data to be stored. As DofE is not an academic subject it does not need to see or use shared fields.