thecdil / dramaturgy Goto Github PK

i.e. sort of like the workflow we talked about using hypothes.is

workflow:

• click button "annotate mode"
• create/edit some annotations displayed in recogito style mode
• click "download annotations" button
• js creates a CSV of annotations with id, text, text position start and end
• the CSV can be added to project annotation CSV, which is then used to generate annotations on the live public page

uses r.getAnnotations(),
transforms the objects into csv-like form,
download as file using something like filesaver.js

advantages: this gets us the sort of detailed markup annotation, with built in method to create/edit (without a database), with the data necessary to create a detailed highlight for the annotation (i.e. start/end character numbers).

disadvantage: sort of odd work around workflow? (but maybe not as odd as trying to fit detailed annotation into a csv line by line)

output different views / printable versions of script

• clean text
• diff text
• annotations only
• annotations as footnotes

network of terms, lines, annotations

export annotations of transcript page as json to re-incorporate into site
https://web.hypothes.is/

visualize where each character's lines appear in the text to give overview of appearances
(similar to OHD colored bar viz)
each unit of bar is line, highlighted if the line matches the character.

something like:

<style> 
    body { counter-reset: section; }
    #contents-container .textline::before {
        counter-increment: section;
        content: counter(section);
    }
</style> 

The count is auto generated by counting some element selector, so would need to tweak which container it is counting to get line numbers that match what we want.

advantage = when you select text, you don't get the line numbers (is this good?). might simplify markup and layout and getting auto numbered lines for display.

disadvantage = potentially doesn't correspond to line # as listed in csv. However, that might get confusing in the text display if the line numbers are off in the csv in general anyway.

in script lines spreadsheet, each line can be edited by adding updated version (or cut) to edited column.
display page has way to toggle between original and edited version.