Debut candidate feature which provides a Personnel content type & view. Useful if you need a page listing of your staff, board, team, etc.
Sandbox link: http://drupal.org/sandbox/lefnire/1473350

Comments

nedjo’s picture

Thanks for posting this.

Questions and comments:

  • An alternate approach to meeting this need could be to use the debut_section feature to produce nested pages. E.g. a "staff" page with a child page for each staff member. It wouldn't have the specific fields (contact info, position), but would be flexible in terms of multiple types of personnel. Would this meet the need?
  • 'Personnel' seems a fairly technical name to appear e.g. as a primary links menu item--"Staff" or "Members" might be more common.
  • How does a personnel record here relate to a user account on the site, if one exists? We have a profile2 profile type in debut_bio. Is this relevant here?
  • The contact info field is free text rather than being structured. Should it use an address or similar field type? Are we getting into contact management territory here? Is something like http://drupal.org/project/party relevant?
  • Should personnel be categorized, e.g., "Board", "Staff", etc.? If so, should they appear on separate pages, or at least in view with a term argument (contextual filter)?
lefnire’s picture

Also, note to self, the new debut_member & how it compares

ljn’s picture

Good points all around. Here are my thoughts, in order:

  • I tested debut_section and it doesn't seem to really fit the need the common application of a staff page how we see it.
  • I think "staff" might be the better term. "Members" sound more like a community tool, but that may be just me.
  • A personnel record doesn't related to a user account at all. Often it's the case that one or two users manage the CMS, but need to create staff pages for each person at the organization. It'd be much easier to keep this separate from user accounts.
  • For the same reasons of keeping it simple, we'd like to keep it away form CRM territory.
  • I think you're right about the term and separate views. Board, staff, advisors - these frequently get separate pages.

Thoughts?

nedjo’s picture

Sounds good, I'd say go ahead.

I'm working on a RedHen-based debut CRM feature, but I agree, it serves a different purpose and doesn't overlay with what you're doing.