Wisski Mirador seems not respecting the window settings

Created on 3 April 2024, 3 months ago
Updated 25 April 2024, 2 months ago

I run the example docker successfully , on the page
/mirador-viewer, it always shows as the layout 1*2:

No matter how I change the window settings in the Views as the screenshot as below:

🐛 Bug report
Status

Active

Version

3.0

Component

User interface

Created by

🇨🇳China fishfree

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @fishfree
  • 🇩🇪Germany Knurg

    Hi :)

    I'm not sure if that really is a WissKI issue. Typically we just provide the options to the mirador viewer and we had problems with mirador itself in the past. I guess you would have to have a deeper look in the console, see if the parameter is really provided to mirador and if so you have to ask over at https://github.com/ProjectMirador/mirador - otherwise I'll have to fix that :)

    Cheers!

  • 🇨🇳China fishfree

    @Knurg There is no error in my browser console. When I export Mirador workspace settings, I find the settings are the exactly as I set in the Views window_settings textbox.
    When I changed the Views pager settings as Use pager:Display a specified number of items | 2 items, it showed as below:

    What I want is: Views pager: Display multiple items, But Mirador still shows only one image with last/next pager icon buttons.

  • 🇩🇪Germany Knurg

    Hm,

    I'm unsure if I can help there. I know that between Mirador 3 and Mirador 2 the settings changed. Can you check if the setting array is correct for your version of mirador?

    Cheers :)

  • 🇨🇳China fishfree

    Finnaly, I noticed it was because WissKI generated one manifest for every object on page /objects. I think it's better to generate one manifest for all objects in one collection.

  • 🇩🇪Germany Knurg

    You can do that by building your own view with all the objects in it.
    But it will be a long time loading if there are many objects (our
    object catalogue e.g. has ~172.000 objects with up to 1000 images per
    object.

    Cheers :)

  • 🇨🇳China fishfree

    @Knurg The key problem is that WissKI generated one manifest per object. If we show multiple objects in a Mirador viewer view, it would show up with equivalent numbers of windows. You can have a try :-)

  • 🇩🇪Germany Knurg

    So you want all objects in one single window? One manifest for all objects?

  • 🇨🇳China fishfree

    @Knurg Yes, I want only one manifest for all objects objects exposed by a views view. Of course, it's best we can configure this option.

  • 🇩🇪Germany Knurg

    I think it is configurable, you just have to build a form the collection and the collection has to have a field to all the associated images of the collection via the objects ( collection -> objects -> images of the objects). Then the manifest of the collection has everything in it :)

    Cheers!

  • 🇨🇳China fishfree

    @Knurg Thank you! What do you mean by "form" here? The pathbuilder form or an WissKI entity entity-reference field?

  • 🇩🇪Germany Knurg

    In Pathbuilder-logic: a main group talking about the collection and there has to be a field that references all the objects of the collection and all the images from these.

    Hope this helps :)

  • 🇨🇳China fishfree

    @Knurg Thanks! The Mirador View seems hardcoded reading the img_image_for_mirador path field as images source. As your suggestion, do we also need add this path in the new pathbuilder? If do, it's not elegant, for we need to maintain content twice: once from the WissKI object group, once from the WissKI collection path.

  • 🇩🇪Germany Knurg

    It is not very hardcoded, it looks in the pathbuilder for image paths for this particular group (in this case collection) and fetches things from that. How should this be more dynamic than auto-selected based on the available fields? :)

    You don't need to maintain content twice, it is a semantic database. However you have to tell the system what you exactly want and what you want is: You want to have a collection and show all the images from this collection :)

    And this is only possible by creating a collection semantically and have image paths there :)

    Cheers

  • 🇨🇳China fishfree

    @Knurg Thanks!
    I tried to create a new pathbuilder as the screenshot below:

    And generated the correspondent bundle and fields.
    Then I create an entity instance of this new pathbuilder bundle, and cloned a view of mirador_viewer and changed the filter to "Wisski Entity: Bundle/Group (= Collection with objects)", but no images showing up.

    The screenshot of the built-in example_pathbuilder in the docker container is as below, you can see I constructed my "collection_with_objeccts" pathbuilder with the reversed path against the built-in one.

  • 🇩🇪Germany Knurg

    Unfortunatelly I can not see the screenshots as watchdog seems to have removed them, I'm sorry :/

    Can you send them to me via chat.wiss-ki.eu? :D

  • 🇨🇳China fishfree

    @Knurg Thanks! I don't know why I cannot upload images in comments. I sent them to you via chat.wiss-ki.eu? :D

Production build 0.69.0 2024