Evaluate database format for similar languages

[loafofpiecrust]

@GracefulLemming and I have talked a bit about this, but we should do a more formal evaluation of our database structure for handling data from other Iroquoian languages. This should give us ideas of how to pivot to support a wider scope than just our Cherokee data. We should also support linking forms across languages, where there may be influence or shared ancestry.

[GracefulLemming]

I was thinking about this over the holiday actually. I view Ojibwe, Tuscarora, or Oneida as strong candidates.

Ojibwe:

• If memory serves me correctly, Ellen has prior experience with the Ojibwe community in Michigan as well as how an Ojibwe archive could look.
• As an Algonquin language, it is likely highly distinct linguistically, and certainly in writing. While this could be a downside, I think this also allows us to explore our work in an empirically and typologically strong way.
• I also have familiarity with the language due to my other research (even if my knowledge is somewhat sparse).

Tuscarora/Oneida:

• Jeff has some familiarity with these languages, giving us a foot in the door
• These are Iroquoian languages from two different sub-branches. This may lead to more direct connections and translatability from our current structure, but does not lend the same power as a non-Iroquoian language would.

EDIT Following Ellen's report in our weekly meeting, we should consider exploring the Wampanoag language.

Wampanoag

• Local. We would have direct contact to the people and their knowledge, and would be a great way to honor the historical stewards of the land we use in our daily work.
• Much like Ojibwe, this is an Algonquin language, so the same statements apply here as before.

@LN7-cyber and @jgbourns ?