A copy of the recipe on Typescript Archive for how to take a raw Zoom transcript and make it into a readable, formatted FedWiki page and an Keyword in Context image for that page, plus recording the page in a list for later reference.
You will probably want to fork Typescript Archive and Typescript Transcripts and ensure that you can upload assets (raw Zoom transcripts) into Typescript Archive and operate the scripts used by the Frame plugin items to format the uploaded data. If you're outside the dojo.fed.wiki neighborhood you might want to make local copies of the frame scripts. Or maybe that reference is helpful to keep the neighborhood connected.
(Aside): Notionally the Typescript Transcripts page could be dynamically generated by a query script run by a plug-in or HTML frame script like the formatter script itself. Ward's Site Survey Factory could be used as a model for looking for pages which match a "this is a formatted transcript" page and accumulated as site survey results using this pattern. Currently Typescript Transcripts is a manually maintained Markdown table.
Meta: If you're reading or writing this page, what makes it a useful document? Is it useful to have it be a separate call-out page from the how-to steps in Typescript Archive?
## How To Make A Formatted Transcript See Typescript Archive for the steps in context of the uploaded Assets for Zoom transcripts and the frame scripts to process them.<br/> *Italics* in the following steps are commentary and context added to the concrete instructions from the original page.<br/>**Bold** is used to name the steps and clarify what you're manipulating in that step.<br/>1. **From Zoom:** Save Chat *(or have someone send you the chat transcript)*. 2. **In your operating system or editor:** Rename the chat transcript file using the form YYYY-MM-DD.txt *because the chat to wiki page scripts recognize this pattern in offering files to be formatted and indexed*. 3. **In your browser/wiki client**: Log in to your wiki, in wiki mode. *Navigate to Typescript Archive which holds the assets and frame script items*. 4. **Wiki Upload:** Upload the chat transcript to the assets by dropping it on the asset panel item. 5. **Wiki Client Refresh:** Reload the page so that the script frames notice the new asset, or jiggle the frame script items to refresh content. *This will update the lists of raw transcripts offered for formatting and for indexing*. 6. **Wiki Format Script:** Click the file name you uploaded on the *format* panel. *This creates a ghost page named* **Typescript YYYY-MM-DD** *after the file name of the raw Zoom transcript*. 7. **Wiki Fork Ghost Typescript Page:** Scroll way down to the bottom of the ghost **Typescript YYYY-MM-DD** page and hit the flag to fork the page into the wiki. *It's probably OK to prune the Assets file to remove formatted and indexed page if the list of raw transcripts is getting too long*. 8. **Wiki Index Script:** Click the file name on the *index* panel. *This action creates a ghost page with a Keyword In Context index made from the raw transcript*. 9. **Wiki Fork Ghost Index Page:** Scroll way down to the bottom of the ghost KWIC index page and hit the flag to fork the index page into the wiki. 10. **Wiki Add To List Page:** Go to Typescript Transcripts and add links to the formatted typescript and index pages you created. *Add the new line by copying the previous line of linked pages. You can choose to add a Transcriber Notes link or not. I usually add topic highlights or personal thoughts on that day's meeting if I was there.*
Here's some literal wiki editor mark-up for the top of the Typescript Transcripts table, using the three-backticks directive in Markdown to show the pipe and hyphen characters used for a Markdown table. The long page names don't break gracefully in this formatting mode. The wiki editor sees more or less the same thing; it's a little messy when adding a new row to the table.
``` | Transcript | KWIC Index | Notes | |------------|------------|-------| | Typescript 2024-04-03 | Typescript Index 2024-04-03 | Transcriber Notes 2024-04-03 || ```