Dashboard collaborator

• US 10,013,667 B2
• Filed: 11/29/2012
• Issued: 07/03/2018
• Est. Priority Date: 11/15/2012
• Status: Active Grant

• Current Assignee: Business Objects Incorporated (SAP SE)
• Original Assignee: Business Objects Incorporated (SAP SE)
• Inventors: Li, Zi Qin, Zhang, Jinming, Chen, Chunsen
• Primary Examiner(s): Pham, Tuan A
• Assistant Examiner(s): Gurmu, Muluemebet
• Application Number:
  US13/689,711
• Publication Number:
  US 20140136489A1
• Time in Patent Office: 2,042 Days
• Field of Search: 707691
• CPC Class Codes: G06Q 10/0637 Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
• CPC Class Codes: G06Q 10/0639 Performance analysis of employees; Performance analysis of enterprise or organisation operations

Abstract

Described herein is a technology for designing a dashboard. In some embodiments, first and second dashboards are provided. Conflict analysis on the first and second dashboard is performed. The conflicts are resolved if any conflicts are detected. The first and second dashboards are merged to form a merged dashboard if no conflicts are detected or after resolving the conflicts.

Claims

1. A computer implemented method of non-sequential collaboration in designing a dashboard by different designers comprising:

providing, to a dashboard merger,

a first dashboard file of a first dashboard from a first designer, the first dashboard file containing first components of the first dashboard, the first dashboard displays the first components for visualizing first data, the first dashboard file includes a first dashboard metadata file and a first dashboard data file, wherein

the first dashboard metadata file comprises first metadata, the first metadata includes information of the first components of the first dashboard, and

the first dashboard data file comprises the first data bound to the first components of the first dashboard, and

a second dashboard file of a second dashboard from a second designer, the second dashboard file containing second components of the second dashboard, the second dashboard displays the second components for visualizing second data, the second dashboard file includes a second dashboard metadata file and a second dashboard data file, wherein

the second dashboard metadata file comprises second metadata, the second metadata includes information of the second components of the second dashboard, and

the second dashboard data file comprises the second data bound to the second components of the second dashboard;

performing conflict analysis on the first and second dashboard files, including the first dashboard metadata and data files and the second dashboard metadata and data files;

in the event no conflicts are detected, merging the first and second dashboard files to form a merged dashboard file of a merged dashboard;

in the event conflicts are detected, resolving the conflicts and merging the first and second dashboard files to form a merged dashboard file of a merged dashboard;

wherein merging the first and second dashboard files to form the merged dashboard file comprises

 

combining the first and second dashboard metadata files together to form a merged metadata file,

 

combining the first and second dashboard data files together to form a merged data file, and

 

the merged metadata file and the merged data file; and

wherein the dashboard merger facilitates non-sequential collaboration by the different designers in designing a dashboard.

2. The method of claim 1 wherein the first and second metadata files are in .xml format files and the first and second data files are in xldoc format files.

3. The method of claim 1 wherein the conflict analysis comprises:

comparing the first and second dashboard metadata files for any metadata conflicts;

resolving the metadata conflicts between the first and second metadata files in the event metadata conflicts are detected;

merging the metadata of the first and second dashboard metadata files after resolving the metadata conflicts when metadata conflicts are detected or when no metadata conflicts are detected;

comparing the first and second dashboard data files for any data conflicts;

resolving the data conflicts between the first and second data files in the event data conflicts are detected; and

merging the data of the first and second dashboard data files after resolving the data conflicts when data conflicts are detected or when no data conflicts are detected.

4. The method of claim 3 wherein the first and second metadata files are compared prior to comparing the first and second dashboard data files.

5. The method of claim 3 wherein the resolving conflicts comprises an automatic mode of conflict resolution or a manual mode of conflict resolution.

6. The method of claim 5 wherein the metadata conflicts are resolved in the manual mode and the data conflicts are resolved in the manual or the automatic mode.

7. The method of claim 6 wherein a user may select whether the data conflicts are resolved in the manual or the automatic mode.

8. The method of claim 7 wherein the data conflicts are effectively resolved in the manual mode when there are metadata conflicts, regardless of whether the user has selected the automatic or manual mode.

9. The method of claim 3 wherein the metadata conflicts are resolved by:

requesting a user to select a dashboard from the first or second dashboard to be a base dashboard, wherein a non-selected dashboard from the first or second dashboard is a non-base dashboard;

metadata which are not in conflict are used; and

for metadata which are in conflict, the metadata of the base dashboard is used and the metadata of the non-base dashboard is not used.

10. The method of claim 9 wherein:

the metadata of the base dashboard is copied into a merged metadata file;

the metadata of the non-base dashboard which are not in conflict are copied into the merged metadata file; and

the metadata of the non-base dashboard which are in conflict are not copied into the merged metadata file.

11. The method of claim 6 wherein data conflict resolution in the automatic mode comprises:

determining for data conflicts between the first and second dashboard data files;

merging the data of the first and second dashboard data files into a merged dashboard data file when no data conflicts are detected; and

merging and updating binding of the data from the first and second dashboard data files into a merged dashboard data file in the event data conflicts are detected.

12. The method of claim 6 wherein data conflicts resolution in the manual mode comprises:

requesting a user to select a dashboard from the first or second dashboard to be a base dashboard, wherein a non-selected dashboard from the first or second dashboard is a non-base dashboard;

