Reviews before committing additions or changes to an SVG repositories content is essential to quality assurance of the data as well as avoiding common pitfalls that come with not vetting entries before mistakes and inferior work is being submitted. So a templating mechanism has been integrated into the studio designer whereby users can save their work to a portable template during their design sessions and only submit it for saving into the repository once it has been approved meeting specifications.
Symbols can be created through a process of shaping them in a designer whereby an initial shape can be created and other shapes can assert an influence over it such as add, subtract, exclude or intersect their own area. All these relationships can be contained in a portable template persisted in an industry standard format called JSON (Java Script Object Notation) residing in text annotated by curl braces. A studio app can export and import these into compositions. It is advised to save to one during all design sessions and submit them for review by the repository manager or domain expert before finally committing them to the repository. This is also noted in the work flow which we advise to be followed.
Symbology can be created through a process of adding and editing shapes, text and symbols on a canvas. However references to symbols are unique to each repository having their own libraries of symbols. All these relationships can be contained within a portable template persisted in an industry standard format called JSON (Java Script Object Notation) residing in text annotated by curl braces. The studio app can export and import these into compositions. It is advised to save to one during design sessions and submit them for review by the repository manager or the domain expert before finally committing their contents to the repository. This is also noted in the work flow that we advise to be followed.
Animation can be created through a process of adding behavior to elements on a canvas. However references to elements are unique to each repository having their own libraries of visual elements. All these relationships can be contained within a portable template persisted in an industry standard format called JSON (Java Script Object Notation) residing in text annotated by curl braces. The studio app can export and import these into animations. It is advised to save to one during design sessions and submit them for review by the repository manager or the domain expert before finally committing their contents to the repository. This is also noted in the work flow that we advise to be followed.
The full activity history for the tasking, linguistic model and graphic model designing sessions is facilitated through a date range and user search utility to view the entity changes in their applicable designers. They are present in both the portal and studio publisher app. NB : It should be emphasized that the review should first start with viewing the templates before they are committed and not from the perspective of reviewing from the work history because that would make the intentional usage of the templates redundant. Work history can be a very effective tool for tracking down wrong doing and provide evidence for disciplinary measures. It also can be used in performance reviews accessing a users work.