Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
list_tool [2019/07/04 12:50]
mcgee [Biology Use Case Layer definition]
list_tool [2019/07/11 17:52] (current)
mcgee [Aspect intersection visualization]
Line 51: Line 51:
  
 The definition of layers and the aspects of the data used to characterize them. As part of this project the LIST team explored possibilities for developing a generic solution for layer definition, as part of the data query at the front end as part of the back end data querying. However, ultimately we decided to define a set of layers for each use case, based on the explicit requirements of each. The definition of layers and the aspects of the data used to characterize them. As part of this project the LIST team explored possibilities for developing a generic solution for layer definition, as part of the data query at the front end as part of the back end data querying. However, ultimately we decided to define a set of layers for each use case, based on the explicit requirements of each.
-} + 
-===== Digital Humanities Use Case Layer definition ​=====+ 
 +===== Use Case Layer Definition ===== 
 + 
 +==== Digital Humanities Use Case Layer definition ====
 Over the course of the project, the digital humanities use case evolved to contain multiple aspects. The primary aspect concerns a division by node type. In this aspect nodes are divided by type and appear in only one layer. The types were , people, organisation , location and documents, where documents grouped several types of resource together. Due to the fact that there were several different types of resource merged together this led to there being some duplicate resource nodes, where there were two nodes of differently underlying types. Cleaning of data was beyond the scope of the BLIZAAR project, due to the considerable effort and the fact that it would raise research questions of its own, beyond the domain of multilayer networks. Over the course of the project, the digital humanities use case evolved to contain multiple aspects. The primary aspect concerns a division by node type. In this aspect nodes are divided by type and appear in only one layer. The types were , people, organisation , location and documents, where documents grouped several types of resource together. Due to the fact that there were several different types of resource merged together this led to there being some duplicate resource nodes, where there were two nodes of differently underlying types. Cleaning of data was beyond the scope of the BLIZAAR project, due to the considerable effort and the fact that it would raise research questions of its own, beyond the domain of multilayer networks.
  
Line 71: Line 74:
  
  
-====== Alternate Layer definition approach ======+===== Alternate Layer Data definition approach ===== 
 + 
 +{{:​list_qbe1png.png?​400 |Digital humanities variant of the list view}} {{:​list_qbe2png.png?​400|Defining Layers for the temporal aspect}} 
 + 
 +As an alternative to the specific query for an entity approach described above, we also developed a visual interface to create queries that would return a working data set for the user to visualize as a multilayer network in the front end. 
 + 
 +A list of available entities allows the user to draw a meta network, illustrating the entities to be retrieved. Clicking on an entity in this meta-network displays all the list of all entities related directly to the clicked one in the back end system. The size of the arc is proportional to the reality numbers of each entity type (see image on right above) 
 +===== Aspect intersection visualization ​===== 
 + 
 + 
 +It is also possible to combine aspects of layers to form their intersection , as can be seen in the image below 
 +{{ :​dh_perspectives.png?​600 |}} 
  
 +In this case the aspects describe the entity type aspect and the temporal aspect have been combined to visualise layers showing edges between people in different time periods. ​ Hovering over an entity highlights it's neighbors in the current layer, and all others being displayed.