You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Content Drive: open in the view set by a custom tool's dataViewMode #37964
Custom tools store a view mode, dataViewMode (list or card), which Content Search reads today (view_contentlets.jsp opens in cards when it is card). Content Drive ignores it.
#37930 adds a grid view to Content Drive next to the table, and remembers each user's choice in their browser. Reading the tool's dataViewMode was deliberately left out of #37930 to keep that PR small. This ticket picks it up.
The gap: custom tools open Content Search (/c/<tool id>), not Content Drive, so the Drive never receives a tool's settings today. Making the setting reach the Drive is part of this ticket.
Agreed so far:
The user's remembered view (from Add a grid view to Content Drive #37930) wins over the tool's dataViewMode. The tool's setting only decides the view for users who have not chosen one in that browser.
An empty dataViewMode, or any value other than list or card, counts as unset, and the Drive falls back to the table.
Open question (to settle when this is picked up): how a custom tool brings users into Content Drive. Options discussed:
Option
What it means
Per-tool setting
A new tool setting chooses between Content Search and Content Drive.
All tools open the Drive
Every custom tool opens Content Drive instead of Content Search.
Only on redirect
Tools keep opening Content Search. When a user is redirected to the Drive (Content Search not in their menu), the tool's view mode goes with them.
Acceptance Criteria
The way a custom tool brings users into Content Drive is decided and documented on this issue.
When a custom tool opens Content Drive, the Drive receives that tool's dataViewMode.
A user with no remembered view who opens the Drive through a tool set to card sees the grid view.
A user with no remembered view who opens the Drive through a tool set to list sees the table view.
A user who already chose a view in this browser sees that view, whatever the tool's dataViewMode says.
An empty or unknown dataViewMode opens the table for users with no remembered view.
Description
Custom tools store a view mode,
dataViewMode(listorcard), which Content Search reads today (view_contentlets.jspopens in cards when it iscard). Content Drive ignores it.#37930 adds a grid view to Content Drive next to the table, and remembers each user's choice in their browser. Reading the tool's
dataViewModewas deliberately left out of #37930 to keep that PR small. This ticket picks it up.The gap: custom tools open Content Search (
/c/<tool id>), not Content Drive, so the Drive never receives a tool's settings today. Making the setting reach the Drive is part of this ticket.Agreed so far:
dataViewMode. The tool's setting only decides the view for users who have not chosen one in that browser.dataViewMode, or any value other thanlistorcard, counts as unset, and the Drive falls back to the table.Open question (to settle when this is picked up): how a custom tool brings users into Content Drive. Options discussed:
Acceptance Criteria
dataViewMode.cardsees the grid view.listsees the table view.dataViewModesays.dataViewModeopens the table for users with no remembered view.dataViewModeas it does today, and how it is stored does not change.Additional Context
specs/37930-content-drive-grid-view/spec.md(PR docs(spec): Content Drive grid view as an alternative to the table #37959). Its Clarifications record why this was split out.PortletID.TOOLS, tools catalog endpoints and custom-tool gate on/v1/portlet#37574) returnsdataViewModeaslistorcard.