...
- Personalisation handled pretty well with ALM and DLM, but customisation is not very good at all.
- Personalisation is pretty hard via fragments.xml and we wouldn't like to see this in a user preferences style thing either. Not good from either a user or administrator side of things.
- UC Berkeley would like to be able to push fragments to different groups and allow users to remove/edit some channels, but not others. They would also like to be able to create editable pulled fragments, which users can select to receive only if they are interested in the subject matter. Finally, they would like to be able to ensure that if a pushed fragment changes, users receive any channels added or updated, but retain any other changes they've made to the fragment. It might be nice to have a setting that allows portal managers to decide whether they want to merge user changes into an updated fragment or not. And of course it will be necessary to have a UI that allows users to manage their fragments in a coherent manner.
Actions:
- Need Documentation of conventions, standards and requirements
- Tutorial style guidance to illustrate common usage, styles, design intentions
- Need a Standing Committee / Interest Group / Discussion Group to continue discussion and keep focus around UI. If anyone can devote any time to this- let Jason Shao know
...