Text-level diagnostics needed

[martindholmes]

This is a list of nice-to-have features for a text-level diagnostic process, gathered from editors:

Please add any diagnostic requests here so we can develop feature requests for our developer.

Working Diagnostics

• Can we check the accuracy of quotations in the critical paratexts (by checking against their own modern texts)?
• Flag links to non-published documents
• Number of words spoken by each character
• Number of speeches by each character
• Characters who speak with the longest words/shortest words
• Number of words in text
• Number of speeches in text
• Something that could show when speakers are onstage? We could see who appears on stage together? --> similar to B G-H's – to do this, we'll have to add a @who attribute to entrances and exits -- ask LE for tips on how to encode this.

Text Analysis

From B G-H:

• Generate cue-scripts by character
• Generate dialogue by character (minus cues)
• Generate a table of entrances and exits by scene (i.e., the building blocks of a doubling chart) -- similar to LE's request to see who appears on stage together.

[martindholmes]

Some work has already been completed in code/diagnostics/diagnostics_text.xsl.

[martindholmes]

I've added the current text-level diagnostics processing as the default transformation for LEMDO XML files.

[martindholmes]

In rev 16313, I added a listing of entrances and exits.

[martindholmes]

In rev 17367, I added proper handling for milestone act and scene divisions for entrances and exits.

[martindholmes]

@JanelleJenstad @LEMDO-PM I need to get your input on this ticket at this stage. Some of the remaining items (such as tables of entrances and exits) cannot be done with additional encoding which doesn't yet exist (such as stage/@who), while others such as cue scripts are going to be massive -- the diagnostics would be longer than the play itself -- so I think they should be a separate feature request handled in a different process. Links to non-published documents will not typically appear in play texts, they'll be in ancillary files, so this suggests that this diagnostic is not just for play texts but for any files; is that right? Would that be better handled by a diagnostic across the whole collection?