Settings and activity
114 results found
-
18 votes
The product manager will review this idea for possible inclusion in a future release.
Jeremy Goldstein
supported this idea
·
-
8 votes
An error occurred while saving the comment Jeremy Goldstein
supported this idea
·
-
9 votes
An error occurred while saving the comment Jeremy Goldstein
commented
This is a critical issue, but also one that is far larger than this specific use case and I'm guessing has impacts on all dates and timestamps present anywhere in the system. For reference https://en.wikipedia.org/wiki/Year_2038_problem
Jeremy Goldstein
supported this idea
·
-
12 votes
An error occurred while saving the comment Jeremy Goldstein
commented
We encounter this quite a bit in our system as well and it is a cause of problems for patrons and confusion for staff.
Jeremy Goldstein
supported this idea
·
-
21 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
supported this idea
·
-
4 votesJeremy Goldstein
shared this idea
·
-
13 votesJeremy Goldstein
supported this idea
·
-
4 votes
An error occurred while saving the comment Jeremy Goldstein
commented
Without the ability to scan items in batch, I've found little incentive to use RFID over the phone's camera for scanning barcodes. There are certainly device limitations in play that would make this unhelpful for many users, but if you do have access to a peripheral such as the one @Shawn shared then adding batch scanning would enormously improve this system.
Jeremy Goldstein
supported this idea
·
-
9 votes
An error occurred while saving the comment Jeremy Goldstein
commented
I never understood why this report didn't include the primary identification point for the invoices it lists out. All invoices are generally referenced by the number assigned by the vendor that produced them and not the internal to Sierra voucher number.
There may be systems where those vouchers are used for something but I've been working with acquisitions with various libraries for nearly 20 years and haven't found one yet who did.Jeremy Goldstein
supported this idea
·
-
7 votesJeremy Goldstein
supported this idea
·
-
15 votesJeremy Goldstein
supported this idea
·
-
13 votesJeremy Goldstein
supported this idea
·
-
30 votes
An error occurred while saving the comment Jeremy Goldstein
commented
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.
Jeremy Goldstein
supported this idea
·
-
7 votesJeremy Goldstein
supported this idea
·
-
20 votesJeremy Goldstein
supported this idea
·
-
4 votesJeremy Goldstein
supported this idea
·
-
13 votesJeremy Goldstein
shared this idea
·
-
5 votesJeremy Goldstein
supported this idea
·
-
3 votesJeremy Goldstein
shared this idea
·
-
28 votes
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.
I know this idea had been submitted at least once previously, but I believe it aged out of the system, though I'm pretty sure it did have some decent support. Very happy to support it again as the lack of this capability is a perpetual annoyance I hear from staff