Matt always makes me think, and today is no exception. He mentioned that I should add transcription abilities to my phonepost. I responded stating that I really didn’t feel like kludging something new into bBlog when I was so close to having Inklog ready to use and then it wouldn’t require a kludge. That’s when I once again got an appreciation for the power of Inklog.
Think about it for a second. What is audio transcription, in this sense? Really, it’s nothing more than a chunk of text that can be edited by multiple people that is associated with a piece of audio. That chunk of text should have revisions, accountability and it should be able to be locked after the author of the audio determines the transcription is complete. Well, essentially, that’s a Wiki page with a lock feature.
Imagine now that you already have an Inklog site. You have the Wiki module installed, and the audio module installed and, of course the blogging module installed. Then you decide you want to be able to moblog audio. You connect an email address to the blogging module and specify which parts of the email should go where (in this case, the text/plain or text/html part is the blog entry itself, and all the other attachments are children of it). Since you have the audio module, the audio child of the blog entry is immediately recognized and linked in to the entry in a default fashion, which can be overridden by the website owner.
Now, imagine you want to add transcription to audio items. That’s easy, you edit your audio display templates to automatically retrieve the text of a child of that audio item called "transcription" which is a Wiki object. Additionally, you provide a link to edit that Wiki object. That’s it. Not only are all your future moblogged audio items transcribable, but every audio item you’ve ever posted is now also transcribable. Maybe you only want certain items to have that ability, that’s fine too. It’s all in the templates, and metadata.