Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relocating 520 field to top of page #130

Open
gbnewby opened this issue Oct 18, 2024 · 6 comments
Open

Relocating 520 field to top of page #130

gbnewby opened this issue Oct 18, 2024 · 6 comments

Comments

@gbnewby
Copy link
Contributor

gbnewby commented Oct 18, 2024

As you've seen, we have automatically-generated summaries in the MARC 520 field, for nearly every title.

To make these easier for readers to find, I'd like to move those fields to the top of the landing page- under the title.

The idea would be to take the first N words (N=50 or so), with an "About this book:" label. Then, a "More..." link at the end to display the full summary.

We have a designer who has mocked up some bigger changes, which we could consider simultaneously. But moving the summary to the top of the page might be its own separate task.

The 520 fields are not currently used for anything else - just the summaries.

Let me know how this sounds, and I can provide a more detailed diagram to consider.

@eshellman
Copy link
Contributor

  1. You don't want to truncate, you want to use a :hover pseudoclass in css and you probably want to suppress it on small screens.
  2. the template code is not hard, just annoying because of the way autocat3 works.
  3. There are (mid 2 digits) books with 2 520 entries.
  4. I can't work on autocat3 till December.

@gbnewby
Copy link
Contributor Author

gbnewby commented Oct 19, 2024 via email

@ddaws
Copy link

ddaws commented Dec 7, 2024

It would be great to see the design mock ups if you don't mind sharing :)

@gbnewby
Copy link
Contributor Author

gbnewby commented Dec 8, 2024 via email

@ddaws
Copy link

ddaws commented Dec 9, 2024

Thank you!

I have left feedback in the mock ups but I'll post the feedback here as well

  • The new landing page looks great!
  • Would be nice to link to docs in the header. Docs would include
    • How to mirror
    • How to integrate the OPDS 2.0 API
    • Where to get a DB dump
    • OpenAPI spec for the OPDS 2.0 API (support auto generating client code in different languages)
  • There are multiple search interfaces. I think this is sub-optimal because
    • More code to maintain
    • The top bar search is not as good as other search forms
    • I don't want to fill out a form. Forms don't feel natural
  • Would be nice if the top search was the only search and we support a search syntax to make it powerful
    • example, author:"CS Lewis" lang:en other search terms
    • This could feel natural with autocomplete
  • Would be nice to have a view for series, aka books that are part of a series
    • The series could have a view that links to all of the books in the series
  • Would be nice to be able to peak into views
    • example, Click on a book in the search view and a panel slides in from the right, partially covering the search view
    • The right panel would show summary info, with the ability to expand it to nav to the page

Sorry for the bullet notes. I'm just speeding along and have to get back to the family 🙂

@JohannesSeikowsky
Copy link

Looks pretty good to me! I've forwarded the designed to a friend of mine who's a UX designer for more feedback.
I would speculate that there are two main user behaviors that the page should be designed for.
For one users who are looking for something specific - either a specific book or books on a specific topic.
And secondly users who are "just browsing" without a very specific goal in mind.
Seems to me that this design is a good starting point to cater to both of those cases.
I agree with the previous comment that improving the search seems important.
One other thing that crossed my mind is mobile. For many pages substantial traffic comes from mobile.
There should probably be a mobile version ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants