Settings and activity
117 results found
-
28 votes
This enhancement is planned for Sierra 6.5.
Jeremy Goldstein
supported this idea
·
-
13 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Jeremy Goldstein
shared this idea
·
-
12 votesJeremy Goldstein
supported this idea
·
-
8 votesUNDER REVIEW · 2 comments · ILS - Sierra » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Jeremy Goldstein
supported this idea
·
-
10 votesUNDER REVIEW · 1 comment · ILS - Sierra » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Jeremy Goldstein
supported this idea
·
-
8 votesUNDER REVIEW · 1 comment · ILS - Sierra » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Jeremy Goldstein
supported this idea
·
-
6 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 Jeremy Goldstein
commented
I have an alternate suggestion for an approach to take to address this problem. As someone who travels between locations with a laptop to work the IP based approach may not be the best option.
It's been some time since then, but when I was a user of a different ILS this was addressed by having the workstation/client "register" to be associated with a location, entirely outside of the user logon process. On a daily basis the user only has to use their single personal logon and the location for the workstation would remain persistent (though it could be altered if need be).
Jeremy Goldstein
supported this idea
·
-
14 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
supported this idea
·
-
12 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
supported this idea
·
-
13 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
supported this idea
·
-
6 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
supported this idea
·
-
10 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
supported this idea
·
-
40 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
shared this idea
·
-
19 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 Jeremy Goldstein
commented
Besides the record count report mentioned in the idea we've had many requests over the years for cost per circ reports, which we've only ever been able to estimate given that our items generally contain list prices (for billing purposes) and not the library's cost (residing in the order record paid field).
I have reservations about establishing a direct link between an order and an item given the need at many libraries to routinely delete old order records, but just having the fund code available as an item field could be a decent compromise and enough to provide some additional reporting options.
Jeremy Goldstein
supported this idea
·
-
9 votesJeremy Goldstein
supported this idea
·
-
8 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
shared this idea
·
-
13 votes
An error occurred while saving the comment Jeremy Goldstein
commented
This is still quite important to me as being able to directly search for a hold as opposed to having to come at it sideways via an item or patron record focused search would make the API far more user friendly.
That said, personally I can knock it back down a bit because of the additional data that has been added to the SierraDNA hold view since this was first written. The pickupByDate field is now available there so the particular use case cited in the idea can now be accomplished more easily. But I still want a way to search for a hold id more easily so they can then be used with the other hold endpoints.Jeremy Goldstein
supported this idea
·
-
20 votesJeremy Goldstein
supported this idea
·
-
14 votesJeremy Goldstein
supported this idea
·
-
13 votesJeremy Goldstein
supported this idea
·
For an additional use case we also have a number of libraries who are heavy users of x-records with invoices and in those cases the invoice is the only point where such a message could be triggered.