Ticket #142 (new defect) — at Version 4

Opened 5 years ago

Last modified 3 years ago

Update User object with additional fields such as 'nickname'

Reported by: dread Owned by: pudo
Priority: major Milestone:
Component: ckan Keywords:
Cc: Repository:
Theme:

Description (last modified by rgrp) (diff)

Suggested fields:

  • id, name (username/profile name), openid, email, password, extras (JsonType?)
    • + current items: apikey, about, created)
    • current contents of name is usually openid and should migrate to openid field (could match based on starting with http://)
  • May also want a fullname field (or perhaps that can

just go in extras - may be better to have its own field as useful to search on this )

Related changes (probably separate tickets):

  • Improve user home page to include this additional information (and have it be editable)
  • Use user 'name' (username) for home page links (rather than current user/<id>)
  • Where we show lists of revisions, each revision author is now a link to the author's user page.

Related to ticket:136 and ticket:138.

Change History

comment:1 Changed 5 years ago by rgrp

Might be interested here in auto-extracting a nickname from openid (or getting service to give it to us). This question is of relevance on this point: http://stackoverflow.com/questions/572939/extracting-a-username-from-an-openid-identity (though basic answer is "you can't").

comment:2 Changed 4 years ago by paperless@…

See also: http://stackoverflow.com/questions/1355292/friendly-name-from-google-using-openid

Looks like Google has made this difficult intentionally.

comment:3 Changed 4 years ago by rgrp

  • Owner changed from rgrp to pudo

comment:4 Changed 4 years ago by rgrp

  • Type changed from enhancement to defect
  • Description modified (diff)
  • Summary changed from User has nickname to Update User object with additional fields such as 'nickname'
Note: See TracTickets for help on using tickets.