Changes between Version 12 and Version 13 of projects/crm_review/report

Timestamp:

Jun 26, 2008, 7:15:17 PM (17 years ago)

Author:

Jamie McClelland

Comment:

--

projects/crm_review/report

@@ -189 +189 @@
 
 Haven't looked under the hood yet.
+
+== CiviCRM ==
+
+=== Basic Member Info ===
+
+Wow. There's really little competition here. CiviCRM was designed with our contact model in mind. There seems to be a way to assign multiple addresses (although I'm having some difficulty getting that to work at the moment). There's a source field (is that for indicating who initially contacted them?). There's plenty of room for multiple emails and you can indicate ones that are "on hold." Simple demographic data (gender and birthday) is in by default. Adding custom fields is a snap. No built-in way to indicate the best time to reach, but every communication mode has a "preferred" one.
+
+There's no way to indicate what type of person it is - although it could be easily added as a new field, or we could use the relationship feature which allows you to determine the relationship of one contact with another (if you enter your own organization you could relate a contact to yourself that way). I can't find anyway to indicate that an address or phone number is bad. And no voter data.
+
+=== Individual vs. Group/Household identity ===
+
+CiviCRM was built to address the issue of groups and households. CiviCRM handles these relationships extremely well.
+
+=== Interactions and Transactions ===
+
+There isn't an endless list of sales related interactions like there is with SugarCRM and vtiger. However, there is flexible event related tracking and the activities related tracking allows you to create arbitrary activities to keep track of.
+
+=== General Reporting/Exporting ===
+
+CiviCRM has three levels of searching: simple, advanced, and a very sophisticated advanced search builder (including custom fields).
+
+The export feature is also really sophisticated - with a wizard that allows users to select the fields to be exported among other options. 
+
+As for reports, there's [http://wiki.civicrm.org/confluence/display/CRMDOC/CiviReport CiviReport] which terrifies me (copy of database on my desktop? tomcat?!?).
+
+=== Access/Controls ===
+
+CiviCRM on Drupal makes extensive use of Drupal's user/role/privileges system allowing for some very fine grained controls. In addition, CiviCRM has additional controls that go beyond Drupal to control access to specific fields.
+
+=== Membership metrics ===
+
+Same as SugarCRM and vtiger ... however, I expect that if we built something like this it would be incorporated into the mainline code (or at least could be packaged as a module).
+
+=== Usability ===
+
+The usability is not as easy or clear as SugarCRM or vtiger - however, not having to dig through the corporate speak makes it a lot easier.
+
+=== Developer/Code ===
+
+Haven't looked under the hood yet.