In order to source data about team members scalably, it seems that every so often when a team member accesses team.artsy.net, the site could prompt them to provide info into the various fields we want.
This could just be a pop-up that asks "What languages do you speak?" or "Choose your favorite artwork on Artsy" and then populates their entry in the Navigator with that info.
Not sure how difficult this is technically, but otherwise our database relies on surveying the team, which is inefficient and ends up with inconsistent data.
In order to source data about team members scalably, it seems that every so often when a team member accesses team.artsy.net, the site could prompt them to provide info into the various fields we want.
This could just be a pop-up that asks "What languages do you speak?" or "Choose your favorite artwork on Artsy" and then populates their entry in the Navigator with that info.
Not sure how difficult this is technically, but otherwise our database relies on surveying the team, which is inefficient and ends up with inconsistent data.