Name: Elli Bleeker
Working group project: ODD visualization
Contribution to group project: in comparison with the other participants, my experience with and knowledge of ODD and JSON was limited. Since it is very useful for anyone working with TEI XML to have at least a basic understanding of these concepts, I was happy to join this working group. At first, my contribution was mainly asking -perhaps obvious- questions about ODD. I’d like to think however that these questions helped to narrow down our goal. At least it was necessary to clearly describe the present state-of-the-art, what is missing, and why an ODD visualizer would be a welcome addition. During the workshop, I assisted with the creation of test data (several project-specific ODD, their transformation to flat ODD and subsequently to JSON); contributed on the design of the treemap and participated in the group discussions.
The general idea and necessity of an ODD visualization was quickly explained, so the group focused on what exactly needs to be visualized and especially, how. The current ODD visualizer of Byzantium does not show the amount of customization. Moreover, it is useful to see on which specific areas the ODD focuses. We were quick in dividing into three smaller groups, each with specific assigned roles depending on our pre-existing knowledge and capabilities.
We decided upon a D3 zoomable treemap for the visualization of the amount of customization. The treemap shows how elements are grouped as well as –by their size or color- to what extent the elements are customized. The zoomable option could also allow to ‘zoom in’ on the customized elements to see the exact changes made.
For all the deliverables (Google doc, Github, demo…), see the reports of the other group members.
It was a very useful experience for me to work on this project. Although from time to time intimidating, the immediate jump from theory to practice was the best way to learn the concept (ODD, flat ODD, TEI schema, JSON, etc…) and to understand the workflow of the different processes. Having to think about the visualization of something that I was not familiar with helped me a great deal in understanding it. Whether the resulting visualization is as clear and useful for others remains to be tested. Nevertheless it is clear that this could be a necessary tool for users of TEI, regardless of their level of experience.
Name: Elena Spadini,
Project: ODD visualization
Contribution: Discussion of the different steps with all the others.
Transformation from .odd to flat odd and then to .json
Contribution to the final design.
All links are available at https://docs.google.com/document/d/1u77xtS1WncnkjCwR9CpTfOYeW65q7meaXz7PM-Y5Tno/edit#heading=h.6w2vysqik2f4
We first discussed if and why it is interesting to have an ODD visualization. It can be useful both during the transcription stage, during which probably the schema continues to evolve; at the end of the process, to check immediatly and intuitive which are the mark-up “zones” where the customization was mainly working; to compare easily different customizations.
We found that the xslt from .odd to .json doesn’t take into account all datas: for instance, if a list of values for an attribute is closed or not and which are the mandatory ones or the suggested ones.
Discover the existence of some resources, as the d3 gallery (https://github.com/mbostock/d3/wiki/Gallery) or the tapasproject.org
Use for the first time new resources, as the different xslt stylesheets for TEI.
Most of all: enjoyng the discussion with scholars with different professional skills and approaches.
Name: Raffaele Viglianti
We wanted to visualize some aspects of a given ODD specification to aid the creation process, or to help the understanding of someone else’s ODD.
We attempted to quantify *how much* an ODD has been customized and show graphically which parts have been curated more and which less.
Nick Laiacona, Performant Software Solutions LLC (www.performantsoftware.com)
Working Group Project:
I worked on the ODD Visualizer project.
Contribution to Group Project:
I adapted the D3 Tree View to work with the data model we developed to characterize the changes to a schema prescribed by a given ODD.
We made use of D3.js, underscore.js, Git Hub, Google Docs. Links to Git repo and our working document are on the TEI Hackathon Wiki page
For me, I didn’t have a specific research question that was addressed by this activity, but nevertheless it was quite worthwhile.
(iii): Learning Outcomes
I think it was very useful to learn more about ODD structure and capabilities from the experts.