path target data missing from IIIF manifest export

i noticed that when exporting from “Presentation API v3 Manifest” option, path annotations are missing a target value (e.g. some kind of line SVG line series). just flagging in case this isn’t known!

Hello, how do you add more than one map to the same room - in other words, how do I create a collection of maps that users can annotate that are part of the same room? The problem I have at present is that everytime I upload a IIIF Manifest, I end up creating a separate room.

"Unable to open [object Object]:..." error

I was hoping to try out a few Library of Congress maps for a class this week, but I keep getting this error! I suspect this is the same error as a bug reported for Courtauld Institute images? Example 1 - https://www.loc.gov/item/2012593214/ Manifest: https://www.loc.gov/item/2012593214/manifest.json Example 2 - https://www.loc.gov/item/2021589948/ Manifest: https://www.loc.gov/item/2021589948/manifest.json However, this one works: https://www.loc.gov/item/99446220/ Any thoughts?

Trouble creating an account via GitHub / other options for auth?

First let me say, this tool is fantastic, and we’ve had a lot of success using it at our institution already! We’re interested in subscribing, but Google isn’t a great fit for a shared account at our institution. GitHub would work, but I'm getting a "Page not found" issue when I try to create an account for Liiive via GitHub. I wondered: Are there known issues with creating Liiive accounts via GitHub? Separately, do you have plans for adding other authentication options, such as an arbitrary email address? Thanks!

Error loading mages from The Courtauld Gallery

The supplied link seems to pass the validator as it gets a tick and retrieve the title of the work, but I then get an error saying ‘Unable to open [object Object]: Error loading image. Example of image, but I have tried a couple and get the same error. Thanks! https://gallerycollections.courtauld.ac.uk/object-p-1932-sc-176

Issues with manifests that are annotated with Liiive more than once

When a manifest is annotated in Liiive, then that annotated version of the manifest is opened in Liiive and annotated again (multiple times), only the annotations from the previous annotation session are visible in the Liiive room. Also, when a manifest that has been annotated with Liiive more than once is viewed in another viewer (e.g. Mirador), only the annotations from the most recent Liiive session are visible, despite the old ones still appearing in the manifest (perhaps the json for the old annotations is malformed somehow?). Here is an example of a manifest that has been annotated in Liiive multiple (3 or 4) times: https://digbmc.github.io/pta-manifests/punc/punc-00039/manifest.json. There are four annotations in the manifest, but only one (added in the latest Liiive session) is visible in IIIF viewers.

Issue: edits don't get stored

When I try to edit an annotation (in my permanent room) the annotation reverts back to the original after save.

Feature request: annotation list

While adding annotations to an image, it is hard to have an overview of all annotations made. I’m noticing I’m openening the liiive.now manifest in Theseus to get a list of annotations. Would be nice to have a button to show this list in the liiive.now editor,

Not being able to revise/delete annotations

I was wondering if there’re any plans for giving editing (especially deleting) rights to the person who created a particular ‘room’ for contributed annotations. I am interested in using this tool in classes and workshops but it’ll be difficult to streamline annotations and fix basic mistakes if the owner of the project doesn’t have editing rights. Thanks!

Could not fetch the manifest

Hi Rainer, This looks amazing. I tried to use several of our manifests, but they each give the ‘could not fetch manifest’ warning. I tried to understand the information that is provided additionally, but this is not my cup of tea, I’m afraid. Do you think there is something wrong with the way we present our IIIF uri’s, I’m sure these two resource are not restricted. https://access.iisg.amsterdam/universalviewer/#?manifest=https://access.iisg.amsterdam/iiif/presentation/ARCH03497.8/manifest https://access.iisg.amsterdam/universalviewer/#?manifest=https://hdl.handle.net/10622/ARCH00448.4?locatt=view:manifest

Share via Liiive

Hello, very cool and useful app you have created! It would be great if one coud add Liiive share button to IIIF viewer so you could share your image via one click without copy/pasteing the manifest. I guess it would require just accepting the parameter for manifest from URL. For example: https://liiive.now/?share=https://your.iiiif.manifest Quick mockup with our project’s website: All the best Hembo

Invalid Manifest

FYI, I receive the “Invalid Manifest or unsupported type” message from this v3 manifest: https://collections.library.yale.edu/manifests/15238597 It passes the validator.

Invalid exported manifest (v2+v3)

I made some annotations on https://www.goudatijdmachine.nl/omeka/iiif/2/13/manifest but when I export these as manifest they seem to be invalid. The v2 version https://www.goudatijdmachine.nl/omeka/files/iiif/manifest_liiive_v2.json doesn’t show the image (in theseusviewer.org) and no annotations. The v3 version https://www.goudatijdmachine.nl/omeka/files/iiif/manifest_liiive_v3.json doens’t show the image but does show the presence of annotations (with invalid annotation target).