Many of these things are already in TIM-TheirStory. One I will highlight:
"Transcript is editable." I'm not so sure of this. It depends on the workflow. If you're making an index editing the transcript might not be important. If you are creating some new transcript-index hybrid, it might also not be important. If TIM starts to become a timecoded transcript editor tool, then yes, you might want to start right in with editing a transcript. Also the first step in Frisch's process would be to make a transcript of record... I think Ellis and Frisch's processes need to be scrutinized, then we could figure out just how many panels/version we need (maybe more than 2, but not 6-7 as Frisch's layers suggest).
"Make the URL import option work with Aviary's Share link and video player." is also important. It has its own issue now.
Many of these things are already in TIM-TheirStory. One I will highlight:
"Transcript is editable." I'm not so sure of this. It depends on the workflow. If you're making an index editing the transcript might not be important. If you are creating some new transcript-index hybrid, it might also not be important. If TIM starts to become a timecoded transcript editor tool, then yes, you might want to start right in with editing a transcript. Also the first step in Frisch's process would be to make a transcript of record... I think Ellis and Frisch's processes need to be scrutinized, then we could figure out just how many panels/version we need (maybe more than 2, but not 6-7 as Frisch's layers suggest).
"Make the URL import option work with Aviary's Share link and video player." is also important. It has its own issue now.