Report Generation System Retaining Annotations via Bookmarks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current report generation tools lose analyst annotations when regenerating reports due to data set modifications, requiring significant rework and time, especially when issues with the data set necessitate revisions to visualizations.
Innovation Solution
A system that automatically generates and regenerates reporting documents based on test data while retaining annotations by using report templates with bookmarks, allowing visualizations to be updated without removing annotations, and using scripts like Visual Basic and R for data analysis and visualization insertion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the reporting document is regenerated automatically based on modified test data, then the data accuracy and reliability are improved, but the analyst annotations are lost and significant rework time is required
Solution Approach 1:
The reporting document is segmented into distinct components: automated visualizations derived from test data and manual analyst annotations. During regeneration, only the visualization portions are automatically updated while the annotation portions are preserved separately, allowing data accuracy to improve without losing valuable analyst insights.
Solution Approach 2:
Analyst annotations are extracted and preserved before the regeneration process begins. This preliminary action ensures that when the report is regenerated with updated visualizations, the annotations are already saved and can be re-integrated, preventing time loss from rework.
2Stability of the object's composition
If the entire reporting document is regenerated when data set issues are identified, then the data consistency is improved, but the analyst work product is erased and significant time is lost
Solution Approach 1:
Analyst annotations are extracted from the reporting document before regeneration occurs. This separation allows the document to be regenerated with consistent data while the extracted annotations are preserved outside the regeneration process, preventing information loss.
Solution Approach 2:
The regeneration process selectively discards only the automated visualization portions that need updating while recovering and preserving the analyst annotations. After regeneration, the annotations are re-integrated, achieving data consistency without permanent loss of analyst work product.
3Loss of information
If manual insertion of data and visualizations is performed, then the analyst can add detailed notes and explanations, but the report generation time and effort are significantly increased
Solution Approach 1:
The system merges automated report generation capabilities with manual annotation capabilities. Automated processes handle data processing and visualization creation quickly, while analysts can still add detailed notes and explanations. This combination reduces overall generation time while preserving comprehensive information.
Solution Approach 2:
The system enables continuous workflow where automated generation and manual annotation occur in sequence without interruption. Analysts can add notes during or immediately after automated generation, eliminating the need for separate manual creation steps and reducing total time while maintaining information quality.
Data Source
AI summary
The present disclosure involves systems, software, and computer implemented methods for automatically generating reporting documents based on contents of an associated set of test data. One example method includes receiving a request to generate a new report, the request identifying a report template, a set of test data, and a report name associated with the request. A repository stores the test data and report templates, each template associated with an initial set of bookmarks, each bookmark associated with a particular location. A copy of the template is generated and stored as the identified report name. Based on the test data, a set of visualizations to be inserted into the new report are identified. Bookmarks associated with each of the visualizations are inserted into the new report. Each visualization is then generated and inserted at the location of the corresponding bookmark. The updated version of the report is then stored.


