fct_stu_contact_information

[keenzarate213]

No description provided.

[rlittle08]

one major TODO: how to deal with the potential case that e.g. address types & language types might overlap? Currently, this would cause duplicate colnames in fct_student_contact_information, which causes SQL error. I can't yet think of a quick way to handle this case.

A similar but less threatening case is e.g. language types that aren't specific enough. One of the Ed-Fi defaults for Language Use is 'Other', and this is pop'd in Boston, so fct_student_contact_information ends up with a column just called other. Not descriptive. Should we have some way of creating configurable aliases in the bld_ef3__student_wide.. tables, which might resolve both these issues?

I think these would both be fixed by including suffix='_language' in bld_ef3__student_wide_languages, BUT this was probably left out initially bc most of the language descriptors end in _language. So we probably want some code to handle this, i.e. replace _language_language with _language or something. Looks like this would also be applicable in less frequent address types, e.g. "Father Address"

[rlittle08]

Marking this back to draft while we figure out best path forward