Evergreen

Bug #1424815
Comment #4

Comment 4 for bug 1424815

Revision history for this message

Don Butterworth (don-butterworth) wrote on 2017-06-14: Re: [Bug 1424815] Re: Wishlist: Add a “read more” feature to the OPAC bib record view for fields with lots of text

I like what Kathy has done a lot !

Question. Will there be a setting that can be made by each library
indicating how many characters display before the Read More feature
activates, or is this to be a hard setting?

Don

On Fri, Jun 2, 2017 at 10:51 AM, Kathy Lussier <email address hidden>
wrote:

> I took some time to look at this code over the past couple of days.
> Overall, the code in Jake's part 1 branch was successful in displaying
> more contents of the field. However, I wasn't a big fan of the way it
> displayed the additional content - see the screencast at
> https://drive.google.com/file/d/0B74gDMUDwDXqeU50VHdMdVpQLUk/
> view?usp=sharing.
>
> The rest of the field displays after the 'read more' text, and I had
> trouble finding a way to change that behavior using the checkbox
> implementation. I decided to try a simpler CSS approach than what Jake
> was using. I've added a commit to the above work-in-progress branch that
> shows my proposed implementation. Still no javascript required.
>
> I have a few todos I still want to work on:
> - The current implementation only works with note fields. We have a local
> use case for truncating the title field on the search results page as well.
> I would like to add a setting to make that happen for sites that want it.
> - We need to account for undefined cont.trunc_length fields
> - I would like to put more settings in config.tt2. On the one hand, I like
> the fact that we can define the maximum character length before truncation
> on a field-by-field basis. But I also think it will be easier for most
> sites to just turn it on and identify the maximum character length in one
> setting for all notes.
>
> Before I work on the remaining to dos, I would like to get some feedback
> on the branch just to make sure I'm moving in the right direction.
>
> Alternatively, if bug 1642086 is merged, we could explore using the
> "Read More" jquery plugin. However, since one of the guidelines for
> jquery use was to only use it for things that can't be handled easily
> without javascript, I wanted to first see if I could get Jake's code
> working without the need to use javascript.
>
> I have a working implementation of it at
> https://mlnc4.noblenet.org/eg/opac/record/249 if anyone wants to see it
> in action.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1424815
>
> Title:
> Wishlist: Add a “read more” feature to the OPAC bib record view for
> fields with lots of text
>
> Status in Evergreen:
> Confirmed
>
> Bug description:
> The issue:
> When fields are very long in a bibliographic record and the full text
> appears immediately in the display, a patron is forced to scroll down to
> see additional record details.
>
> Recommendation:
> In order to preserve a more compact, uniform display on the OPAC Record
> Detail screen, create a feature that limits the amount of text displayed in
> some fields; particularly in note fields such as Content Notes, and Summary
> Notes. When text exceeds the designated limit, hot text such as “read more”
> or "View complete summary” or “View full contents” will appear which can be
> clicked on in order to expand and display the full text.
>
> Particulars:
> Michael Schell indicated that Fort Erie Public Library has already
> implemented a “Read More” feature in their test catalog that uses the
> jQuery plugin. Michael says, “Here is a link to an example. It uses the
> lightweight jQuery plugin readmore.js from here, and is super easy to setup
> and has some great options. All it requires is that the [%- INCLUDE
> "opac/parts/record/contents.tt2" %] from the summary.tt2 be inside
> article tags like this:
> <article>
> [%- INCLUDE "opac/parts/record/contents.tt2" %]
> </article>
>
> Several individuals have indicated support for this enhancement
> request and some noted that they would like this feature included in a
> public library PAC as well.
> http://georgialibraries.markmail.org/thread/tgj2qjwjez547cg7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1424815/+subscriptions
>

--
Don Butterworth
Collection Management Librarian /
Faculty Associate
B.L. Fisher Library
Asbury Theological Seminary
<email address hidden>
(859) 858-2227

I like what Kathy has done a lot !

Question. Will there be a setting that can be made by each library
indicating how many characters display before the Read More feature
activates, or is this to be a hard setting?

Don

On Fri, Jun 2, 2017 at 10:51 AM, Kathy Lussier <1424815@bugs.launchpad.net>
wrote:

> I took some time to look at this code over the past couple of days.
> Overall, the code in Jake's part 1 branch was successful in displaying
> more contents of the field. However, I wasn't a big fan of the way it
> displayed the additional content - see the screencast at
> https://drive.google.com/file/d/0B74gDMUDwDXqeU50VHdMdVpQLUk/
> view?usp=sharing.
>
> The rest of the field displays after the 'read more' text, and I had
> trouble finding a way to change that behavior using the checkbox
> implementation. I decided to try a simpler CSS approach than what Jake
> was using. I've added a commit to the above work-in-progress branch that
> shows my proposed implementation. Still no javascript required.
>
> I have a few todos I still want to work on:
> - The current implementation only works with note fields. We have a local
> use case for truncating the title field on the search results page as well.
> I would like to add a setting to make that happen for sites that want it.
> - We need to account for undefined cont.trunc_length fields
> - I would like to put more settings in config.tt2. On the one hand, I like
> the fact that we can define the maximum character length before truncation
> on a field-by-field basis. But I also think it will be easier for most
> sites to just turn it on and identify the maximum character length in one
> setting for all notes.
>
> Before I work on the remaining to dos, I would like to get some feedback
> on the branch just to make sure I'm moving in the right direction.
>
> Alternatively, if bug 1642086 is merged, we could explore using the
> "Read More" jquery plugin. However, since one of the guidelines for
> jquery use was to only use it for things that can't be handled easily
> without javascript, I wanted to first see if I could get Jake's code
> working without the need to use javascript.
>
> I have a working implementation of it at
> https://mlnc4.noblenet.org/eg/opac/record/249 if anyone wants to see it
> in action.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1424815
>
> Title:
>   Wishlist: Add a “read more” feature to the OPAC bib record view for
>   fields with lots of text
>
> Status in Evergreen:
>   Confirmed
>
> Bug description:
>   The issue:
>   When fields are very long in a bibliographic record and the full text
> appears immediately in the display, a patron is forced to scroll down to
> see additional record details.
>
>   Recommendation:
>   In order to preserve a more compact, uniform display on the OPAC Record
> Detail screen, create a feature that limits the amount of text displayed in
> some fields; particularly in note fields such as Content Notes, and Summary
> Notes. When text exceeds the designated limit, hot text such as “read more”
> or "View complete summary” or “View full contents” will appear which can be
> clicked on in order to expand and display the full text.
>
>   Particulars:
>   Michael Schell indicated that Fort Erie Public Library has already
> implemented a “Read More” feature in their test catalog that uses the
> jQuery plugin. Michael says, “Here is a link to an example.  It uses the
> lightweight jQuery plugin readmore.js from here, and is super easy to setup
> and has some great options.  All it requires is that the [%- INCLUDE
> "opac/parts/record/contents.tt2" %] from the summary.tt2 be inside
> article tags like this:
>   <article>
>         [%- INCLUDE "opac/parts/record/contents.tt2" %]
>   </article>
>
>   Several individuals have indicated support for this enhancement
>   request and some noted that they would like this feature included in a
>   public library PAC as well.
>   http://georgialibraries.markmail.org/thread/tgj2qjwjez547cg7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1424815/+subscriptions
>

-- 
Don Butterworth
Collection Management Librarian /
Faculty Associate
B.L. Fisher Library
Asbury Theological Seminary
don.butterworth@asburyseminary.edu
(859) 858-2227