Settings and activity
122 results found
-
17 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment 
Jeremy Goldstein
supported this idea
·
-
4 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
The split name fields are how the information is stored in the underlying SQL tables so this seems pretty feasible and very nice to have.
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
·
-
27 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Jeremy Goldstein
shared this idea
·
-
18 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
9 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
Automating clean up is one thing, though I'm not sure AI is the ideal approach to take given the differences in codes across customers.
We've made some custom scripts using SQL and the available APIs to automate some low lying clean up tasks such as applying ptypes based on address information.
But for the most part we've needed to instead generate reports for staff to look over and make manual corrections. Items with seemingly incorrect item types is a good example. Something with a book itype attached to a bib record with a mattype like dvd could be a matter of a type in the item, or the item could be attached to the wrong bib entirely. Making that correction requires staff intervention and can't be outright automated.
-
29 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
·
-
13 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
commented
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.
Jeremy Goldstein
supported this idea
·
-
10 votesUNDER REVIEW · 1 comment · ILS - Sierra » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Jeremy Goldstein
supported this idea
·
-
9 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
·
-
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
·
-
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
·
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.