search

Islandora / documentation

Contains islandora's documentation and main issue queue.
MIT License
104 stars 71 forks source link

Media EVA not rendering all media #1242

Open mjordan opened 5 years ago

mjordan commented 5 years ago

I'm playing with EVA settings to see if I can get all media with a specific tag (in this case, "Service file") to show up within the node display. In other words, the user should see not just one image, but all images tagged as "Service file".

I have two "Service files" on an Image node. When I change the pager in the Media EVA View -> Service File display from the default " Display a specified number of items" > 1 to "Display all items", the View works as expected in the Preview, i.e., I pop in the node ID that has the two service files, and they both show up in the Preview as expected. But back at my normal node display, only the first service file is showing up.

I tried clearing the cache with no luck. Does anyone know why the EVA works as expected ("expected" here meaning I expect to see both of my service files in the node display similar to how they show up in the View Preview). I will also add that when I add a Footer to this diplay, it shows up as expected in the Preview but not in the node display.

Is this how the EVA should work, or am I misunderstanding how they work?

mjordan commented 5 years ago

Over at https://github.com/Islandora-CLAW/openseadragon/pull/16 @dannylamb suggested I try making multi-valued file field on a media. I set the cardinality of field_media_image on Image media to 2, and it let me upload two images:

multiple1

But the technical metadata (width, size, etc.) only applies to one of the images. Likewise, in the Media view for the parent node, the derivatives for only one of the images is showing up:

multiple2

So I'm not sure this approach meets my need here.

But, I need to ask, am I the only person who would want to have multiple files (or media of a given Media use value) associated with a parent node? Compound objects are not out of the question, but for the following situations (which we discussed in a Tech Call), I think they are overkill:

seth-shaw-unlv commented 5 years ago

I don't know that they are overkill, but the UI is certainly awkward for them. We are using compound objects for things like oral histories and postcard recto/verso; but we are also bulk loading everything and avoiding the web UI at the moment anyway.

It seems like the Paragraphs module would be some useful inspiration for making "lightweight compound objects". I know @alxp has a session next week that mentions Paragraphs which could prove very interesting.