Replacement for Post-List Hovers

Issue #1945 resolved
Former user created an issue

Some users have trouble identifying which publicationpost to click because the publication metadata is abbreviated and not completely visible especialy with lower screen resolutions. The old javascript based Post-List Hovers were removed because they strongly interferred with the usability of clickable elements around the hover element.

To show the required information, we like to extend the title attribute of the link behind the title of the publication post in the list.

Comments (7)

  1. Former user Account Deleted

    Robert's requirements:

    The post list entry for post http://www.bibsonomy.org/bibtex/27a8b6e9196b6f6321fcdaa62ae3c7567/jaeschke should also contain "Journal of the Association for Information Science and Technology 65(4):656--669 (2014)" in the title-attribute.

    My Proposal (for completeness): If we need this amount of fields we coud directly use a JabRef Layout like DIN1505 in the title attribute. This would be standard compliant and there is no need to pick the proper fields (booktitle / journal) again. A CSL rendered string would be even better but this might be to complex for a quick solution.

    @mamerz if this is easily done, use JabRef. Otherwise render fields directly

  2. Robert Jäschke

    I would strongly suggest to not use Jabref for that, since it might be slow! We need something simple. Therefore, please use the existing JSP-based rendering mechanism that is also used to render the "www" tab on the publication details page. It just needs to render the meta information without title and authors.

  3. Former user Account Deleted

    Sadly, i couldnt reuse the "www"-tab Code, cause it doesnt allow rendering into a attribute. I created a new JSP EL Function implemented in BibTexListTitleHoverFormatter which renders the title attribute based on the layout of the "www"-tab.

  4. Robert Jäschke

    I guess this was a big effort. Thanks for your work.

    It would have been better, if you had written this comment before you started to implement this. Often, the complexity of tasks is not clear at the beginning and we can understand the tasks completely only from your feedback. Thus it is important that before you start the implementation, you explain problems and your proposed solution.

    By the way, it would have been no problem to render the <bib:desc> tag into a variable by using the following code:

    <c:set var="postmetadata">
       <bib:desc publication="${post.resource}"/>
    </c:set>
    <a href="${bibUrlTemplate}" title="${fn:escapeXml(postmetadata)}"><c:out value="${bibTitle}" /></a>
    

    That would have solved the basic problem and caused a new one: <bib:desc> also renders HTML which of course you don't want here. Hence, we would need a function stripHTML() which strips off HTML tags and escapes XML and use that then, e.g.,

    <a href="${bibUrlTemplate}" title="${fn:escapeXml(mtl:stripHTML(postmetadata))}"><c:out value="${bibTitle}" /></a>
    

    Would that be the solution? Well, not completely: the authors are rendered although we don't want them. This could be solved by modifying the <bib:desc> tag with a parameter to enable/disable author rendering.

    Although this is also not a perfect solution, it would clearly avoid copying code and could also be easily removed once we found a better solution.

  5. Former user Account Deleted

    since we now already have a (not too long nor too ugly) piece of java code rendering what we want for our hover, I would leave it like this and consider the task as solved. The redundant code is not really that much redundant anyway when considering that changing the hover does not introduce inconsitency with the www export and vice versa.

  6. Log in to comment