Add app for entity visualizations
Add sample data for entity visualizations
Add url mapping, view and template for entity visualization

Added an url mapping, a view and a template for entity visualization.
Add visualization of LIWC category posemo

Added a line graph that visualizes the frequency of posemo words per
sentence for a certain character.
Next steps:
- Add other LIWC categories
- Plot measure instead of raw frequencies
- Add other characters to the graph
- Add act/scene information on x-axis
Add multiple LIWC categories to graph

Based on a new data file that specifies the frequencies of multiple
LIWC categories (of a single speaker), a new line graph is created.
The graph shows frequencies per sentence for all LIWC categories in
the data.
Next step: smoothing (the lines currently show raw frequencies and need
to be smoothed).
Add data files for visualization

Several data files for visualisation were added to the data directory.
Adjust width of graph

The graph was not wide enough to show interesting details. Increased
graph width.
Add data files for visualization

Files containing data about speaker turns instead of sentences were
added to the data directory.
Change graph for visualization of speaker turns

The graph was changed to display data about speaker turns instead of
sentences (using the new data files added in the previous commit).
Add legend to LIWC entity visualization chart

A legend was added to the chart.
Add custom tick values (hardcoded)

Added (hardcoded) custom tick values, representing act boundaries.
Add play metadata to web page with graph

Play metadata (year, author names, genres, and subgenres) has been
added to the web page displaying the entity graph.
Add models for entity visualizations

Added models for storing information about plays, characters, and
entities in the database. This information will be used for more
interactive visualizations.
The next step is to create a script (Django management command) to
extract information about entities and put it in the database.
Add files to create management commands for entity_vis

Added files that are required for Django management commands in the
entity_vis app. This was done as a preparation to add a management
command for extracting information about entities from FoLiA files.
Fix SpeakerTurn model

Removed foreign key to Titel from the SpeakerTurn model, because it
caused an error when generating the database table.
Add entity_vis models to the admin

The entity_vis models have been added to the admin for easy inspection
of the database contents.
Add __unicode__ functions to entity_vis models

Added __unicode__ functions to entity_vis models, for easy inspection
in the admin interface.
Update relation between SpeakingTurn and Entity

The relation between SpeakingTurn and Entity was a ForeingKey
relationship. This is a conceptual mistake: a SpeakingTurn can have
many Entities and many Entities can occur in a SpeakingTurn. Therefore,
the relation between SpeakingTurn and Entity was changed to a
ManyToMany relation. Because the entity score must also be saved, a new
model EntityScore was added to the entity_vis models for this relation.
Add EntityScore to admin

Added the EntityScore model to the admin for easy inspection of results.
Add management command to store EntityScores in the database

Added a management command that extracts Characters, Entities,
SpeakingTurns and EntityScores from a FoLiA XML file and add them to
the database. The information in the database is used for
visualization.
What needs to be improved: at the moment it is still possible that the
same speaking turn/entity score is added multiple times. This needs to
be avoided. Also, it might be a good idea to add a field 'class' to the
Entity model (now an Entity.name consists of <class>-<name>.