dracor-org / ezlinavis

Easy Linavis (Simple Network Visualisation for Literary Texts)

ezlinavis

Easy Linavis (Simple Network Visualisation for Literary Texts)

https://ezlinavis.dracor.org

How to Cite

Frank Fischer, Carsten Milling: Easy Linavis (Simple Network Visualisation for Literary Texts). In: HDH2017: "Sociedades, políticas, saberes". 18–20 October 2017. Málaga. Libro de resúmenes, pp. 173–176. (doi:10.5281/zenodo.10478399)

Development

This project was bootstrapped with Create React App.

Synopsis

git clone https://github.com/dracor-org/ezlinavis.git
cd ezlinavis
yarn install
yarn test
yarn start

Available Scripts

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:8000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

ezlinavis's Issues

publish short info text

along those lines:

"Easy Linavis (ezlinavis) generates CSV files with network data from simple segmentations of dramatic texts. In the left column, you can list segments (chapters, acts, scenes, etc.) and characters appearing or speaking in a given segment. Segments are indicated with a hashtag and they can be hierarchical (e.g., # First Act / ## First Scene / ### …). This will automatically generate a CSV file with node-node relations (source, type, target, weight) in the column in the centre. Data changes as you type: as soon as you change something in the first column, the mid-column changes accordingly. The "type" column in the CSV file is always "undirected" here, but we inserted it so you can directly work with the CSV files in Gephi. The network graph in the right column is also generated live, using a spring-embedded layout, just to give you a first impression of what your network data looks like. To make it easier to understand how ezlinavis works, we provide some example files which can be accessed via the drop-down menu in the first column.

ezlinavis was developed by Carsten Milling and Frank Fischer, making use of the React and Sigma JS libraries. It is mainly meant for didactic purposes, although it could also be suitable to process simply-structured research data. We are mainly resorting to it in our workshops on network analysis of literary texts."

Provide some example files

More lenient segmentation hierarchy

Characters occurring more than once in a scene should be counted only once

Migrate to reactstrap and bootstrap@4

In order to update our dependencies and bring ezlinavis more in line with the dracor-frontend we should migrate from react-bootstrap to reactstrap which depends on bootstrap 4.

Allow comments before first leading hashtag

Deploy on dlina.github.io/ezlinavis …

… via gh-pages.

Switch to create-react-app setup

create-react-app provides a more modern development environment and ezlinavis (now hosted on its own domain) could profit from the service worker setup that comes with it.

Nearley parser breaks with CRLF line endings

When the text input uses CRLF (\r\n) line endings the parser takes very long (with just a few lines) or does not return at all. As a workaround example files should always use linefeeds (\n) only. For a proper solution the grammar should be modified to prevent the parser from stalling.

Migrate to Vite

See dracor-org/dracor-frontend#275.

Add weight to graphs

Value in 4th column of CSV should be used to put weight on edges (make lines thicker, according to value).

Ignore trailing spaces and improve delimiter

1. At the moment, having "Name" and "Name " (the latter with trailing whitespace) in two lines yield two different nodes. This has been reported as confusing by some, so could we ignore trailing spaces (and only them) when extracting node labels?
2. For the delimiter, we need a hashtag followed by a whitespace at the moment. Wouldn't it be enough to have just the hashtag without the whitespace? This would shorten the explanation how to delimit co-occurrences.

Graph rendering in Firefox

I see two problems when starting ezlinavis in Firefox:

1. The graph seems to be placed in the vertical centre of the CSV column. If this list is long, the graph doesn't show before scrolling down (maybe it's enough to top-align the graph?).
2. The graph-layout algorithm seems to work differently in Firefox, if you compare the graphs for "Faust, pt. 1" in Firefox and Chrome. The latter, although always a bit differently of course, usually shows nice clusters around Faust. In Firefox, the graph looks like a haystack. Why could the two browsers show different results?