Hi Luke - these responses are actually really useful. Here are a couple quick thoughts:
Re: re: 1, I think import-export compatibility with FLEx and ELAN would be a really good feature (almost every fieldworker will already have data in this format, or will be planning to have their data move through one or both of these pieces of software over the course of most projects)
Re: re: 2, great - I’m glad I was understanding correctly
In terms of personal thoughts on where Glam could fit in with my workflows: I currently have three projects where collected data (in the target languages Gorwaa, Hadza, and Ihanzu) are, in ELAN, given a rough transcription and Swahili translation in ELAN by local researchers. This data is then archived, but then sits (languishes?) for a LONG time before it can be a) given a standardised transcription and an English translation (which I usually do in FLEx, along with formally glossing and parsing the data). This step (give a standardised transcription, English translation, parse, and gloss), should actually be broken into one or two steps, and could employ students or trained local researchers. I could see Glam being a really nice tool for students or trained local researchers (or a TEAM of the above 
) to take the output of the first step, and clean it up as well as translate it into English. The output could again be archived, and then moved on to FLEx for parsing / glossing when I get the chance (though I’d only be using FLEx here because all of my data currently lives there - I suspect with Glam, one could actually just continue the parsing and glossing there, if one desired).
…and re: collaborations, I’ve got no problem thinking about Glam from the perspective of my own project. Hopefully that might give you some context with which to further develop things. All very exciting!
2 Likes