CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Discussion »
  • Extensions (Moderators: mathieu, totten, kasiawaka) »
  • Move engagement_level from core Activity to an extension?
Pages: [1]

Author Topic: Move engagement_level from core Activity to an extension?  (Read 582 times)

JoeMurray

  • Administrator
  • Ask me questions
  • *****
  • Posts: 578
  • Karma: 24
    • JMA Consulting
  • CiviCRM version: 4.4 and 4.5 (as of Nov 2014)
  • CMS version: Drupal, WordPress, Joomla
  • MySQL version: MySQL 5.5, 5.6, MariaDB 10.0 (as of Nov 2014)
Move engagement_level from core Activity to an extension?
October 05, 2013, 11:56:10 am
Many activities have nothing to do with engagement level. The current implementation of engagement_level field on _ALL_ activities of all type is inappropriate. Many organizations do not use engagement levels, though certain models of community organizing do. For those that implement engagement levels, many of them place it as a calculated value on the contact to assist in segmenting the contact. I don't think this field should be in core product by default. I think it would be fine to add it as a field in a CiviEngage extension.

Comments? Feedback?
Co-author of Using CiviCRM https://www.packtpub.com/using-civicrm/book

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: Move engagement_level from core Activity to an extension?
October 05, 2013, 01:00:37 pm
My guess is that if CiviEngage were written today and not x number of years ago, they would have made this a custom field.
Try asking your question on the new CiviCRM help site.

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: Move engagement_level from core Activity to an extension?
October 05, 2013, 04:17:06 pm
Hi Joe,

Good point, in general, we should (and do) move more to a "lighter" core and more extensions.

IMO if it makes the interface more complex and is not needed by "a majority" (highly subjective, I'd argue that the majority of civi users should be concerned about engagements ;) it should be part of an extension, unless technical (and or marketing/political) reasons.

I'd argue as well that civiaccount would make sense as an extension too as (the majority?) of users don't need "accountant correct" export and would prefer not to loose he performance due to the more complex financial structure it introduces ;)

As for the engagement, I think it's a good example. In the core it's "simply" a new column in the activity table and some UI and reporting.

If it were an extension, it'd need a separate table or a custom field, both more expensive (ie extra join, more records) and probably loosing some functionalities (eg in export/api/report/search) were the extra field is "trivial" to add but the extra field in a joined table might imply way more wrestling with the framework.

And I don't think anyone has the resources to "redo as extension" what is already in the core, especially if whomever added that in the core thought (often for good reasons) that this need was a common one shared by the majority so I think we should have that discussion about new features, but for existing ones, it's likely to reach the point of status quo being cheaper, and therefore better ;)

X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: Move engagement_level from core Activity to an extension?
October 06, 2013, 12:58:45 am
Probably the solution at this point would be to leave it as a core field but allow it to be disabled/hidden in the UI via some admin config screen.
BTW - I thought "engagement level" only appears if CiviCampaign component is enabled - was I wrong about that? If so should we do that?
Try asking your question on the new CiviCRM help site.

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: Move engagement_level from core Activity to an extension?
October 06, 2013, 04:03:04 am
@coleman you are right.

However, some might want to have surveys or petition but not engagement index?

X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Discussion »
  • Extensions (Moderators: mathieu, totten, kasiawaka) »
  • Move engagement_level from core Activity to an extension?

This forum was archived on 2017-11-26.