In the BrowZine app new users at our institution are prompted with OpenAthens login. For some reason wrong username and password combinations are accepted.

Suggestion 1: validate Openathens credentials. Or even better: Suggestion 2: allow for OpenAthens personalisation:

https://support.thirdiron.com/forums/181845-browzine-features/suggestions/36781075-single-sign-on-openathens-authentication-for-browz

Have ever considered adding months of the issues to the issue numbers in the list of issues on the left hand side? Most journals are citing only month and year now and it's just an extra steps to convert issue numbers in Browzine to the month in the citations.

If a user logs in with OpenAthens, an additional BrowZine account should not be necessary.
https://docs.openathens.net/display/public/partner/Which+resources+link+personalisation+to+the+users%27+OpenAthens+IDs

The bookshelves for My Library display too few titles - I'd prefer a simple list, which would enable perhaps 25 titles on a screen - the bookshelf display might be suitable for kids but it's not really necessary for Browzine's users.

Some publications include links not out to full text but to abstracts, perhaps highlighting presentations at recent conferences or announcing future papers, etc. Currently BrowZine ignores these as "non-articles" but knowing about these could be beneficial to some researchers in the BrowZine environment such as linking to abstracts like this from JCO:

https://ascopubs.org/doi/abs/10.1200/JCO.2019.37.4_suppl.3

After reading a paper, I really want to write down some notes about the paper, like "the main purpose of the paper", "the interesting points of the paper", etc. It is very useful for future review. However, under each item (paper), we can only download, export citation or share. It would be much convenient if we could add some notes under each item.

Some users' workflows involve copying and pasting BibTeX information, vs. downloading a .bib file. This is the user experience for Google Scholar.

Not sure whether changing to just .html would be best, or changing to add another option, e.g.: BibTeX (download) and BibTeX (.html)

Enable images associated with the abstracts to be visible in the ToC. This is especially import for chemistry journals, as the abstract images contain significantly more information than the title.

Visualization of TOC for a journal can be largely improved, at least for the mobile app. I have here some suggestions:
- possibility to sort in different ways (newest first/last, unread first/last)
- possibility to hide read articles
- add gestures to mark as read (swipe)
- visualize TOC as list of titles (as now) or list of titles with abstract (at least few words of it)

Some of our users sign up for eTOCs through JournalTOCs: http://www.journaltocs.ac.uk/. If a user was set-up to receive an eTOC from a journal and they go to the link supplied by this service, would they be able to pull up the full-text through either through BrowZine or LibKey?

For several of our journals, we have access to some years through one source and other years through a different source. Right now, BrowZine only supports one source and chooses the one that provides the most access. We would like BrowZine to support multiple sources so we can have our complete access available.

To help to make it clear to users that they are linking to an external system (i.e. leaving Primo), it would be great if a customisable mouseover could be added to the text View Issue Contents.

It would be useful to be able to select specific titles to be displayed on the widget. This would mean they could be in different subject areas, allow more personalized choices, and avoid embargoed titles.

In My Articles allow me to create a sub-collections under a main collection. For example Under Cystic Fibrosis allow sub-collections for diagnosis, treatment, etc.

Can you offer an Admin-tool for Library Administrators where the admin can monitor (anonymized) usage statistics (e.g. lenght of usage, download number, journal hitlist, day/time of usage, from which pages the user come from e.g. if the Browzine-API is used mostly or another library page...)