beamanator / rips-auto-import-cext Goto Github PK

Instead of putting all client data WITH header row, maybe make separate input box for it, so it's not possible to delete it while swapping out new client data to import?

Add a checkbox setting that allow or denies the Auto Import to update existing RIPS info. If checked, Auto Import will change any existing data, based on passed-in import data. If not checked, data in RIPS will only be updated if empty / unchecked.

During testing phases, it may be useful for the extension to automatically archive clients as it creates them.

Pros:

1. users could import large data sets and not worry about manually deleting / archiving later.

Cons:

1. users would not be able to see the clients after the import was over - they would have to search on advanced search instead of via recently accessed clients

Currently we're erroring on Registration page whenever a SWAL pops up. This is usually good, but a SWAL currently pops up via Validation extension when phone number was only 9 characters and an extra 0 was added.

Now we want to make sure the import still imports the client when this minor warning is present

Look for webpage / table templates - lots of free ones online

Amal showed me a bug where, while creating clients, the import just stops on the Registration page, without clicking past it or anything. Maybe the are validation errors or something, but somehow the page does not move forward.

Status bar would contain:

1. Current client # worked on - index or name or unhcr # (in case internet cuts out)
2. percentage completed
3. more?

If someone is using the auto import, make sure they can't add a caseworker as 'Staff' unless it's the one person who is actually 'Staff'

These new services need to be added to the mapping:

1. CHP: "PS Community Hosting Program", // 73
2. DRP: "PS Distribution Response Program", // 77
3. ED: "Education grant", // 79
4. UCYDR: "Unaccompanied Children and Youth Department Reception", // 76
5. UCYNCN: "UCY Naimo Center Nursery", // 78
6. YMPP: "Young Mothers Psychosocial Program", // 75

Here:

If it is recorded that a client can speak multiple languages, how should this be imported into RIPS? I think the options are:

1. Both languages go in "Main Language" field, separated by a comma.
2. Main language and Secondary language go in "Second Language" column.

If method 1 is used, languages will both be added during Registration.
If multiple languages appear in "Main Language" AND another language appears in "Second Language", the Second Language will be over-written.

This shouldn't be possible - we need at least 1 setting to be active at all times, with the default being Skip Conditionally

Outstanding question that needs to be answered before publishing:

Related to 1 - Is it ok to ask users to change column header names (ex: name, gender, dob, etc) in order to match Auto Import specifications, OR is it needed for the Auto Import to accept multiple versions of header names?

Outstanding question that needs to be answered before publishing:

If any data columns are titled incorrectly (nme instead of name, for example), or not recognized (participant name instead of Full Name, for example), should the auto import FAIL or just skip that column? (obviously, required information on registration page can not be skipped).

Definitely needed for DOB on Registration page

Figure out how to nicely & easily display errors on client import

Maybe show separate lists of Successes & Errors?

Right now the auto import only looks at UNHCR number for matches, but instead we should do the following:

1. If UNHCR number is NOT "None"

• Insert UNHCR number into advanced search page
• If results are returned, check for match on UNHCR and Names (first and last)
  --- if UNHCR number matches but either name doesn't match, throw error with how close the names are

2. If UNHCR number is EXACTLY 'None'

• Insert UNHCR number AND first name (maybe last name) into advanced search page
• do similar check as above

Fedena stores many nationalities as country name in English AND in that country's language.
Example: Egypt (Egypt - in Arabic)

In order to fix this, we PROBABLY can just split nationality data on space (nationality.split(' ')) and take the first component.

Issue caused when error doesn't change between tests / imports.

Eventually...