Skip to content
This repository has been archived by the owner on Jan 9, 2019. It is now read-only.

Include affiliation in participants list #75

Open
wseltzer opened this issue Mar 22, 2017 · 2 comments
Open

Include affiliation in participants list #75

wseltzer opened this issue Mar 22, 2017 · 2 comments

Comments

@wseltzer
Copy link
Member

e.g. Wendy Seltzer (W3C) rather than Wendy Seltzer, Strategy Lead.

Most people haven't given a "title", and I bet those that have didn't give much thought to it or keep it updated. Organizational affiliation / IE status is more relevant.

@tripu
Copy link
Member

tripu commented Mar 22, 2017

I too have noticed that “work titles” are often missing or inaccurate. And I agree that affiliation would be more relevant in most contexts.

The problem is that a page like labs.w3.org/unitas/?g=42434 already involves 8 API requests (group, chairs, services, specs, team contacts, participants, charters, members). The API query for team contacts, for example (api.w3.org/groups/42434/teamcontacts; append a valid API key) does not include the affiliations of those people (only a reference to the corresponding API endpoint). It does include their work title and a few other scalar fields (that's why Unitas is displaying it). So to retrieve the affiliation we'd have to query the API once for each team contact or participant in the group… Lots of HTTP requests; not practical.

There's an open issue on the API related to this: w3c/w3c-api#64. If it's tackled, we may get that information with a decent number of queries, and we could display affiliations instead. Otherwise, I don't see how to do it.

@tripu
Copy link
Member

tripu commented Mar 22, 2017

What we can do, for the time being, is simply not show those work titles on lists of participants, team contacts, chairs, etc — if we think they're not useful.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants