STAC 3 Collaboration Meeting Summary 2/25/2026

STAC 3 Collaboration Meeting Summary 2/25/2026

1) Meeting Format

  • Purpose is to cover feature usage, design intent, and workflow approach.
  • Tickets can still be raised, but the group time is better spent on platform guidance that applies broadly.

2) Upload Center vs Image Tab Folder Upload

Issue / Question

asked whether Upload Center supports:

  • Bulk uploads (multiple files)
  • Drag/drop of an entire folder
  • Preserving folder/file structure (folders + subfolders)

clarified:

  • Upload Center currently supports multiple files, but not folder structure if you drop a folder.
  • Upload Center’s current process reads files, not folder trees.
  • Preserving folder structure is currently handled via Image Tab drag/drop, not Upload Center.

explained Upload Center mechanics:

  • Files are moved to a controlled location so STAC can lock and manage them.
  • Adding folder structures introduces naming/organizational complexities that require careful implementation.

noted that if folder drag/drop fails on the Image Tab, it’s usually due to:

  • Local agency validations/configuration (allowed file types, restrictions)
  • Empty folder / no supported files
  • Not a technical “limit” of the feature itself

dragging a folder with subfolders into the Image Tab:

  • STAC uploaded the contents
  • Prompted to name/classify the folder (example: “Photos / Crime Scene”)
  • Created the folder container inside the case and preserved the structure

3) “My STAC” Landing Screen + Menu

the intent behind My STAC as the default landing page and how it replaces older menu patterns.

  • Consolidates “what needs attention” (documents, requests, image review, upload center, etc.)
  • Reduces “I didn’t know I had work waiting” by surfacing counts and queues
  • Moves away from older “Options/Activities menu” reliance

4) Case List Workflow: Right-Click Actions + “Don’t Lose Your Place”

two STAC 3 workflow pillars:

  1. Right-click context actions
  2. Add/update records without losing your spot (especially court workflows)
  • Right-click from case list enables common actions (edit, wizards, tag actions, etc.)
  • Designed for court usage: quick actions while running a docket without navigating away
  • Docking/undocking panels supports different device setups (monitor vs laptop)

The goal is speed + continuity:

  • Add a note, relationship, event from the list view
  • Maintain filter/sort position and keep working

5) Relationship Tab: Detail Panel Tabs (Witness/Victim/VOCA/VAWA) + Navigation Speed

redesigned Relationship Tab where the right-side details panel changes based on the selected record type.

Improvements Highlighted

  • Selecting a witness shows witness detail panels
  • Selecting a victim exposes additional tabs, including VAWA/VOCA
  • Faster navigation victim-to-victim or witness-to-witness without opening buried option menus

valuable for cases with many relationships:

  • Witness-heavy cases (dozens+)
  • Victim workflows requiring fast VOCA/VAWA review and editing

6) UI Suggestion: Visual Indicator When “Detail Tabs Have Data”

proposed a grid-level indicator to show when something exists in the right-side detail tabs, such as:

  • icons per tab
  • single indicator icon (triangle/exclamation)
  • bolding of relationship row when additional info exists
  • hover indicator similar to “special instruction” markers used elsewhere

Concerns / Discussion

highlighted constraints:

  • If there are 5 tabs, do you show 5 icons? (visual clutter)
  • Must be meaningful across agencies (not just one circuit’s priorities)
  • Icon meaning must be universally understood (new staff onboarding)
  • Accessibility: colors alone don’t work for color-blind users; icons must be clear
  • They’ve had prior complexity with “minor highlighting” and icon translation
  • Acknowledged and on backlog, but not a priority right now
  • CIP open to exploring alternatives:
    • hiding the right panel when empty
    • showing panel only via right-click
    • other UX approaches as they continue testing

7) Relationship Grids: Grouping, Sorting, Record Count (Performance vs Usability)

grouping relationships by dragging a column header into the grouping area.

  • Group by relationship type (or any field)
  • Multi-level grouping supported
  • Sort order can be changed within groups
  • Works alongside filtering

Record Limit

  • Early STAC 3 initially limited grids to 100 records for performance
  • Feedback led to a user-selectable record load count (100 / more / up to 1000)
  • the tradeoff:
    • more records = more load on workstation/browser
    • but users can choose what they need per workflow

8) Copy Relationships Between Cases (Drag/Drop)

a major workflow improvement:

  • Select one or multiple relationships
  • Drag to another case to copy relationships (faster than old copy/paste workflow)

9) Relationship Right-Click Functions: Directory Updates “On the Fly”

Right-click within relationships supports quick actions without leaving the case.

  • Edit relationship (double-click works too)
  • Add relationship / delete
  • Retrieve all cases for that directory person
  • Add/update address/phone/email directly from relationship context
  • Export to Excel
  • Send forms (example: victim impact statement / PD questionnaire)

10) Text Messaging + Replies + Automation Rules (Programmatic vs Manual)

Manual Text Messages

  • Can send one-off manual message and allow replies (creates a live conversation)
  • Reply setting is important because of user expectations: if it looks like texting, people expect reply capability

Programmatic Messages (Automated)

  • Many offices send reminders (hearing reminders, deposition reminders, etc.)
  • By default, reply is blocked for automated notices to avoid confusion (recipient may assume they’re texting a staff person)

Communication Tab

  • Centralized view of:
    • texts (formatted like texts)
    • emails (formatted cleanly with recipients)
  • Shows message type, source, and recipient destination details (phone/email)
  • Includes new Communication history in Directory as well (person-level history, not only case-level)

