Skip to content

Link published notes to their transcript in ShotGrid - #233

Merged
camerontarget14 merged 2 commits into
mainfrom
feature/publish-link-to-transcript-with-notes-revised
Oct 20, 2026
Merged

camerontarget14 merged 2 commits into
mainfrom
feature/publish-link-to-transcript-with-notes-revised

Conversation

@camerontarget14

Copy link
Copy Markdown
Collaborator

Summary

In 5 file changes, and with much less 'diff bloat' - everything in the prodtrack provider and not in storage (to avoid conflicts between SG and mongo as disccussed with @jspada200 )

Now, when a note is published or republished, we set its sg_linked_transcript to the version's newest transcript row (looked up in ShotGrid). The link is written as the script user and is best effort: a missing row or field logs a warning and the note still publishes.

The Publish dialog publishes transcripts before notes so new notes are created already linked.

Testing

  • I have tested these changes locally
  • I have run all relevant automated tests
  • I have verified this does not break existing workflows
  • For changes that can be tested in UI, I have included screenshots or gif animations of the changes.

How I Tested

Stood the application up and tried it out.

Screenshot 2026-10-14 at 9 21 47 PM Screenshot 2026-10-14 at 9 22 30 PM

When a note is published or republished, set its sg_linked_transcript
to the version's newest transcript row, looked up in ShotGrid. The link
is written as the script user and is best effort: a missing row or
field logs a warning and the note still publishes.

The Publish dialog publishes transcripts before notes so new notes are
created already linked.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Cameron Target <camerontarget@gmail.com>
@camerontarget14
camerontarget14 merged commit 9ebea84 into main Oct 20, 2026
4 checks passed
@camerontarget14
camerontarget14 deleted the feature/publish-link-to-transcript-with-notes-revised branch October 20, 2026 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants