How to display alternative thumbnails?

Asked by Siegfried Schweizer

The default thumbnail in list view is the front cover. Sebastian mentioned on September 15th that it is possible to have displayed an alternative thumbnail. How exactly do I have to setup this?

Question information

Language:
English Edit question
Status:
Solved
For:
Goobi.Presentation Edit question
Assignee:
Sebastian Meyer Edit question
Solved by:
Siegfried Schweizer
Solved:
Last query:
Last reply:
Revision history for this message
Frank-Ulrich Weber (fuw) said :
#1

Please look at this Whishlist-But
https://bugs.launchpad.net/goobi-presentation/+bug/956155

This feature is already available with Release 1.2b2 of Goobi.presentation.

The configuration can be done by editing a structure element (e.g. monograph).
(Look at the screenshot attached to the bug.)

If a structure element is marked as "Top-level Unit"
you are able to select a structure element used for the thumbnail "Get thumbnail from..."
in the search result list.

It works like this:

1. If "Get thumbnail from..." is not configured, always the first image of the "monograph" is returned as the thumbnail.

2. If "Get thumbnail from..." is configured, always the first page of the first appearance of the selected structure element (e.g. Title page) is returned as the thumbnail.

3. If there is no structure element "Title page" within the "monograph", the result is the first page of the "monograph" itself.

Be aware that after changing this you have to do the Indexing again!

Revision history for this message
Siegfried Schweizer (siegfried-schweizer) said :
#2

Do I get this correctly that if I, say, had a METS file where a "monograph" super structure element was being defined in

./mets:structMap[@TYPE="LOGICAL"]/mets:div[@TYPE="monograph"]

and a "title_page" sub structure element in

./mets:structMap[@TYPE="LOGICAL"]/mets:div[@TYPE="monograph"]/mets:div[@TYPE="title_page"]

, that then I could simply define another DLF Structure backend module in my DLF setup with an "Index name" reading "title_page", and if I then defined my other DLF Structure backend module which has an "Index name" reading "monograph" as a "Toplevel Unit", I would find the "title_page" thing inside its "Get thumbnail from..." select?

And if I subsequently reindexed, DLF would then automagically sort out all title page thumbnail URLs and put them into the index?

Revision history for this message
Sebastian Meyer (sebastian-meyer) said :
#3

Yes, that is exactly how it should work!

Revision history for this message
Siegfried Schweizer (siegfried-schweizer) said :
#4

OK. I'm curious to see if it does for us. Reindexing is running right now.

Revision history for this message
Siegfried Schweizer (siegfried-schweizer) said :
#5

Unfortunately it doesn't. Should I file a bug now or are there any suggestions to what else could be wrong?

Revision history for this message
Sebastian Meyer (sebastian-meyer) said :
#6

Did you specify the correct fileGrp in the extension configuration (default is "THUMBS") and does this fileGrp exist in your METS files?

Maybe Henrik Lochmann has some more hints, since he made this feature. I do not use it myself, so I don't have much experience with it.

Revision history for this message
Siegfried Schweizer (siegfried-schweizer) said :
#7

Yes, fileGrp == "THUMBS" is set in the backend as well as a section

./mets:fileGrp[@USE="THUMBS"]

exists in our METS files, e.g.

http://digital.staatsbibliothek-berlin.de/dms/mets-resolver/?PPN=PPN65902456X

Revision history for this message
Henrik Lochmann (henrik-lochmann) said :
#8

Hi Siegfried,

we also experienced a problem here with the selection of substructures for thumbnail generation/indexing. It appears that currently thumbnail indexing works only for structures themselves ("Get thumbnail from..." > "self") and not for sub-structures.

Since this worked once, we are still investigating the problem. The bug could be introduced during the merge process.

I would very much appreciate if you could file a bug on that.

Thank you!

Best regards,
Henrik

Revision history for this message
Sebastian Meyer (sebastian-meyer) said :
#9

There is a bugfix for this issue:
https://bugs.launchpad.net/goobi-presentation/+bug/1089332

Could you please verify that it solves the problem?

Revision history for this message
Siegfried Schweizer (siegfried-schweizer) said :
#10

Sorry, but what fix?

Revision history for this message
Sebastian Meyer (sebastian-meyer) said :
#11

Sorry, it was merged into the trunk as revision 156:

http://bazaar.launchpad.net/~slub.team/goobi-presentation/trunk/revision/156

Revision history for this message
Siegfried Schweizer (siegfried-schweizer) said :
#12

Yes, that solves the problem. BTW, what revision should I use as of now? Is it safe to use the newest one or should I wait for the next release?

Revision history for this message
Sebastian Meyer (sebastian-meyer) said :
#13

The formal answer is: You should always use the latest stable release for production -which still is version 1.1.3.

BUT: The latest trunk revision is currently running on my development system without any known issues, but it isn't thoroughly tested, yet.
Our productive system is currently running revision 157 without any problems, but we do not use all the features there, so maybe there are still issues with some features we do not use.

I would appreciate if you could test the latest revision of the trunk and give me some feedback.

Revision history for this message
Siegfried Schweizer (siegfried-schweizer) said :
#14

My focus is upon going productive asap, so I'll upgrade to r157 now. Unfortunately I do have no time at all left for any further evaluation work now.