Using actions to record museum visits.

Lance Dudek

At our museum, we have been tracking attendance using a constituent attribute, and a second attribute to track attendance to the museum's theatre. For each visit we have an attribute, and include the date attended. The attribute tab therefore becomes cluttered for individuals who attend often. We are planning to begin recording this information as actions. Does anyone who currently records casual attendance/visits in RE have advice on the benefits, pitfalls or clutter control and how they code and make use of attendance data?

Joshua Bekerman bCLO bCRE

Lance Dudek:
At our museum, we have been tracking attendance using a constituent attribute, and a second attribute to track attendance to the museum's theatre. For each visit we have an attribute, and include the date attended. The attribute tab therefore becomes cluttered for individuals who attend often. We are planning to begin recording this information as actions. Does anyone who currently records casual attendance/visits in RE have advice on the benefits, pitfalls or clutter control and how they code and make use of attendance data?

Do you have the membership module?  If so, then use actions which is already integrated into the Membership Scanning that will add an action when a membership card is scanned.

Otherwise, the Appeal tab might be a better choice when it comes to clutter control.  For us, the Appeal tab isn't viewed that often so clutter shouldn't be much of an issue (as opposed to Attributes), and you would still be able to pull data from it (last visit, number of visits, etc.).  I think Actions might be overkill if all you need to track is that they visited and the date of visit... unless you have the membership module, then Actions all the way.

 

 

Lance Dudek

Josh Bekerman:

Do you have the membership module?  If so, then use actions which is already integrated into the Membership Scanning that will add an action when a membership card is scanned.

Otherwise, the Appeal tab might be a better choice when it comes to clutter control.  For us, the Appeal tab isn't viewed that often so clutter shouldn't be much of an issue (as opposed to Attributes), and you would still be able to pull data from it (last visit, number of visits, etc.).  I think Actions might be overkill if all you need to track is that they visited and the date of visit... unless you have the membership module, then Actions all the way.

 

 

Thanks Josh, We still do not have RE at our admissions, but are using a separate ticketing system. We have only been capturing bar codes with a scanner but we do have the membership module. For us, using the Appeal tab won't work since we're trying to use that tab only for when we are making an ask for support. Looks like Actions is the choice. Thanks.