Social Networks (Romeo and Juliet)

Purpose

To represent and explore a range of relationships and interactions between characters in the Shakespeare play “Romeo and Juliet,” which takes place in a 6-day timeline. This project represents these relationships and interactions using Prospect’s Qualified Relationship feature set.  View this exhibit on our server HERE.

Download zip file: Archive-Romeo7Juliet.

Data Design Details

The information in this data set is based on the timeline of events, across 6 days, described on this webpage. The events are arbitrarily set in the year 1450.

Project data is stored in Records described by two Templates:

  • person, which describes each of the characters in the play
  • relationship, which describes many (but certainly not all) of the relationships and interactions between characters in the play

Person

The person Template is comprised of the following Attributes:

  • name: A Text Attribute for the character’s name.
  • gender: A Vocabulary Attribute for the character’s sex.
  • role: A Vocabulary Attribute specifying the character’s social role (Apothecary, Aristocrat, Priest or Servant)
  • house: A Vocabulary Attribute specifying the noble house to which the character belongs, if any (Capulet, Montague, Verona, none, unknown)
  • when: A Dates Attribute giving the date range of the character’s lifetime only during the plays’s six days. A Dates Attribute is necessary for a Record to be viewable on the TIme Rings visualization.

Relationship

The relationship Template is comprised of the following Attributes:

  • name: A Text Attribute describing the relationship.
  • relation_type: A Vocabulary Attribute listing the different kinds of relationships and interactions modeled in this data (Amity, Familial, Romance, Messages, Service, Violence).
  • r1: A Text Attribute providing the role for the first character in the relationship.
  • r2: A Text Attribute providing the role for the second character in the relationship.
  • e1: A Pointer Attribute pointing to the Record for the first character in the relationship.
  • e2: A Pointer Attribute pointing to the Record for the second character in the relationship.
  • act: A Vocabulary Attribute providing all of the acts of the play (in which relationships appear).
  • when: A Dates Attribute giving the date (or date range) for the relationship.
  • where1: A Lat-Lon coordinate Attribute giving a location for the first character in the relationship. This is an entirely arbitrary location (near Rome) for the purpose of demonstrating the QR-Map visualization.
  • where2: A Lat-Lon coordinate Attribute giving a location for the second character in the relationship. This is an entirely arbitrary location (near Rome) for the purpose of demonstrating the QR-Map visualization.