Similar to #2 there is an airtable that was set up as an earlier version of the CAT directory containing tags, profile information and so on.
In most cases we have an email address to key the information on, so we'd be able to fetch the corresponding row from airtable, and either:
a) update an existing user if there is an existing user with a matching email address
b) create a user and populate it with information if the user doesn't exist
At present, users can't change their email address, so users changing their address to someone else's one to fetch someone's profile info is less of a worry right now. We'd need to only support this import when an email address haas been confirmed.
Ideally this would be something a user can trigger on their own profile, so allow them to support a one way 'sync' of information.
Similar to #2 there is an airtable that was set up as an earlier version of the CAT directory containing tags, profile information and so on.
In most cases we have an email address to key the information on, so we'd be able to fetch the corresponding row from airtable, and either:
a) update an existing user if there is an existing user with a matching email address
b) create a user and populate it with information if the user doesn't exist
At present, users can't change their email address, so users changing their address to someone else's one to fetch someone's profile info is less of a worry right now. We'd need to only support this import when an email address haas been confirmed.
Ideally this would be something a user can trigger on their own profile, so allow them to support a one way 'sync' of information.