Complete Metadata Section Improvements

[SueValente]

User Story

In order to review all metadata attributes in a user-friendly format, data users want the Complete Metadata section to display all imported metadata (not just a subset) with improved formatting and access to raw JSON.

Acceptance Criteria

• GIVEN a user views the Complete Metadata section
  WHEN they review the table
  THEN all metadata attributes imported into data.gov are displayed (not just those not rendered elsewhere)

• GIVEN a user wants to see raw metadata
  WHEN they view the Complete Metadata section
  THEN they see a link to view the raw JSON (similar to old catalog pages)

• GIVEN the Complete Metadata table displays many attributes
  WHEN a user views the section
  THEN the formatting is improved for readability (consider expandable/collapsible format like "View all resources")

• GIVEN a user is unfamiliar with JSON
  WHEN they want to review complete metadata
  THEN they can use the HTML table view instead of only having access to JSON format

Background

Source: External beta feedback from Chris Marcum (christopher.steven.marcum@gmail.com) - 1/26/2026 and Jennifer Walter (DOI/ONRR) - 1/29/2026

Current problems:

• Complete Metadata section only shows subset of metadata (attributes not displayed elsewhere on page)
• Formatting is difficult to read
• No link to raw JSON like old catalog had
• Users who don't understand JSON can't easily review all metadata attributes

Example URL from feedback: https://catalog-beta.data.gov/?q=%22Survey+of+Current+Business%22&sort=relevance

User needs:

• See ALL metadata in readable format
• Access to raw JSON for technical users
• Better visual formatting for easier scanning

Security Considerations

None - display and formatting improvements with no security implications.

Sketch

• Audit which metadata attributes are currently excluded from Complete Metadata display
• Update logic to include all imported metadata attributes
• Add "View Raw JSON" link (determine appropriate endpoint/format)
• Improve table formatting (spacing, alignment, nested object display)
• Consider implementing expandable/collapsible UI pattern if space is a concern
• Test with various datasets that have different metadata completeness
• Ensure JSON objects within table cells are readable