For the second talk of our Documentation Tool Design day, we’ll be hearing from Dani Katenkamp about her approach to making an app to visualize the Historical Choctaw Corpus. Let’s use this thread to discuss the project and ideas that come up!
2 Likes
Another set of applications for a JSON export format from FLEx. This is needed for so many reasons!
3 Likes
Great talk! A few practical questions:
a.) being able to see texts selected by the years in which they are produced is a great idea. But on a practical level, does this require a person to code all the texts in FLEx?
b.) Same question for translation status. How do we make this work?
3 Likes
Have you tried the use of multiple windows in FLEx? It does allow you to view both a text and the concordance.
(But like a lot of things in FLEx, it could definitely be improved.)
2 Likes
For our corpus all the texts have the year of composition in the titles, so whether a text is within the range or not is automatically taken from there. Similarly, the translation status is based on looking at each text and seeing if there is text in the two translation fields.
So the translation status doesn’t have to be coded (which is good, cause the idea is that it is continually changing). The years need to be coded in the sense that we’ve been putting them at the beginning of the titles, but there’s no additional work we would have to do while creating/inputing texts.
tl,dr: these filters can function without requiring any more metadata than we’ve been putting into the texts thusfar
1 Like
Also, I should have said that it would be amazing to be able to share these texts with non-linguists in a simpler way. Right now, I feel like our tools limit the ways that we can collaborate with Native people as well as people outside the bubble of documentary linguistics.
3 Likes