SwissChecklist

Checklist: DotNetNuke Best Practices - Profile Definition

User profiles are very usefull, and like every data storage it's easier to set up right the first time, than to tweak over and over once a lot of data has accumulated. This checklist will help you define a good profile.

BTW: more such checklists here DotNetNuke Best Practices - Users and Roles(No Checklist found)
  • Get the specs right - not too much, not too little

    Show Details Show Substeps Show Substeps Show Substeps
  • Start with the goal

    Show Details Show Substeps Show Substeps Show Substeps
    Always start with the goal, because that will be your guidance in deciding what fields you need. Do this:
    • Write down why exactly you need the user data
    • Write down how you will use it later on (directory? mass mailing?)
  • Define the groups of information you need

    Show Details Show Substeps Show Substeps Show Substeps
    Typical groups are
    • Login information
    • Address/Postal information
    • Contact information (tel, mail, fax)
    • Business Profile
    • Experience customization (I like the red skin...)
    • Preferences for the module xxx (like search preferences)
    • Hidden stuff (like configuration that the user never sets himself, but that gets set by other software for him)
  • Define the fields

    Show Details Show Substeps Show Substeps Show Substeps
  • Create a full list of all the fields you want, with the data type

    Show Details Show Substeps Show Substeps Show Substeps
  • Review the list and try to remove as much as possible

    Show Details Show Substeps Show Substeps Show Substeps
    The more data you have, the more likely the user will never fill it in. Try to shorten the list as much as possible.
  • Determine what fields are really required - try to keep most optional

    Show Details Show Substeps Show Substeps Show Substeps
  • Define the naming schema

    Show Details Show Substeps Show Substeps Show Substeps
  • Decide an your preferred language

    Show Details Show Substeps Show Substeps Show Substeps
  • Decide on naming of multi-word fields, like FirstName

    Show Details Show Substeps Show Substeps Show Substeps
    Recommendation is Pascal Casing: FirstName

    Alternatives
    • Firstname
    • firstname
    • first name
    • FIRSTname
    • fname (bad!)
  • New Step

    Show Details Show Substeps Show Substeps Show Substeps
Use this Checklist

Preview/Print

Use

Change

Sort