WORK IN PROGRESS
Misc notes
- Civicrm on dev.kabissa.org seems slow!
- got logged out of joomla several times while importing.
- realized I had to create a user for myself so I can be associated with the orgs/people I added
client_info database field matching issues
- member ID number = match to external ID. editable in backend.
- Question: continue using for new members as they sign up, and display on frontend and use for default short URLs?
- "client_status" 0=inactive, 1=active, 2=pending, 3=canceled, 4=fraud
- Question: how to match up with Civicrm status options?
- Tags and selectable custom data is defined using id numbers, whereas our old system uses clear text, so intermediary field replacement has to be done for the following fields:
- African Regions
- Geographic Scope
- Beneficiary Location
- Organization Size
- Tags/Categories
- Timestamps in client_info are in an unusual linux style not compatible with civicrm's import tool. An interim field translation will be needed for the following field:
- client_stamp
- Question: What is client_stamp used for in MB?
- These fields need to be incorporated as well and matched to equivalents in civicrm. Some are in supported format yyyy-mm-dd but others have an exact time stamp following the date in the same field. Not sure what the effect of this is.
- member_since
- This field is inaccurate for many organizations pre 2003/04 because of a bug in our profile update script that we didn't catch until sometime in 2004. I will look into doing a comparison with old backups to fix them.
- Question: display on frontend to show the longevity of our wonderful members, a la American Express?
- member_since
-
- modified_date
- This field is important as it allows us to see which members are keeping their records up to date/are active.
- modified_date
- STATE field mapping breaks in import - may need to be combined with City for people living, for example, in Ikeja, Lagos (where Lagos is a state).
- Fields to ignore
- "approved" 1 or 0
Configuration changes on civicrm backend:
- Added tags for Organizational Focus
- Need to write up nice descriptions for each tag
- Avoided use of forward slash in tags for tech reasons
- Additional keywords is a searchable custom field
- Relationship types
- Deleted irrelevant relationship types (child of, spouse of etc)
- Kept "employee of"
- AJ: create relationship types here for defining ACL?
- Created Custom data group: "Organizational Data"
-
- Matched up as much as possible with ModernBill field label names
- Kim/Liz: geographic scope -- change name to "community level" from simply "community"? This might help to clarify this for people.
- Lobo: Max length for "Note"/textarea fields?
- Answer: It is NOT possible as of 1.6 to set a max length (ie. 250 characters) for a textarea field. We will have to do this on the frontend using custom component
- Lobo: How to handle Registration number and authority - need to be able to add data in pairs, up to two.
- Created Custom data group: "Financial data"
- Kim/Liz: Should we allow file uploads? Might be more powerful than a textarea field.
- Location types
- Deleted irrelevant location types (home, work etc)
- Created new ones -
- Location 1
- Location 2
- Location 3
- Location 4
- Location 5
- Kim/Liz Question: we have to have unique types for each address in the system - they are used internally by civicrm. How many do we need to offer? Unlimited or just maybe up to 5?
- Multiple Locations
- It is possible to add multiple locations - which each then include address, phone, email. In our specs we had separated these out. Web site is not part of this
- Additional fields for orgs that I left in:
- Latitude/Longitute (may be useful later)
- Instant Messenger - tho not sure how this is relevant for orgs as opposed ot the people working for them.
civicrm.settings.php changes
- expanded countries available to the rest of the world by changing
define( 'CIVICRM_COUNTRY_LIMIT' , 'US' );
to:
define( 'CIVICRM_COUNTRY_LIMIT' , '' ); - AJ: Will need to set up display of addresses in non-US format in the settings file - I'm not sure how to do this.
Labels:
