Settings and activity
114 results found
-
8 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
An error occurred while saving the comment -
9 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
shared this idea
·
-
33 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
·
-
25 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
@jonathan Currently the Hold API for Sierra only allows for the changing of a hold pickup location and whether or not the hold is frozen....well or just cancelling the hold entirely. So that limits the ability of third party systems like Aspen to take other actions.
Jeremy Goldstein
supported this idea
·
-
17 votes
The product manager will review this idea for possible inclusion in a future release.
Jeremy Goldstein
supported this idea
·
-
14 votes
The product manager will review this idea for possible inclusion in a future release.
Jeremy Goldstein
supported this idea
·
-
17 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
Our annoying version of this problem is that most of our libraries use a macro for tabbing to the status field, typing a w for withdrawn, and saving the record.
If their cursor is in the wrong location when they trigger the macro what winds up happening more often then not is 'w' is typed into the location field instead and the item winds up in the scope of our long suffering Watertown library. We probably wind up fixing a dozen out of scope items a week from this.
Jeremy Goldstein
supported this idea
·
-
20 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
Would this feature require having the volume record add on for Sierra?
Jeremy Goldstein
supported this idea
·
-
20 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
The setting you describe is actually the default system behavior when you first create a Sierra login, but that breaks if you change your view. That change then gets applied to all the functional areas and there's no way to restore the default behavior (other than creating a new login).
Jeremy Goldstein
supported this idea
·
-
4 votes
The product manager will review this idea for possible inclusion in a future release.
Jeremy Goldstein
supported this idea
·
-
8 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
I can certainly see the value in this for some locations. In our consortia we tend to have a large number of patrons that will freely move between locations so home library can be a bit less reliable, but even then I could still see this being a helpful way to narrow down searches for common names.
Jeremy Goldstein
supported this idea
·
-
5 votesJeremy Goldstein
supported this idea
·
-
13 votes
An error occurred while saving the comment Jeremy Goldstein
commented
Absolutely a critical feature that the system has been lacking, presumably because of the added complexity of having to deal the individual encumbrance adjustments this would impact as well. but with work on a batch cancelation feature under way I'm very hopeful this can be considered as well as something I've only wanted for as long as I've been a librarian.
Jeremy Goldstein
supported this idea
·
-
19 votesJeremy Goldstein
supported this idea
·
-
8 votes
An error occurred while saving the comment Jeremy Goldstein
commented
I don't remember this previously, but looking at the Swagger documentation on our site there is currently a delete endpoint of /v6/patrons/{id}/checkouts/history/{checkoutHistoryId}, which is distinct from the delete endpoint /v6/patrons/{id}/checkouts/history for deleting the full history
-
12 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
This is nice from a patron service standpoint but I know some of our member libraries would object given space constraints on their hold shelves not to mention the wasted labor on the part of staff retrieving the item and likely sending it through delivery.
I can certainly see the value for other libraries but this would really need to be an optional feature that organizations like us could opt out of.
Jeremy Goldstein
supported this idea
·
-
19 votesJeremy Goldstein
supported this idea
·
An error occurred while saving the comment Jeremy Goldstein
commented
I would be thrilled to be able to use a similar editor to the one found in LXStarter for non-notice based templates. But I'm not sure if that is the right platform for this given that it is designed for actions that occur outside of Sierra and these very much need to be incorporated back into the client to be utilized.
-
7 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
I can't believe I'm voting to support non-standard data but in this case absolutely. We often have to get creative with records and certainly have plenty of fully non-MARC bibs within our system for various purposes. The API shouldn't have a problem with those instances.
Jeremy Goldstein
supported this idea
·
-
10 votes
The product manager will review this idea for possible inclusion in a future release.
Jeremy Goldstein
shared this idea
·
-
13 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
From my understanding (thanks in large part to Ray having passed along the response to a ticket he had opened) the hold_removed includes all holds that were cancelled, expired, or cleared from the holdshelf.
Then for filled holds they exist in the table for the period between when they have been filled and the subsequent time that clear holdshelf is run.
Jeremy Goldstein
supported this idea
·
An error occurred while saving the comment Jeremy Goldstein
commented
Or retain the data in the new hold_removed table for a longer period of time. Either would be quite helpful for projects. In particular we use hold data frequently as a gauge of patron demand so having a historical record of the demand for certain materials would be incredibly helpful.
There is an hourly circulation by transaction type report in Decision Center. Do you need a version of this that breaks transactions out by stat group / terminal?