We are adding an "Export CSV" button to the multi page table title bar. When this button is clicked it should allow a user to download a CSV file that contains all the field columns and rows. In addition to the field columns we will also add the following columns:
Created At (Date Time)
Created By
Updated At (Date Time)
Content Item ZUID
Questions to Investigate
Describe a situation of why and where the export csv feature will be used? How will this CSV data get consumed by them after downloading it? Are they archiving it? Are they trying to duplicate a model and also have the items carry over with it? Are they trying to transfer data between two instances?
How does the user expect to see:
One to Many, One to One,
Internal Link relationships
Do they want all the columns of the related fields?
Media Field (are they expecting the file name, URL, thumbnail, or a ZUID)
How does the user expect the media field
Are they comfortable with ZUIDs? Do they wish to see the display labels?
Where would they expect to see this feature? Schema or Content?
Intro
We are adding an "Export CSV" button to the multi page table title bar. When this button is clicked it should allow a user to download a CSV file that contains all the field columns and rows. In addition to the field columns we will also add the following columns:
Questions to Investigate
Describe a situation of why and where the export csv feature will be used? How will this CSV data get consumed by them after downloading it? Are they archiving it? Are they trying to duplicate a model and also have the items carry over with it? Are they trying to transfer data between two instances?
How does the user expect to see:
How does the user expect the media field
Are they comfortable with ZUIDs? Do they wish to see the display labels?
Where would they expect to see this feature? Schema or Content?
Figma
https://www.figma.com/file/zOI7oSH3fG1XDmmPzsP6PX/Zesty-3.0-Revamp?type=design&node-id=4288%3A191852&mode=dev&t=qXhv5y0NQio0iSqe-1