JSON Migration Todos

(?) denotes tasks which could be optional or need further discussion to determine if they should be performed.

• DEPLOY

  • Deploy to prod (DUA-719)

• FRONT-END UI

  • App: Show a intrusive popup when user tries to navigate away while SM is generating (DUA-708)
  • App: When Generator throws an errors, allow the user to generate again. (DUA-710)
  • App: UI bug while storymap is generating (DUA-711)
    • Weird gap between section title and first slide when storymap is generating
  • Admin: Create schema viewer for admin (DUA-659)
  • App: Make front end components able to natively handle JSON objects instead of having to convert the object (DUA-707)
    • To render tables we need to convert to TableWithCellIds or TableWithRowIds
    • To render storymap we need to convert to Section[]
    • To generate outline we convert to Storyline (this is already very similar to OutlineCompletion)
  • App: Determine and implement UI solution for handling streaming completions that fail validation
    • The user will see the data completely reset and it will likely be very confusing.

• BACK-END

  • Add completion process UID and completion pass to LLMCalls table (DUA-713)
  • Clean up completion logging (DUA-714)
  • Further expand Slidewriter validation (DUA-720)
  • (?) Merge converter LLM calls in to one per slide
  • (?) Further review of user input storage
    • I want to put a little more thought in to how we store user input data, I think it could be improved
  • (?) Implement custom schema validation that can reprompt LLM with smaller prompts in specific situations
    • Example: If validation fails due to one element having too many words/sentences then we could run a simple LLM call that just prompts the LLM to shortern the text