11) Multilingual Translation for Texting

  • Directory record holds:
    • default language
    • translator flag/settings
  • Messages are translated as they go (send in English → recipient receives in their language; replies translate back)
  • Spanish, Creole, Portuguese
  • Expanded list mentioned: German, Italian, Russian, Polish
  • additional languages added via language code table (examples: Dutch, Ukrainian)

12) Translation Verification

If a message is sent in English and translated to Spanish:

  • how does staff verify the translation occurred and what language was used?
  • Translation is triggered by directory language + translator settings
  • CIP is considering enhancing Communication view to show:
    • translated version “as sent”
    • an explicit indicator of what language was used
  • suggested possibly adding a language label next to message metadata
  • STAC 2 had reporting that showed translated from/to and reply chain; that report should work in STAC 3 but may need deployment

13) Communication Report (Case Summary of All Comms)

  • Communication Report summarizes communications for a case
  • One communication per page (useful for court packets / documentation)
  • Includes properly formatted email and text content

14) Best Practice: Use Help Desk Portal + Knowledge Base (Not Email)

agencies to submit tickets through the portal because it captures:

  • priority, category
  • release/version number
  • structured “expected vs actual”
  • attachments and error messages

Email-created tickets often lack key fields → slows triage and prioritization.

  • Version/release field is critical due to:
    • frequent patches
    • 6-week release cadence
  • Portal tickets are visible to the submitting agency’s users (not other agencies)

Q&A

 Upload Center & Image Uploads

Q: Can Upload Center upload multiple files at once?
A: Yes. Upload Center supports selecting/pasting multiple files in a single job.

Q: Can Upload Center accept a folder and preserve the folder structure?
A: Not currently. Upload Center reads files and does not retain folder trees/subfolder structure when dropping a folder.

Q: What is the correct way to upload a folder with subfolders and keep structure?
A: Use the Image Tab drag/drop folder upload, which supports folders and preserves structure.

Q: Why might folder drag/drop into the Image Tab fail?
A: Typically due to agency validations/configuration (file type restrictions), empty folders, or unsupported files. If it persists, submit a ticket with examples.

Q: What is the “best” method for bulk video ingestion?
A: For high-volume videos (Axon/FHP/Motorola links), use the Hyperlink Center, which downloads/extracts to cloud and returns the file list ready to attach.

Q: Can STAC auto-upload files from a monitored folder?
A: Yes. Agencies can use a monitored directory workflow (commonly for e-service or inbox attachments), where STAC continuously uploads new files.

My STAC, Navigation, and Right-Click Workflow

Q: What is the goal of the “My STAC” landing screen?
A: To give a dashboard-style view of work queues (documents, requests, image review, upload center, etc.) and reduce missed tasks that used to live inside menus.

Q: Why is right-click emphasized in STAC 3?
A: It’s a common interaction pattern in most apps and enables context-sensitive actions without losing place in lists or tabs.

Q: How does “don’t lose your place” help court workflows?
A: Users can add notes/relationships/events from list context without navigating away, preserving filters, sorting, and case position while working a docket.

 Relationship Tab Enhancements

Q: What changed in the Relationship Tab compared to STAC 2?
A: The details panel is now record-sensitive (witness vs victim) and includes accessible tabs like witness info, VOCA/VAWA, etc., without opening buried menus.

Q: Can users group relationships by type (or other columns)?
A: Yes. Drag a column into the grouping bar to group; multi-level grouping and within-group sorting are supported.

Q: Why did STAC 3 start with a 100-record grid limit?
A: Performance balancing. STAC 3 now allows users to choose how many records load (up to 1000), with the tradeoff that more records increases workstation load.

Q: Can I copy relationships from one case to another easily?
A: Yes. STAC 3 supports selecting one/multiple relationships and drag/drop copying to another case.

 Text Messaging, Replies, and Translation

Q: What’s the difference between manual and programmatic text messages?
A: Manual messages are one-off staff-to-person messages where reply can be enabled. Programmatic messages are automated reminders/notifications and typically block replies by default.

Q: Why does STAC block replies on automated messages?
A: To avoid confusion—recipients may assume they are texting a staff member and expect immediate interaction.

Q: How does translation work for text messages?
A: Translation is triggered by directory settings: the person’s default language + translator flag. Messages translate outbound and inbound for the conversation.

Q: Can users see the original message and the translation?
A: Users can view original text and translated result in the communication history. CIP discussed adding clearer “translated version as sent” and/or explicit language indicator.

Q: What languages are supported?
A: Common ones mentioned include Spanish, Creole, Portuguese, plus expanded support including German, Italian, Russian, Polish, Dutch, Ukrainian (via language code table updates).

Q: How can staff verify translation was used for a specific person?
A: Check the directory for language and translator settings. CIP is evaluating adding a visible language indicator per message for easier verification.

 Communication Tab and Communication Report

Q: What does the Communication Tab show?
A: All communications for the case (texts formatted like threads; emails formatted with recipients), along with metadata like message type and destination.

Q: What is new about communications in the Directory?
A: STAC 3 provides person-level communication history in Directory (useful when communicating across multiple cases).

Q: What is the Communication Report used for?
A: A printable court-friendly summary of all case communications, typically one communication per page.

Q: What if the Communication Report errors or is missing?
A: Submit a ticket with your release number and error details; CIP noted they would investigate an error observed by Edward.

 Help Desk / Knowledge Base Best Practices

Q: Why submit tickets through the portal instead of email?
A: Portal submissions capture priority/category/version/expected vs actual/error fields and attachments, enabling faster triage and better support.

Q: Why is the release/version number so important?
A: Because updates and patches are frequent. Support needs to know what version you were running when the issue occurred.