Settings and activity
131 results found
-
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
supported this idea
·
-
9 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.
-
11 votesJeremy Goldstein
supported this idea
·
-
13 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
·
-
64 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
·
-
8 votes
The product manager will review this idea for possible inclusion in a future release.
Jeremy Goldstein
supported this idea
·
-
14 votesJeremy Goldstein
supported this idea
·
-
22 votesJeremy Goldstein
supported this idea
·
-
4 votesJeremy Goldstein
supported this idea
·
-
7 votesJeremy Goldstein
supported this idea
·
-
17 votesJeremy Goldstein
supported this idea
·
-
17 votesJeremy Goldstein
supported this idea
·
-
21 votesJeremy Goldstein
supported this idea
·
-
64 votes
An error occurred while saving the comment Jeremy Goldstein
commented
For another use case, we use shared logins for nearly all of our user accounts and have a naming schema used for helping to identify the role each is used for (think circulation vs circulation supervisors). We have needed to modify that schema in the past, but doing so now means creating whole new accounts instead of simply updating our existing ones in order to fit with such a change.
Jeremy Goldstein
supported this idea
·
-
10 votesJeremy Goldstein
supported this idea
·
-
9 votesUNDER REVIEW · 1 comment · ILS - Sierra » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Jeremy Goldstein
commented
I would love a way to more easily get this data into a tool like Excel, I'm just wondering if a print template is the way to go as opposed to a straight export tool more like the one recently introduced to the fund report
-
11 votesJeremy Goldstein
shared this idea
·
-
50 votes
This idea was selected in MEEP voting for Sierra 6.5.
Jeremy Goldstein
supported this idea
·
-
57 votes
An error occurred while saving the comment Jeremy Goldstein
commented
The use case for this idea makes a ton of sense though such a feature would have to be VERY carefully implemented for sites like ours with 100's of loan rules. There would have to be at a minimum some way to limit the loan rules the global change is being applied to.
Jeremy Goldstein
supported this idea
·
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.