Project: Modern Dataverse Feature completion.

[jp-tosca]

Track Remaining Work to Complete the Modern UI Refactor

Parent issue: #123

Summary

This issue tracks the next phase of work required to complete the Dataverse Modern UI (SPA) refactor started in #123: identifying what functionality is still missing from the new UI relative to the legacy JSF application, verifying what backend/API support is needed, and sequencing that work.

Next Steps

1. Define the items left to complete the application

• Use AI code tools to scan the JSF Dataverse codebase and produce a comprehensive list of features representing all functionality available in the legacy UI.
• Compare that list against the current Modern UI development to identify which items are still to be developed.
• Run the resulting gap list through a group of subject-matter experts to collect feedback and catch any hallucinations or mistakes introduced by the AI-assisted analysis.
• Verify the list and create the GitHub issues for Modern Dataverse

2. Verify backend/API readiness

• Run a scan (using Claude) to identify which Dataverse API endpoints will be needed to support the Modern UI features that are not currently available in the API.

3. Plan and track the missing work

• Once endpoint gaps are verified, create individual GitHub issues to track each missing item.
• Size (estimate) each issue.
• Build a plan to interleave endpoint development with UI development, so UI work isn't blocked waiting on missing APIs.

Related

• Previous tracking issue: Project: Dataverse Rearchitecture (Single Page Application) #123

Dataverse-Frontend Issues

• Browser tab title is static instead of reflecting page context dataverse-frontend#1047

[cmbz]

Status: August 2026

• Pending