Settings and activity
12 results found
-
3 votes
Victor Zuniga
supported this idea
·
-
14 votes
The product team will review this idea for consideration for a future release.
Victor Zuniga
supported this idea
·
An error occurred while saving the comment Victor Zuniga
shared this idea
·
-
17 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Victor Zuniga
commented
I think this would address the issue of permissions to generate reports for internal or external use (vendors). As Jeremy mentioned, there is no viable way to provide access to the circulation transactions without exposing the entire database. This proposal finds a compromise for this particular scenario.
Victor Zuniga
supported this idea
·
-
27 votes
An error occurred while saving the comment Victor Zuniga
commented
Yes, this will be a great addition. I know that in recent upgrades to the Patron REST API, there is the ability to assign a value for the stat group. You still rely on the vendor to make this change.
It would be great for library staff members to control this feature via the user interface.
Victor Zuniga
supported this idea
·
-
5 votesVictor Zuniga
supported this idea
·
-
6 votes
An error occurred while saving the comment Victor Zuniga
commented
Also, can we provide an option to export the reading history as a .csv file?
An error occurred while saving the comment Victor Zuniga
commented
We recently encountered this issue with a patron request to include the checkout date. In addition to the checkout date, including repeat checked-out items (aka duplicates) would be ideal. It is not unusual for some patrons to borrow the same item multiple times, especially if their reading history spans over 10+ years. Patrons would love to see each of these entries when exporting the data from the system. Currently, duplicate titles are exported only once. This misleads the patron into thinking they checked out fewer items than what the exported email would display.
Victor Zuniga
supported this idea
·
-
23 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Victor Zuniga
supported this idea
·
-
69 votesVictor Zuniga
supported this idea
·
-
30 votes
The product team will review this idea for consideration for a future release.
Victor Zuniga
supported this idea
·
-
9 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Victor Zuniga
supported this idea
·
-
13 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Victor Zuniga
supported this idea
·
-
75 votes
An error occurred while saving the comment Victor Zuniga
commented
Yes, please implement this functionality into LX Starter.
This should be an expected functionality out of the box.
Please migrate the existing code workflow from JasperStudio (Print Templates) into LX Starter.
Victor Zuniga
supported this idea
·
Thanks for the clarification, Jeremy. Yes, we want to maintain the existing stat group parameter. If a vendor does not implement the provided stat group code, this will serve as a backup plan to keep track of their usage on the system via the Patron API. Thanks!