Using Shopping Basket (Search results)
Description
A selected set of data from (multiple) data sources has to be put in the Shopping Basket of the Web Client. From there, it should be possible to launch proprietary authoring applications (e.g. PAK, LMS).
The rich clients should have direct access to the data that was present in the Shopping Basket.
At this stage 2 important remarks need to be made:
First, this is the point where ideally Single Sign On (SSO) becomes active. We expect that from the Web Client shopping basket, the rich client authoring tools will get references to the data, not the data themselves. So, the tools should connect to the data sources to fetch the “mass data”. The corresponding authentication & authorization steps should go unnoticed for the end user because of SSO.
Access to the mass data through OpenMDM must be also realized for the future. Today it is not clear whether the OpenMDM specification is complete enough to achieve this.
Activity
See Eclipse Bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=529569
Added the xsd and an example xml file to this ticket.
The used file extension ".xml" for the handling of the shopping basket is a problem in practice. An openMDM-specific extension for a clear identification would be helpful - see comment Mr. S. Laumann.
We will extend the User Preference Service, that the file extension is configurable via the admin Gui.
See Bugzilla Issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=531090
Shopping basket file extensions
When downloading the contents of a shopping basket, a file with extension `mdm` is generated. The file extension can be changed by adding a preference with key `shoppingbasket.fileextensions`. For example the used extension can be set to `mdm-xml` by setting the value to `{ "default": "mdm-xml" }`.
Assignee
Reporter
Labels
Process Step
Eclipse Project
Status
Components
User Story Name
Implementer (Company)
Customer (Company)
Sprint
Fix versions
Affects versions
Priority