data of the base dashboard are used in the merged dashboard; and

for data which are in conflict, the data of the base dashboard is used and the data of the non-base dashboard is not used.

13. The method of claim 12 wherein:

data of the base dashboard are merged into a merged dashboard data file; and

data of the non-base dashboard which are in conflict are copied into the merged dashboard data file but are not used.

14. A non-transitory computer-readable medium having stored thereon program code, the program code executable by a computer to perform a method for collaboration in designing a dashboard by different designers comprising:

selecting a first dashboard file of a first dashboard from a first designer, the first dashboard file containing first components of the first dashboard, the first dashboard displays the first components for visualizing first data, the first dashboard file includes a first dashboard metadata file and a first dashboard data file, wherein

the first dashboard metadata file comprises first metadata, the first metadata includes information of the first components of the first dashboard, and

the first dashboard data file comprises the first data bound to the first components of the first dashboard;

selecting a second dashboard file of a second dashboard from a second designer, the second dashboard file containing second components of the second dashboard, the second dashboard displays the second components for visualizing second data, the second dashboard file includes a second dashboard metadata file and a second dashboard data file, wherein

the second dashboard metadata file comprises second metadata, the second metadata includes information of the second components of the second dashboard, and

the second dashboard data file comprises the second data bound to the second components of the second dashboard;

performing conflict analysis on the first and second dashboard files, wherein the conflict analysis comprises

analyzing the first and second dashboard metadata files, and

analyzing the first and second dashboard data files;

when no conflicts are detected, merging the first and second dashboard files to form a merged dashboard file of a merged dashboard;

when conflicts are detected, resolving the conflicts and merging the first and second dashboard files to form a merged dashboard file of a merged dashboard;

wherein merging the first and second dashboard files to form the merged dashboard file comprises

combining the first and second dashboard metadata files together to form a merged metadata file,

combining the first and second dashboard data files together to form a merged data file, and

the merged metadata file and the merged data file; and

wherein the method facilitates non-sequential collaboration by the different designers in designing a dashboard.

19. The non-transitory computer-readable medium of claim 14 wherein the conflict analysis comprises:

comparing the first and second dashboard metadata files for any metadata conflicts;

resolving the metadata conflicts between the first and second metadata files in the event metadata conflicts are detected;

merging the metadata of the first and second dashboard metadata files after resolving the metadata conflicts when metadata conflicts are detected or when no metadata conflicts are detected;

comparing the first and second dashboard data files for any data conflicts;

resolving the data conflicts between the first and second data files in the event data conflicts are detected; and

merging the data of the first and second dashboard data files after resolving the data conflicts when data conflicts are detected or when no data conflicts are detected.

20. The non-transitory computer-readable medium of claim 14 wherein a user may select whether the data conflicts are resolved in a manual or automatic mode.

15. A system for designing dashboards comprising:

a data source for storing dashboard files of dashboards, wherein the data source includes

a first dashboard file of a first dashboard from a first designer, the first dashboard file containing first components of the first dashboard, the first dashboard displays the first components for visualizing first data, the first dashboard file includes a first dashboard metadata file and a first dashboard data file, wherein

the first dashboard metadata file comprises first metadata, the first metadata includes information of the first components of the first dashboard, and

the first dashboard data file comprises the first data bound to the first components of the first dashboard, and

a second dashboard file of a second dashboard from a second designer, the second dashboard file containing second components of the second dashboard, the second dashboard displays the second components for visualizing second data, the second dashboard file includes a second dashboard metadata file and a second dashboard data file, wherein

the second dashboard metadata file comprises second metadata, the second metadata includes information of the second components of the second dashboard, and

the second dashboard data file comprises the second data bound to the second components of the second dashboard;

a processor that implements a dashboard design module, wherein the processor is configured to execute processing including,

selecting the first and second dashboard files of the first and second dashboards from the data source,

performing conflict analysis on the first and second dashboard files,

in the event no conflicts are detected, merging the first and second dashboard files to form a merged dashboard file,

in the event conflicts are detected, resolving the conflicts and merging the first and second dashboard files to form a merged dashboard file,

wherein merging the first and second dashboard files to form the merged dashboard file comprises

combining the first and second dashboard metadata files together to form a merged metadata file, and

combining the first and second dashboard data files together to form a merged data file, and

the merged metadata file and the merged data file; and

wherein the dashboard design module facilitates non-sequential collaboration by different designers in designing a dashboard.

16. The system of claim 15 wherein the first and second metadata files are in .xml format files and the first and second data files are in xldoc format files.

17. The system of claim 16 wherein the conflict analysis comprises:

comparing the first and second metadata files for any metadata conflicts;

resolving the metadata conflicts between the first and second metadata files in the event metadata conflicts are detected;

merging the metadata of the first and second dashboard metadata files after resolving the metadata conflicts when metadata conflicts are detected or when no metadata conflicts are detected;

comparing the data files of the first and second dashboard data files for any data conflicts;

resolving the data conflicts between the first and second data files in the event data conflicts are detected; and

merging the data of the first and second dashboard data files after resolving the data conflicts when data conflicts are detected or when no data conflicts are detected.

18. The system of claim 15 wherein the resolving conflicts comprises an automatic mode of conflict resolution or a manual mode of conflict resolution.