Settings and activity
83 results found
-
26 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
7 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
14 votesJeremy Goldstein
shared this idea
·
-
5 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
5 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
shared this idea
·
-
41 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment -
30 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
This really would make working with the APIs a lot easier an improved prospect and be a big step toward fulfilling the promise of opening up the system.
Jeremy Goldstein
supported this idea
·
-
18 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
I can see this being hugely helpful. We have restrictions in place to keep libraries from generally editing items belonging to someone else, you don't want to let someone change the location to steal a popular book after all. But this is a great use case for why there should be a way to make a particular exception to that.
Jeremy Goldstein
supported this idea
·
-
11 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Jeremy Goldstein
supported this idea
·
-
6 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
An error occurred while saving the comment Jeremy Goldstein
commented
Really adding some basic sorting options to all the endpoints that return records would be amazing
Jeremy Goldstein
supported this idea
·
-
34 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Jeremy Goldstein
shared this idea
·
-
20 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
50 votes
Support for a newer version of Jaspersoft Studio will be provided in Sierra 6.7.
Jeremy Goldstein
shared this idea
·
-
28 votesJeremy Goldstein
supported this idea
·
-
26 votes
An error occurred while saving the comment Jeremy Goldstein
commented
The only way to do something like this currently is via the API's, which require you to have a developer on staff and from my experience is generally a lot more limited (and risky) to use for batch updates. Adding this to scheduler would greatly improve Sierra's capabilities merely by taking advantage of the infrastructure that's already present in the system.
Jeremy Goldstein
supported this idea
·
-
52 votes
An error occurred while saving the comment Jeremy Goldstein
commented
We have received sooooooo many complaints about this system behavior over the years. Staff have had to waste an inordinate amount of time on deduping the produced lists, which has only gotten worse with the introduction of the pagination issue (SIERRA-38727) that was introduced in 6.0.
Jeremy Goldstein
supported this idea
·
-
14 votes
An error occurred while saving the comment Jeremy Goldstein
commented
These errors will occasionally show up in the client too so this is a bit broader of an issue than just the sql views.
There’s a glitch with the self checkout feature in our mobile app where if an item is rapidly scanned twice it doesn’t get checked out correctly and the only reason we know about that is the items wind up with a due date of 1969.
Jeremy Goldstein
supported this idea
·
-
65 votes
This will be a part of the Renewal Journey feature
An error occurred while saving the comment Jeremy Goldstein
commented
Yes, here is the enhancement on the LX Starter roadmap https://portal.productboard.com/iii/15-vega-product-portal/c/397-default-journeys
Jeremy Goldstein
supported this idea
·
-
16 votesJeremy Goldstein
supported this idea
·
-
22 votesJeremy Goldstein
supported this idea
·
The hold table doesn't currently store that information beyond the timestamps for when it was placed and when it was placed on a holdshelf if that's occurred...but the circ_trans table does include the application_name and stat_group_code_num from when the holds are first placed.