WebNewRoles

From NMC Wiki

Jump to: navigation, search

return to nmc 2.0

[edit] Process

Guests can see all content beyond member restricted tools/resources and project restricted forums.

Any site visitor can create their own account; select their organization from a drop down list of member organizations, or enter it in form field if not there. Their member status would need to be approved either by NMC staff admin or (?? possible) by the local NMC Director (the rep for that organization).

[edit] Roles (draft)

  • guest (not logged in)
    • browse,search public content
    • post comments
  • authenticated user (logged in)
    • tag/rate content
    • register for NMC events
  • Specific project members:
    • Marcus Project
      • participate in private project forum discussions
      • contribute examples to gallery
    • Horizon Project
      • participate in private project forum discussions
      • possible associate log in with log in to edit project wiki?
  • NMC Members (authenticated and associated with active member)
    • participate in members only discussions
    • add RSS feeds to center RSS aggregator, podcast aggregator
    • add spotlight featured for gallery
    • create other content published on NMC site (see WebMembers)
  • NMC Directors (one person as rep from a member institution)
    • update database info for their org (edit address, phone, url, etc)
    • enter/edit data to locate center on Google map for member orgs
    • possibly?? approve individuals from their institution as NMC member status??
  • NMC Corporate Members (authenticated and associated with active member)
    • create blog/story info related to new products, etc
    •  ??? needs work here
  • NMC Content admin (ability to do everything in terms of creating, approving content)
  • Drupal Admin (manage modules, configuration, approve/create/edit accounts)

[edit] Roles (updated)

These are roles that existing in the alpha version of NMC web 2.0. A number of them were added from listings in the old NMC database. The roles in Drupal need only be if they require some special sort of permission or task they need to do on the site, not necessarily for conference registration purposes. Roles are only in regard to activities on NMC web 2.0

roles in bold are ones added for drupal purposes

  • academic champion
  • blog writer for those that will be posting news on specific NMC project
  • board emeritus
  • board member
  • corporate champion
  • faculty
  • former nmc director
  • mailing list
  • new media center director (these are director contacts, yes?)
  • nmc content admin for people who will be editing, adding new content to the main sites
  • nmc corporate member
  • nmc drupal admin people who need full admin to the web server system
  • nmc member all NMC members who have access to "members only content"
  • nmc staff admin for NMC staff to edit page content, events, user, and organizational profiles
  • nmc superuser NMC staff with access to all drupla features (Adam, Alan)
  • ordering/sales contact
  • primary corporate contact
  • program assistant
  • purchasing contact - new media c
  • purchasing contact - university
  • second corporate contact
  • second key contact
  • staff
  • student assistant
  • technical support contact
  • technology contact

Need to add:

  • marcus project member will enable acces to specific resources, discussion forums, etc. Previusly this was a database field, needs to be moved to a role
Personal tools