For Schools
Q1: Are teachers required to handle the data access request via EdData on their own?
A1: No. The request(s) can be handled by the school administrator who manages EdCity accounts.
Q2: Can teachers and students use their Google account to log in to the eResource platforms if the school is using Google Classroom?
A2: Yes. Simply log in to the platform and follow the steps to enable ‘log in with third party account’ under ‘Setting’. If school intends to connect third party accounts by batch, please contact EdCity for assistance.
Q3: Can teachers and students log in to the eResource platform by using the email account provided by school?
A3: Yes. Teachers and students can use the email account provided by school to log in if the school administrator has filled out such information in the ‘School Email’ column.
Q4: How do schools notify the providers if there are changes made on student data, e.g. adding or removing student account?
A4: School administrator can update student data on ‘School Accounts Administration System’, providers will then receive an email notification and the update(s) can also be viewed on provider’s admin page of the EdData portal.
Q5: How can school know if a provider has requested for data access?
A5: School administrator will receive an email notification and the request(s) can also be viewed on administrator’s admin page of the EdData portal.
Q6: Can school decide whether to authorise or edit providers’ data access request?
A6: Except the mandatory data, school can edit or decline providers’ request for accessing the optional data. The system will base on schools’ respond, and notify the provider by email, as well as message on provider’s admin page accordingly.
Q7: Can school edit the data which provider has been authorised to download?
A7: Yes. School can edit the data through the EdData portal. The system will notify the provider for such changes. Provider simply downloads then uploads data to the eLearning platform again for the updates.
For Partners
Q8: Can providers use EdData only, but not EdConnect?
A8: No. The prerequisite for providers to access data via EdData is to use the ‘EdConnect Single Sign-on Directory Service’. If providers are looking for a single sign-on solution, and not required to access school data, they may just apply for the ‘EdConnect Single Sign-on Directory Service’.
Q9: By using EdData, are providers required to collect data file from schools?
A9: No. Provider can make request(s) and access data with schools’ authorisation on the EdData portal, provided that the school administrator has updated account information on ‘School Accounts Administration System’.
Q10: How do providers know if school has responded to the request(s)?
A10: Provider will be notified by email with schools’ responses, including the authorisation, changes request and declination. The information can also be viewed on provider’s admin page of the EdData portal.
Q11: How do providers know if school has made changes on student account?
A11: Provider will be notified by email if school administrator has updated student account on ‘School Accounts Administration System’. The information can also be viewed on provider’s admin page of the EdData portal.
Q12: How do providers access data?
A12: Providers can access data by the following ways:
- Access student data by using the EdData API on the backend
- Log in to the EdData Portal, and download the encrypted CSV or JSON files
Q13: What student data will be shared with partners?
A13: EdCity invited industry partners to share their views on ‘Student Data Standard’, and the 14 data fields include:
Mandatory Data (2 fields)
- DISPLAY_NAME (Display Name)
- PROFILE_ID (Profile ID)
Optional Data (12 fields)
- HKEDCITY_ID (EdCity Login Name)
- SCHOOL_CODE (School Reg Number)
- STUDENT_ENNAME (Student English Name)
- STUDENT_CHNAME (Student Chinese Name)
- REG_NO (Student Reg No.)
- SCH_YEAR (School Year)
- CLASS_LVL (Class Level)
- CLASS_NAME (Class Name)
- CLASS_NUMBER (Class No.)
- * GENDER (Sex)
- * MOBILE_NO (Mobile Phone No.)
- * EMAIL (School Email)
* Service provider MUST give a reason for accessing such sensitive data