Marking a bitstream as "primary" fixes this -- unfortunately, we have 300+ 
items in the collection that have this problem.

I was hoping that we could find a "code" method to resolve this more 
quickly... unfortunately, that's looking like it may not be possible...

Alex

On Tuesday, 4 December 2018 14:06:01 UTC-5, Terry Brady wrote:
>
> I have experienced a similar issue in the past.
>
> If you mark one of the bitstreams as primary (on the item edit screen), do 
> you see more consistent results?
>
> On Tue, Dec 4, 2018 at 10:56 AM Alex Fletcher <[email protected] 
> <javascript:>> wrote:
>
>> Really delayed followup, as other priorities came up (typical).
>>
>> Comparing the two, they really come down to the src attribute.
>>
>> item-view.xsl has it presented as:
>> <xsl:value-of 
>> select="$context/mets:fileSec/mets:fileGrp[@USE='THUMBNAIL']/   
>> mets:file[@GROUPID=current()/@GROUPID]/mets:FLocat[@LOCTYPE='URL']/@xlink:href"/>
>>
>> while item-list.xsl has it as:
>> <xsl:value-of select="mets:fileGrp[@USE='THUMBNAIL']/mets:file/   
>> mets:FLocat[@LOCTYPE='URL']/@xlink:href"/>
>>
>> It looks like the major difference is in the 'mets:file" call. The 
>> question I have is -- will the item-view version work in the item-list 
>> context, or is it too specific?
>>
>> Alex
>>
>>
>>
>> On Thu, Nov 8, 2018 at 5:36 PM Fitchett, Deborah <
>> [email protected] <javascript:>> wrote:
>>
>>> I haven’t seen that particular problem but I’d check into the 
>>> item-view.xsl vs the item-list.xsl for the code that creates the thumbnail 
>>> – it sounds like the two have slightly different logic.
>>>
>>>  
>>>
>>> Deborah
>>>
>>>  
>>>
>>> *From:* [email protected] <javascript:> <
>>> [email protected] <javascript:>> *On Behalf Of *Alex Fletcher
>>> *Sent:* Thursday, 8 November 2018 2:51 AM
>>> *To:* DSpace Technical Support <[email protected] <javascript:>>
>>> *Subject:* [dspace-tech] 5.10 Discover/Search showing final thumbnail, 
>>> not first
>>>
>>>  
>>>
>>> We have a collection of art objects/photos on our local implementation, 
>>> and for many objects, the thumbnail that appears on the search results page 
>>> is taken from the last image of the entry, rather than the first one (for 
>>> example a detail of the feet rather than of the whole work). This is a 
>>> problem, because art historians find information by looking at images, and 
>>> so we have carefully selected which is the first image, in order to 
>>> generate the most helpful thumbnail. Now, on the search results page, you 
>>> are more likely to see a secondary image (the building in which a sculpture 
>>> is located or feet, or another odd detail of a sculpture), which makes it 
>>> difficult to use the database for visual research. The odd thing is that 
>>> when you click on the entry, the thumbnail on the individual object page is 
>>> taken from the first image of the entry. So for example on this search page:
>>>
>>>  
>>>
>>>
>>> https://qspace.library.queensu.ca/discover?scope=1974/14832&rpp=10&page=6&query=Image&group_by=none&etal=0
>>>
>>>  
>>>
>>> And then the individual entries:
>>>
>>>    - https://qspace.library.queensu.ca/handle/1974/24713
>>>    - https://qspace.library.queensu.ca/handle/1974/24700
>>>    - https://qspace.library.queensu.ca/handle/1974/24701
>>>
>>> Has anyone come across this previously and have any advice as to how to 
>>> correct this?
>>>
>>>  
>>>
>>> Thanks,
>>>
>>>  
>>>
>>> Alex Fletcher
>>>
>>> Queen's University Library
>>>
>>> Kingston, Ontario, Canada
>>>
>>> -- 
>>> All messages to this mailing list should adhere to the DuraSpace Code of 
>>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected] <javascript:>.
>>> To post to this group, send email to [email protected] 
>>> <javascript:>.
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> ------------------------------
>>>
>>> "The contents of this e-mail (including any attachments) may be 
>>> confidential and/or subject to copyright. Any unauthorised use, 
>>> distribution, or copying of the contents is expressly prohibited. If you 
>>> have received this e-mail in error, please advise the sender by return 
>>> e-mail or telephone and then delete this e-mail together with all 
>>> attachments from your system." 
>>>
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> https://github.com/terrywbrady/info
> 425-298-5498 (Seattle, WA)
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to