Skip to content

Commit 3709ff4

Browse files
committed
Added blogs on 'Lessons learned' and 'Choosing image viewer'
1 parent 72bcc46 commit 3709ff4

File tree

4 files changed

+79
-0
lines changed

4 files changed

+79
-0
lines changed

_posts/2024-09-19-lessons-learned.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
layout: post
3+
read_time: true
4+
show_date: true
5+
title: IIIF and Omeka S - Lessons Learned
6+
description: Lessons learned during Maastricht University Library's implementation of IIIF in Omeka S
7+
date: 2024-09-19
8+
img: posts/lessons-learned-web.jpg
9+
tags: [ omeka s, iiif ]
10+
author: Maryam Mazaheri
11+
---
12+
13+
### 1. Install and switch to 'vips' from ImageMagick for faster image processing in Omeka S.
14+
Read more on: [Power up! Optimize IIIF user experience](https://maastrichtu-library.github.io/tech-talk/optimize-iiif-performance.html)
15+
16+
### 2. Use 'Tiled tiff' as the tiling method to ensure correct image display.
17+
Read more on: [Power up! Optimize IIIF user experience](https://maastrichtu-library.github.io/tech-talk/optimize-iiif-performance.html)
18+
19+
### 3. Prefer JPEG quality 80 as the source image type for the best balance of performance, disk space usage, and viewing quality.
20+
Avoid JPEG 2000 and uncompressed TIFF due to performance issues and high disk space consumption.
21+
22+
Read more on: [Power up! Optimize IIIF user experience](https://maastrichtu-library.github.io/tech-talk/optimize-iiif-performance.html)
23+
24+
### 4. Avoid relying on client-side annotations in the Mirador viewer due to their non-persistent nature and lack of contribution or curation workflows in Mirador.
25+
Instead, we recommend exploring alternative annotation systems like Madoc.
26+
27+
Read more on: [Choosing an IIIF-Compliant Image Viewer: Mirador vs. Universal Viewer](https://maastrichtu-library.github.io/tech-talk/choosing-iiif-image-viewer.html)
28+
29+
### 5. Manually adjusting visual settings like brightness and contrast on each page in the viewer is inefficient.
30+
Implementing global settings within the viewer enhances user efficiency. This feature is work in progress.
31+
32+
### 6. Use smaller batch sizes when adding bulk imports of large datasets into Omeka S to improve processing speed and reduce system slowdowns.
33+
**Regularly monitoring logs** helps detect any import issues early and ensures data integrity.
34+
35+
### 7. Batching large uploads, monitoring system resources, and testing under real-world conditions are essential to manage performance with multiple tasks and concurrent users.
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
layout: post
3+
read_time: true
4+
show_date: true
5+
title: Choosing an IIIF-Compliant Image Viewer - Mirador vs. Universal Viewer
6+
description: TODO
7+
date: 2024-09-26
8+
img: posts/choosing-iiif-viewer-web.jpg
9+
tags: [ omeka s, iiif ]
10+
author: Maryam Mazaheri
11+
---
12+
13+
## Introduction
14+
15+
When integrating IIIF capabilities into our Omeka S environment, we needed to choose the right viewer to ensure optimal
16+
user experience for accessing digital collections. After extensive testing of the available options, we selected
17+
**Mirador** over **Universal Viewer** for a number of compelling reasons:
18+
19+
### 1. Faster Image Loading
20+
21+
Mirador outperformed Universa Viewer in loading high-resolution images, providing a smoother user experience.
22+
23+
### 2. Modern Interface
24+
25+
Its clean, modern design offers easy navigation and a visually engaging way to explore digital collections.
26+
27+
### 3. Advanced Features
28+
29+
Mirador supports useful tools like annotations, **OCR overlays**, and image adjustments (brightness, contrast),
30+
enhancing research capabilities.
31+
32+
## Mirador Technical Considerations
33+
34+
Mirador allows users to add annotations directly within the viewer, but these are stored locally and can be lost if
35+
cookies are deleted. Consequently, we have found Mirador's annotation functionality too limited for our
36+
needs. Client-side annotations are not persistent, and there is no established contribution or curation workflow. We
37+
recommend exploring alternative systems for annotation, such as [**Madoc**](https://docs.madoc.io/), which appear more
38+
promising in this regard.
39+
40+
## Conclusion
41+
42+
For a project that depends heavily on user interaction and the flexibility to tailor the viewer to specific use cases,
43+
Mirador is the clear choice. Its customization capabilities make it particularly suited for projects requiring advanced
44+
image handling and specific interaction functionalities.
124 KB
Loading
124 KB
Loading

0 commit comments

Comments
 (0)