Terms of Use Overlay Improvements

[crhallberg]

• Default to requiredStatement
• Make license a link when used
• Break words instead of hiding longer URLs
• Give more flexibility of overlay width

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
universalviewer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 11, 2025 6:48pm

[demiankatz]

Thanks, @crhallberg. I like how this looks, but we might need a IIIF expert to weigh in on whether this solution is entirely acceptable. I think in many cases, the requiredStatement is going to include license information... but I think it's at least theoretically possible that the license information might be independent of the required statement. Not sure what the most appropriate behavior would be there, or how to decide what to do.

One possible approach: check if the license URI is part of the required statement. If so, use the current behavior; if not, add a "License: [linked URI]" to the end.

(Not sure if that's the best approach -- just brainstorming!)

[LanieOkorodudu]

Thanks, @crhallberg. I like how this looks, but we might need a IIIF expert to weigh in on whether this solution is entirely acceptable. I think in many cases, the requiredStatement is going to include license information... but I think it's at least theoretically possible that the license information might be independent of the required statement. Not sure what the most appropriate behavior would be there, or how to decide what to do.

One possible approach: check if the license URI is part of the required statement. If so, use the current behavior; if not, add a "License: [linked URI]" to the end.

(Not sure if that's the best approach -- just brainstorming!)

Yeah, I agree, it would be great to get someone with more IIIF experience to weigh in. Maybe we could share this PR in a relevant community or channel to get some feedback. I’m not an expert in this area either, so some extra eyes would definitely help.