E-mail
This page contains specification and implementation design information for a Human Rights Defender contract of the core team.
Case Timeline Definition
- Open Case
- (+6 weeks) Case update
Case and activity categorisation
Activities
Legacy db column: activity_tag1_id
Legacy field label: Case Activity Type
Values from case_activity_type option group
Destination: civicrm_activity.activity_type_id
There is some activities which don't have activity_tag1_id set (value: 0). For those, the handling algorythm is as follows:
- Those legacy activities, which have 'FL Activity' activity type (in legacy database), should be marked as "Legacy Case Activity Type". There is slightly less than 300 of those.
- For those legacy activities which DON'T HAVE 'FL Activity' activity type (in legacy database), activity type should stay as is.
Legacy db column: activity_tag2_id
Legacy field label: Communication
Values from communication_medium option group
Destination: civicrm_activity.medium_id
Rows with 0 values should not have any value set (db default stays).
Legacy db column: activity_tag3_id
Legacy field label: Violation Type
Values from f1_case_violation option group
Destination: new Tag set for activities - "Violation Type"
Rows that have NULL, 'null' or other empty value (like ^H), should not have any value set (db default stays).
Cases
Legacy db column: case_type_id
Legacy field label: Case Type
Values from case_type option group
Destination:
We will assume that case type is NOT a multi-value field. Those records that have multiple values will have Case Type set to one, and the rest of values (2 or 3) should be migrated to new Tag set for cases - "Supplementary Case Type"
Legacy db column: casetag2_id
Legacy field label: Case Sub Type
Values from f1_case_sub_type option group
Destination: new Tag set for cases - "Case Sub Type"
As above, db default if empty value.
Legacy db column: casetag3_id
Legacy field label: Violation
Values from f1_case_violation option group
Destination: new Tag set for cases - "Violation"
As above, db default if empty value.
Case migration
Newly created cases don't follow timeline rules set in CiviCase XML files. In order to avoid compatibility problems later on, for each case, we need to create Open case activity and Case Review activity 6 months after case start, both Scheduled.
Field mapping:
Built-in fields stay as they are.
Issues:
- Check how contact photos are stored - if they are in custom fields, need to push one of them to built-in contact photo.
Custom fields:
 | Those files were migrated using regular upgrade process, no need to do anything, apart from contact photo mentioned above. |
Front Line Contact - Extending all contact types:
Languages spoken |
Alphanumeric |
Multi-Select |
Not required |
Contact photo |
File |
File |
Not required |
Other photo |
File |
File |
Not required |
Country(s) working on |
Alphanumeric |
Multi-Select |
Not required |
Front Line Human Rights Defender Contact - Extending Individuals maybe use contact subtype here?
Inactive HRD Status |
Alphanumeric |
Select |
Not required |
Human Rights Defender Type |
Alphanumeric |
Select |
Required |
Front Line ID Card issued? |
Yes or No |
Radio |
Required |
Front Line ID Card date of issue |
Date |
Select Date |
Not required |
Front Line ID Card information |
Alphanumeric |
Text |
Not required |
Visas and passport section - Extending Participants
Passport number |
Alphanumeric |
Text |
Not Required |
Passport scan image |
File |
File |
Not Required |
Irish visa status |
Alphanumeric |
Select |
Not Required |
Irish visa place of application |
Alphanumeric |
Text |
Not Required |
Irish visa application date |
Date |
Select Date |
Not Required |
Irish visa number |
Alphanumeric |
Text |
Not Required |
Transit visa status |
Alphanumeric |
Select |
Not Required |
Transit countries |
Note |
TextArea |
Not Required |
Travel and Accomodation - Extending Participants
Type of the room |
Alphanumeric |
Select |
Not Required |
Arrival from |
Alphanumeric |
Text |
Not Required |
Arrival flight number |
Alphanumeric |
Text |
Not Required |
Arrival date and time |
Date |
Select Date |
Not Required |
Departure to |
Alphanumeric |
Text |
Not Required |
Departure flight number |
Alphanumeric |
Text |
Not Required |
Departure date time |
Date |
Select Date |
Not Required |
Travel Notes |
Note |
TextArea |
Not Required |
FL Card & Registration Form - Extending Participants
Need FL Card |
Yes or No |
Radio |
Not Required |
FL Card Language |
Alphanumeric |
CheckBox |
Not Required |
Registration Form Scan |
File |
File |
Not Required |
Attendee Notes - Extending Attendee
Testimony |
Note |
TextArea |
Not Required |
Testimony Scan |
File |
File |
Not Required |
Speaker Notes - Extending Speaker
Speach notes |
Note |
TextArea |
Not Required |
