[PamelaBryman]

I'm working in a merged database (1 RE and 2 Results Plus). Staff have coded board members in differing manners over the years & I'm standardizing it.

How do ya'all code your board members? I am coding current board members as:

Constituent Code: Board Member
Attribute: Current Board Member

Former board members get an attribute coding only (Former Board Member).

Does that make sense or is there a better way?

Thanks!
Pam

[JBeckland]

I would recommend only using the Constituent Code for your current Board members. There is no reason to create duplicate codes in both CCs and Attributes. And, it can cause confusion in individual records and in queries.

Other than that, I think your coding system is good. You might want to also consider tracking the committees they serve on with a table-based "Board Committee" Attribute.

[PamelaBryman]

Thanks J! That is what I am doing (coding only current board members using Constituent Code).

[andrea.bbbs]

We have 8 boards - with about 80 board members at any given time. I have a separate Cons Code for each board, plus one for Former Board. All current board members have a From date with the To date blank. When a member leaves, I add an end date and add a Cons Code of Former Board. Writing this makes it look pretty redundant - now I am thinking I should revisit that....

Anyway, to find current members I can just query on To date is blank.

[Peter Gulka]

There's also a school of thought that says you create an org record for
your board and add those folks as relationships to that org.

[Matthew]

I like creating an org record for your organization and linking the board members through relationships with the appropriate relationship codes (for the boards they sit on and/or the committees they sit on). This way you can also use the position field in the relationship for things like Board Chairperson, etc.