Ancestors

Written by Rainer Simon on 2024-12-23 at 12:34

Today I'm launching #liiive: a new IIIF viewer that puts real-time collaboration front and center. View, annotate, and discuss together as if you're in the same room. Just paste a manifest URL and go! https://liiive.now 🎄 #DigitalHumanities #IIIF #DH #ArtHistory #Museums

=> More informations about this toot | More toots from aboutgeo@vis.social

Written by Hubert Mara on 2024-12-29 at 15:55

@aboutgeo That looks great. However, I have troubles with IIIFs from HeidICON e.g from a tablet the mainfest link given is: https://heidicon.ub.uni-heidelberg.de/iiif/2/1669480%3A872538 ... works only by adding "info.json" and then there is some error about "loading the TileSource" :(

=> More informations about this toot | More toots from hubertmara@mastodon.social

Written by Rainer Simon on 2024-12-29 at 19:18

@hubertmara yes - same in Universal Viewer, Theseus, and Mirador. I'll see if I can diagnose the issue when I get a chance. But it's not a problem with liiive. TBH I'm expecting a lot of these "bug reports" in the coming weeks. (Thinking about adding a direct link to Theseus/UV in my error messages, with a note "did you check if it works in other viewers" ;-)

=> More informations about this toot | More toots from aboutgeo@vis.social

Written by Rainer Simon on 2024-12-29 at 19:21

@hubertmara Ok, already found it. Well, HediCON is pointing to an HTTP (not HTTPS) URL in their manifest. That's fine in principle. But then they'd need to automatically redirect from HTTP to HTTPS which they don't.

Because an HTTP manifest will not load from an HTTPS site, they are effectively blocking outside use on their end (even though it's clearly not intentional).

=> More informations about this toot | More toots from aboutgeo@vis.social

Written by Hubert Mara on 2024-12-29 at 19:35

@aboutgeo Thanks. I had a small suspicion that it is a problem of the Heidelberg library server. Looks like IIIF isn't used to much with their system. Will report to them 🙂

=> More informations about this toot | More toots from hubertmara@mastodon.social

Written by Rainer Simon on 2024-12-29 at 19:36

@hubertmara great, thanks!

=> More informations about this toot | More toots from aboutgeo@vis.social

Written by Hubert Mara on 2025-01-07 at 09:50

@aboutgeo Got an answer from the UBibHD. The cuneiform tablets don't (yet) have IIIF manifests. The link we tried is for the images only. Maylein gave another URL for an object with manifest, which works fine:

https://heidicon.ub.uni-heidelberg.de/manifest/iiif/1075036/manifest.json ... so we requested manifests for the tablets. For your tool it might be nice to add a hint that one maybe tried a "non manifest" IIIF URL.

=> More informations about this toot | More toots from hubertmara@mastodon.social

Written by Rainer Simon on 2025-01-07 at 09:54

@hubertmara I've been thinking about adding better identification/validation functionality. (Potentially even support for just pasting a link to a JPEG.) I actually started to work on this. But it's a can of worms... basically writing my own validator that should be able to react to anything people throw at it ;-) Planned in the long run, but may take a bit.

=> More informations about this toot | More toots from aboutgeo@vis.social

Written by Hubert Mara on 2025-01-07 at 09:56

@aboutgeo I totally understand. There are already bigger and smaller cans of @gigamesh worms standing around ;)

=> More informations about this toot | More toots from hubertmara@mastodon.social

Written by Rainer Simon on 2025-01-07 at 10:01

@hubertmara @gigamesh 😃 FWIW: if you have a plain JPEG image, you could theoretically create your own IIIF manifest for it. I don't know the exact details off the top of my head. But it would be a Sequence, with a Canvas, with an Image that has a Resource, which has no Service. (Easy right? God... I wish IIIF wouldn't have to be like that all the time...) Then the Resource @id would have to point at the JPEG image directly. This scenario works in liiive, as of last week.

=> More informations about this toot | More toots from aboutgeo@vis.social

Written by Rainer Simon on 2025-01-07 at 10:02

@hubertmara @gigamesh as an example, here's a manifest which does this: https://apicollections.parismusees.paris.fr/iiif/160009707/manifest

=> More informations about this toot | More toots from aboutgeo@vis.social

Written by Hubert Mara on 2025-01-07 at 10:05

@aboutgeo @gigamesh That is interesting as well ... until using it for annotation in a lecture I wasn't aware about all these possibilities. Just used it computer science style as image URL with a fancy name :D

=> More informations about this toot | More toots from hubertmara@mastodon.social

Written by Hubert Mara on 2025-01-30 at 15:21

@aboutgeo @gigamesh new from UBib Heidelberg. They created proper IIIF manifests for the cuneiform collection https://doi.org/10.11588/heidicon.hilprecht ... now everything works like a charm :)

=> More informations about this toot | More toots from hubertmara@mastodon.social

Written by Hubert Mara on 2025-01-30 at 15:26

@aboutgeo @gigamesh What I don't understand why Excel or rather CSV export is not available?

=> More informations about this toot | More toots from hubertmara@mastodon.social

Written by Rainer Simon on 2025-01-30 at 15:29

@hubertmara @gigamesh simply because it's not done yet. (I.e. it's not a problem with data, manifest, bug etc. I just have to shift my attention back to paid work for a while, I'm afraid ;-)

=> More informations about this toot | More toots from aboutgeo@vis.social

Toot

Written by Hubert Mara on 2025-01-30 at 17:18

@aboutgeo @gigamesh Good to know that the problem is not in front of the computer ;)

=> More informations about this toot | More toots from hubertmara@mastodon.social

Descendants

Proxy Information
Original URL
gemini://mastogem.picasoft.net/thread/113918445479411597
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
342.606676 milliseconds
Gemini-to-HTML Time
3.106517 milliseconds

This content has been proxied by September (3851b).