Settings and activity
228 results found
-
14 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo supported this idea ·
-
13 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo supported this idea ·
-
17 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo supported this idea ·
-
13 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo supported this idea ·
-
59 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo supported this idea ·
-
26 votes
Nicole Turzillo supported this idea ·
-
18 votes
An error occurred while saving the comment Nicole Turzillo supported this idea ·
-
31 votes
Nicole Turzillo supported this idea ·
-
21 votes
An error occurred while saving the comment Nicole Turzillo commented
This sounds like a great improvement for our big consortium. It is similar to features in Encore and WebPAC that our patrons like and use.
Nicole Turzillo supported this idea ·
-
12 votes
Nicole Turzillo supported this idea ·
-
20 votes
Nicole Turzillo supported this idea ·
-
23 votes
Nicole Turzillo supported this idea ·
-
17 votes
Nicole Turzillo supported this idea ·
-
19 votes
An error occurred while saving the comment Nicole Turzillo commented
The current generic default cost leads to patrons being overcharged for items with values significantly below the default. For instance, our default book cost is $25. Consequently, if a patron pays online without contacting their library, they could pay $25 for a paperback that the owning library values at only $7.99.
Nicole Turzillo supported this idea ·
-
12 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Nicole Turzillo commented
We manually clear this field system-wide every month, retaining the last patron number for 90 days. A more flexible solution would be to automatically clear this field based on a site-specific retention period.
Nicole Turzillo supported this idea ·
-
21 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo supported this idea ·
-
17 votes
The product team will review this idea for consideration for a future release.
Nicole Turzillo supported this idea ·
-
17 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Nicole Turzillo commented
Just like Jeremy's consortium, we have vendors that use a single key for multiple libraries. Consequently, while the API endpoints will need a stat group parameter for data separation, it would be a significant improvement in usability if the stat group could be assigned as a default to the key.
-
16 votes
An error occurred while saving the comment Nicole Turzillo commented
Our consortium's policy includes purging patron records with no circulation activity over a specified period. Given that several vendors use the REST API to authenticate patrons, and many libraries have patrons who primarily use online services, there is a need for the Patron Validate process to update the CIRCACTIVE field. This would ensure that these online-only users are correctly identified as active.
Nicole Turzillo supported this idea ·
-
23 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Nicole Turzillo commented
Given our current practice of using the Highest Level Overdue to block after billing, and the need to preserve the current overdue-to-bill interval across our 500+ loan rules, this new block must operate within those existing parameters. This would provide an additional incentive for returning overdue items before they are billed.
Nicole Turzillo supported this idea ·
The current "record locked" message frequently appears in workflows unrelated to fines, causing ongoing staff confusion.