Results for users should include link to People page for W3C staff

tagawa commented 9 years ago

E.g. the API result for Philipp Hoschka should ideally include a link to http://www.w3.org/People/#Hoschka

Note that the in-page anchors don't follow a set format such as the user's family name so there may need to be a re-naming of anchors (at the risk of breaking some existing links).

tripu commented 9 years ago

We also discussed returning all the links that are listed for that user under the “links” section in their https://www.w3.org/users/<ID> page.

WDYT?

vivienlacourba commented 9 years ago

@tripu I am reluctant to expose user profile links in their current implementation as today it is a simple list of unchecked links with labels, plus our privacy policy does not state that we will share publicly those user provided links. For me working on public profile comes first, as this is when we will have to answer those privacy question and have new profile edit pages that would explain clearly to the user which information are going to be shared publicly. Once that project is done then yes we can expose the data that users would have agreed to share publicly.

vivienlacourba commented 9 years ago

@tagawa I don't want to add links to People page in the API result of a user as those links are only relevant for current W3C Staff members. On the opposite you should be able to create such a link easily.

The issue today is that the anchors used on the People page are the usernames (an info we decided not to expose in the API). As you suggested I think we should change those anchors and use the user id (an info we are already exposing in the API), the issue is that it might break existing links. Note that exposing usernames on the People page is already a mistake we should fix.

I am adding @tguild to see what he thinks about this proposal to change the anchors.

FYI, based on yesterday's weblogs here are the w3.org pages that are linking to /People and that would need to be reviewed and fixed as needed:

tguild commented 9 years ago

I am also disinclined from exposing usernames as identifiers and support converting to numeric ids.

tagawa commented 9 years ago

Thanks for the reply @vivienlacourba and @tguild. The current anchors in the People don't seem to be consistent - many times they are not the username so it would not be easy to create links as it is.

I agree changing all of them (and their backlinks) to numeric IDs would be the best solution although it's a lot of work. The list of backlinks above doesn't include all pages - is it possible to generate a complete list of all pages linking to w3.org/People please?

vivienlacourba commented 9 years ago

The current anchors in the People don't seem to be consistent - many times they are not the username so it would not be easy to create links as it is.

@tagawa the /People page is always using the user login for the user entry anchor. Here is the related template code:

<div class="foaf-person vcard" id="{{ user.login }}">

As agreed with you and @tguild I'll change that to use the user id instead.

The list of backlinks above doesn't include all pages - is it possible to generate a complete list of all pages linking to w3.org/People please?

@tagawa regarding your above comment what did you meant?

The list of pages I gave in my previous comment on this issue lists all w3.org URIs pointing to the People page. It was built from the HTTP referer header in our weblogs, so if some pages are missing it means they did not receive any traffic in a full day (even from web crawlers) which indicate they are not that important. Note that this might be the case for some historic non-public pages that aren't viewed or linked from anywhere. Let me know if you have knowledge of other (public) pages not listed here.

tagawa commented 9 years ago

Thanks for the quick response @vivienlacourba.

Re. the user logins it must be my misunderstanding. I thought user logins were the same as the first part of a user's email address (***@w3.org) but it seems not — sorry.

For pages linking to w3.org/people, I looked at a few WG pages and several of them link to People, e.g. http://www.w3.org/2012/webcrypto/ , http://www.w3.org/2013/csvw/wiki/Main_Page , http://www.w3.org/auto/wg/ etc. so there are probably more. If it's possible to programmatically get all pages that link to People that would be great.

vivienlacourba commented 9 years ago

@tagawa you are right, looking at logs for a single day was clearly not enough.

I made an updated list based on the last 3 months of logs that I uploaded on jay. It has 216 entries I believe several don't need to be fixed as they will only have a link to /People without using any anchor of that page.

Also note that http://www.w3.org/2013/csvw/wiki/Main_Page does not contain any link to a People page anchor http://www.w3.org/People/# but rather it has a link to Ivan's People page which is at: http://www.w3.org/People/Ivan

tripu commented 9 years ago

“As you suggested I think we should change those anchors and use the user id (an info we are already exposing in the API), the issue is that it might break existing links.”

FWIW, here goes an idea I shared with @tagawa days ago to avoid breaking links (if we were to keep old IDs on that page): we can't give more than one ID to the same element, but we can either assign it a new name or assign the new ID to an element that is almost that one.

Example of the first option:

<div class="foaf-person vcard" id="shadi" name="28937286802">
  <div class="person-info">
    <img src="/2006/05/u/2bc50aca8577-sm.jpg" alt="Photo of Shadi Abou-Zahra" class="photo foaf-depiction" width="90" height="120">
    <!-- … -->
  </div>
</div>

Second one:

<div class="foaf-person vcard" id="shadi">
  <div class="person-info" id="28937286802">
    <img src="/2006/05/u/2bc50aca8577-sm.jpg" alt="Photo of Shadi Abou-Zahra" class="photo foaf-depiction" width="90" height="120">
    <!-- … -->
  </div>
</div>

That would give us new fragment IDs without breaking the old ones.

tagawa commented 9 years ago

+1 I'd go for the second option to avoid id/name confusion.

w3c / w3c-api

Results for users should include link to People page for W3C staff #13