Image Streams Don't Resolve To Be Cached
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start at the getUncachedImageStream entry point and read the discussion in #703 to understand how unresolved image URLs currently produce dimensions. Trace how those dimensions reach canvases and manifests, then verify that unresolved images are not recorded as 1,1 and that resolved dimensions can update the cached folio values one folio at a time.
Written by the indexing model from the issue text.
Description
When getUncachedImageStream cannot resolve the URL, it will use Image dimensions 1, 1 instead of being omitted or using/returning 0, 0. This means the Canvases with these images are all 1000, 1000 and the images themselves are all 1, 1 in the Manifests, which will absolutely wreck all attempts at interoperability. However, somehow the TPEN interface manages because after some time it does resolve the image.
Our best idea, already referenced in #703, is to let the interface detect this scenario and after it loads the images and has dimensions to update the cached dimensions for the folio (per folio, one at a time, as the interface resolves the image so the user will not experience any extra delay).
- Dominant language
- Java
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CenterForDigitalHumanities/TPEN28
-
bug IIIF interoperability
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
interoperability
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
interoperability
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
servicesOpeninteroperability
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in CenterForDigitalHumanities/TPEN28
Similar issues
-
pdfium-drift
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Stirling-Tools/JPDFium#188 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openremote/openremote#3487 · 1 comment ·
-
Type/Bug U2
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
wso2/product-is#28675 ·
Maintainers usually reply within 1 day
-
a:bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
erupts/erupt#460 · 1 comment ·
Maintainers usually reply within 1 day