tla / stemmaweb Goto Github PK

It would be good to have a larger window for working with the stemma (@kterzopoulos)

There should be a way to export a stemma as PDF, JPEG, etc. (@kterzopoulos)

When you try to check the progress of a stemweb algorithm, nothing happens until the request returns, and then it's an ugly alert box. This should be fixed.

When a tradition's change is named, the directory is not currently updated until page reload. This should be fixed.

Users should be able to download their own traditions in GraphML format, maybe also TEI format. Maybe also public traditions.

When a merge suggestion is confirmed (clicking the green button), the server should be asked not to send any additional merge suggestions just yet. In future we probably want to handle additional suggestions more gracefully.

The compress_readings method is failing when it shouldn't be. This is because of a naive means of assembling the original text in the sanity checking code.

At the moment it produces a 'No tradition with ID help' page.

On the servers running via Apache, an attempt to run Pars is sent to Stemweb, which returns an error.

It is annoyingly common to forget to clear the annotation field when the next different relationship is made. The annotation text should just be automatically cleared whenever the relationship type dropdown value changes.

'Hypothetical witness' and 'extant witness with lacuna' are both greyed out/white right now. Provide other color for lacuna.

Depends on tla/stemmatology#17.

Need a client listener for use of Stemweb - result calculations will be sent back asynchronously.

At the moment a Moose typing error gets thrown if a relationship gets made in the UI without setting a significance value. This shouldn't happen.

The yes/no follow-on merge icons that appear on subsequent readings after a reading merge don't appear in production, because the proxy conversion isn't invoked on absolute paths. Fix this.

Deleting a global relationship currently deletes all instances. Make this optional.

At the moment, correcting collations by flattening identical distinct nodes is a server-side hack. This should be client-side functionality.

This is the main issue for commits associated with implementing Stemweb integration on the client side.

This is caused by the JS client side handing out ids: don't, new ideas are in the ajax data.

There is currently no good way to make a relationship between two readings that are very far apart in the graph. It might be nice to have a 'shortcut box' where the user can specify the two readings by ID, and the relationship to be made.

When the stemma editor is used to add the first stemma to a tradition, the 'Edit this stemma' button does not appear until the page is reloaded. Fix this.

If the auth cookie expires while the relationship mapper is in use, the permissions error (which is not JSON) is uncaught and nothing is shown to the user. Fix this.

Likely-coincidentally-arising readings should be marked explicitly, except maybe in the case of spelling variation.

Horizontal scrolling of large graphs is tedious; a "quicksearch" function would be helpful whereby the view centers on the next node matching a search term.

The user should have the choice of whether e.g. spelling/orthographic variation gets counted as variation or not, when generating phylogenetic trees.

It's not clear for new users what colors in the stexaminer mean what, there's no color legend is there?

When a user logs into the index page on IE9, the text directory doesn't refresh - not even if the whole page is reloaded. Caching issue?

The stemma edit dialogue is not recording changes in stemma identifier, and is not displaying the stemma after edit.

It should be possible to download the tradition in e.g. spreadsheet collation format, TEI parallel segmentation, SVG with or without relationships marked, etc. Proper nested parallel-seg is difficult, and double-endpoint-attachment is only feasible if we choose an arbitrary "base" text (majority maybe?) but naive parallel-seg should be straightforward.

There should be a relatively simple way, when a very long edge (i.e. lacuna) is encountered in the graph, to fast-forward to the other end of that edge. Also, there should be a way to instantly see the witness that corresponds to the edge.

There should be some quick visual indication (gold plating? Halo?) of when a relationship link is marked as significant.

We should be able to export the current view of the variant graph (or a subset thereof), complete with relationship links, as an SVG image.

Parsimony should also be an option for creating a stemma tree in the interface. It isn't provided by Stemweb, but we can do it ourselves with phylip...