IIIF/CTS line level alignments

[gregorycrane]

I just realized that we have implemented links from lines of Homer to regions of interest in the IIIF image.

https://beyond-translation.perseus.org/reader/urn:cts:greekLit:tlg0012.tlg001.msA-folios:12r.1.1?mode=folio

The problem is (1) that the region of interest is too small to read and I can't expand it and (2) that I think we may be pulling up the wrong region (are the coordinates different in the JHU version?)

[jacobwegner]

@gregorycrane: It looks like ROI, but is actually just a side effect of how the image is being rendered (the height matches the text on the left).

If you look at the two passages below, the image is basically the same:

https://beyond-translation.perseus.org/reader/urn:cts:greekLit:tlg0012.tlg001.msA-folios:12r.1.1-12r.1.12?mode=folio https://beyond-translation.perseus.org/reader/urn:cts:greekLit:tlg0012.tlg001.msA-folios:12r.1.13-12r.1.25?mode=folio

The intended use case of the "Folio Images" display mode was so that you could view a folio at a time (or a range of them):

https://beyond-translation.perseus.org/reader/urn:cts:greekLit:tlg0012.tlg001.msA-folios:12r-12v?mode=folio

24r shows the switch in lines from Book 1 to Book 2:

https://beyond-translation.perseus.org/reader/urn:cts:greekLit:tlg0012.tlg001.msA-folios:24r?mode=folio

[jacobwegner]

@gregorycrane: I should mention that we certainly could look into making better use of the ROI data, just wasn't something we were concerned with initially.

[jacobwegner]

@pletcher has started on this; I've just merged his change into the backend that will allow us to access the ROI via the GraphQL API:

https://github.com/scaife-viewer/backend/pull/52

[jacobwegner]

With regards to the difference between 12v / 12r references and the canonical 1.1, 1.26 references, there are several things that we can approach between now and March 15th:

Table of Contents Widget

http://localhost:8080/explore-homer/urn:cts:greekLit:tlg0012.tlg001.msA-folios:12r.1.1-12r.1.25?toc=urn%3Acite%3Ascaife-viewer%3Atoc.iliad-folio-ref-1&mode=folio

This would need some additional styling / refining, but would be adaptable to other texts.

Per-text hooks for passage healing

We already have a "passage healing" functionality in place. We can add a hook so that a 1.20-1.25 reference would be resolved:

http://localhost:8080/explore-homer/urn:cts:greekLit:tlg0012.tlg001.msA-folios:12r.1.1-12r.1.25

Integrate additional folio to verse mappings into the folio images display mode

This would work similar to the passage reference or TOC functionality, but be done within the folio image mode

Alternate chunking

This is the best, but long term solution. This would allow us to retrieve a range of book / lines chunked by the folios.

[jacobwegner]

@gregorycrane: The table of contents and passage healing functionality is available for preview at:

https://beyond-transl-pr-110.herokuapp.com/reader/urn:cts:greekLit:tlg0012.tlg001.msA-folios:42v?toc=urn%3Acite%3Ascaife-viewer%3Atoc.iliad-folio-ref-10&mode=folio

The ↵ entry will go up a level to view all of the books:

The passage reference widget will convert book / line to folio: