Settings and activity
117 results found
-
11 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
18 votesJeremy Goldstein
supported this idea
·
-
17 votesJeremy Goldstein
supported this idea
·
-
35 votes
An error occurred while saving the comment Jeremy Goldstein
supported this idea
·
-
18 votesJeremy Goldstein
supported this idea
·
-
24 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
4 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
·
-
4 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
shared this idea
·
-
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
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.
-
6 votes
An error occurred while saving the comment Jeremy Goldstein
commented
@Semane Rachid There is currently an item on the Sierra Product board (listed under upcoming so it's not targeted for a particular release yet) pertaining to pickup locker support. That's another location to provide additional feedback to help make this happen https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/501-support-lockers-for-hold-pickup
Jeremy Goldstein
supported this idea
·
-
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
·
-
17 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
·
-
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
·
-
26 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Jeremy Goldstein
shared this idea
·
-
16 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.
The lack of this feature is precisely the reason that our consortia opted to not move to LX Starter at this point in time. We love the editor and really want to be able to utilize this product but until centralized notices are available we simply cannot use this product.