I agree with Mary. To me it is clogging the database with having the spouse as a separate consituent just because they are (say) an alum. Nor do we have the staff resources to manage it. We are a small office and don't the luxury of having a dedicated staff person do nothing but manage RE.
Often I need to query spouses who are alums.
When a couple give, they are giving together, not separately.
Not going to happen in my opinion. Constituent codes are for constituents. You have other options - such as attributes - to create and manage codes for non-constituents. The developers will (hopefully) not dedicate resources to this when there are hundreds of issues in here for which there are no alternative options.
Records are not just about giving - they are about people. There are dozens of reasons a spouse in his/her own right has enough data about them that you need to store which will necessitate them being a full constituent. To avoid this only ties your own hands for no reason.
I know this is not fun to hear but not having the resources to manage the database is not a valid reason to manage it poorly. If RE is too big for your organization you have other alternatives. If you have spent the hefty price to get RE you should, in my opinion, dedicate the proper resources to manage it.
Guest
Spouses can have constituent codes - if they are constituents. Non-constituents can't and shouldn't have constituency codes.
We are small enough that it would be messier to have them as their own (linked) constituent, but would be helpful to give them their own code.
I agree with Mary. To me it is clogging the database with having the spouse as a separate consituent just because they are (say) an alum. Nor do we have the staff resources to manage it. We are a small office and don't the luxury of having a dedicated staff person do nothing but manage RE.
Often I need to query spouses who are alums.
When a couple give, they are giving together, not separately.
Not going to happen in my opinion. Constituent codes are for constituents. You have other options - such as attributes - to create and manage codes for non-constituents. The developers will (hopefully) not dedicate resources to this when there are hundreds of issues in here for which there are no alternative options.
Records are not just about giving - they are about people. There are dozens of reasons a spouse in his/her own right has enough data about them that you need to store which will necessitate them being a full constituent. To avoid this only ties your own hands for no reason.
I know this is not fun to hear but not having the resources to manage the database is not a valid reason to manage it poorly. If RE is too big for your organization you have other alternatives. If you have spent the hefty price to get RE you should, in my opinion, dedicate the proper resources to manage it.