Details
-
Epic
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
-
Remote folder for Content library
-
5
-
QDS Oulu - 2025 Week 13/14
Description
Content library has pre-defined directory structure which can be moved around, even to remote directory. This enables user to use assets in their own projects easily.
Assets are shared also with other means, within the organization or between third parties. With little change the content library could be extended to support these too.
In principle, there would be directory 'external' or 'custom' or alike which would have the same directory structure as 'User' folder has and the content of the folder would be made visible if the view is enabled.
Changes in the UI: (each needs separate user story)
- Content Library should not have specific gategories as filters in the UI, the filters would be 'standard assets', 'user specific' and 'external' (or name it better). Each of these would be filters, not either-or buttons.
- User should be able to set the external directory to any remote resource
- OneDrive
- Dropbox
- Git (how to accomplish this?)
- Remote folder is can be read only or r/w, depending on the resource.
- If remote content is updated, user must be notified of the change in Qt DS UI
Validation: Can the Car HMI Kit project deliverables be delivered to customers who have subscription to get it ?
- initial delivery
- updates
Initial delivery (beta) 4.8
- remote directory similar to 'User' folder with separate setting
Full implementation: QDS5
- Filters, multiple different library sources