Address existing back log of issues before or while addressing any potential design changes.

[kaladay]

We need to make sense of this back log of issues and determine if they apply to any design changes, determine if they need to be closed, or determine if they need to be left alone.

Many of these lack details and so I am noting everything here with my particular observations and thoughts.

This breaks things apart based on what is or is not potentially relevant to the Cantaloupe issues:

1. Fails to Return Images for Certain Items in Fedora cantaloupe#1
2. Optimize Processor Strategy, Caching, and Tuning cantaloupe#2
3. Improve Performance for Simultaneous Users and Average Response Time cantaloupe#3

Issues that May be Related or of Importance Relating to Research.

• Fedora resources with %20(1) in filename fail to generate presentation manifests #139
  This shows potential at causing problems like those mentioned in (1) above.
  This should be considered and solvable in any re-designs or major design changes.

• Scheduled task to test image server cache and report performance #109
  This is being done via the Cantaloup investigation issues for (2) and (3) above.
  This probably can be closed once issues (2) and (3) are closed.

• Collection manifest from fedora collection container not applying correct labels #91
  This may relate to (1) as the associated image does not even load.

• If manifest is required to be generated respond accordingly #70
  This would be helpful but the better approach would be to not need this by fixing the performance problems.
  This should ideally not be needed if the performance is improved with appropriate design changes.

• Fedora IIIF presentation should translate container of resources to sequence #69
  This seems like it would matter when regarding performance.

• Internal cache of manifest being generated to prevent duplicate manifest generating at same time #66
  This should ideally not be needed if the performance is improved with appropriate design changes.

• /fedora/image/ can't create manifest  #54
  This seems important and it shows that there is a resolver delegate.
  We need to investigate the state of our resolver deligate and any potential problems.

Issues that May be Related or of Importance Relating to Potential Re-design.

• IIIF Generator: Refactor manifest generation to provide better extensibility #102
  This is something to consider should any re-design happen.

• IIIF Generator: Add Manifest Identifier Resolver #96
  This may or may not be needed and might go away following any re-design.

• Add configuration for thumbnail size #88
  This shows integration concerns such as with SAGE.
  This is something to think about during any re-design.

• Manifest identifier strategy avoid use of query params #71
  This may or may not be needed and might go away following any re-design.

• Additional query parameter to update presentation manifests within a collection on request #53
  This is something to think about for any re-design especially when it conflicts with Manifest identifier strategy avoid use of query params #71 .

• switch dependency to iiif-apis #49
  What is this and how is it different from what we already do?
  This seems highly relevant to any re-design.
  The referenced iiif-apis project appears to also be actively maintained.

• documentation for use with Spotlight and Mirador #19
  Documentation is of courses needed but this also shows that Spotlight and Mirador need to be payed attention to on any design changes.

• granular manifests with using dereferencable ids, query param to expand manifest #7
  This is something to think about for any re-design especially when it conflicts with Manifest identifier strategy avoid use of query params #71 .

• iiif structures generation #6
  This is of important note as if the re-design is to simplify things and remove not needed functionality then this might not be do-able.
  "... need in the National Library of Wales in order to generate the IIIF manifests for Works that have Chapters."
  But this request is from 2018 and so there may no longer a need for this by that interested party.

Not Sure of or No Opinion On

• Replace use of RDFNode toString #136
• IIIF Generator: Rename to iiif-generator #105
• Message topic property should not be named after the application which produces the messages #86
• increase test coverage #60
• test authorization for resource create and delete #46
• code comments #20
• DSpace REST implementation #17
• manifest license #5