Settings and activity
121 results found
-
8 votes
Jeremy Goldstein
supported this idea
·
-
8 votesJeremy Goldstein
supported this idea
·
-
6 votes
An error occurred while saving the comment -
7 votesJeremy Goldstein
supported this idea
·
-
12 votesJeremy Goldstein
supported this idea
·
-
16 votes
An error occurred while saving the comment Jeremy Goldstein
commented
After a bit more experimenting I found another common occurrence that can lead to similar behavior. The parser seems to want the city and state to share a line of the address, and to either be separated by a comma, or for the state abbreviation to have both letters capitalized.
"Boston, Ma" works as does "Boston MA". However "Boston ma" or "Boston Ma" does not.
Jeremy Goldstein
shared this idea
·
-
11 votesJeremy Goldstein
supported this idea
·
-
10 votesJeremy Goldstein
supported this idea
·
-
4 votesJeremy Goldstein
shared this idea
·
-
8 votesJeremy Goldstein
supported this idea
·
-
9 votesJeremy Goldstein
supported this idea
·
-
20 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Jeremy Goldstein
commented
Oh yes, I agree with Ray's comment fully it would be amazing to have an anonymized form of this data available.
Jeremy Goldstein
shared this idea
·
-
17 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
An error occurred while saving the comment Jeremy Goldstein
commented
I mostly like this a lot, just treat the API key as a user account, similar to how stat groups are assigned to users in Sierra. The only point of clarification I would put out there is I would still want some of the API endpoints to include a stat group parameter as well so that it is possible to use a variety of stat groups in some circumstances. For example our mobile app has a self checkout feature that needs to use a different stat group for different locations within our consortia. We would still like to issue a single API key to the support vendor for administering that. But in that case even it would still be useful to provide a default stat group other than 0 for the key, and just allow that to be overridden by an implicit stat group parameter as part of an API call.
-
10 votes
The product team will review this idea for consideration for a future release.
Jeremy Goldstein
supported this idea
·
-
10 votes
This enhancement is planned for Sierra 6.5.
Jeremy Goldstein
supported this idea
·
-
21 votes
The product manager will review this idea for possible inclusion in a future release.
Jeremy Goldstein
supported this idea
·
-
21 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 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
Jeremy Goldstein
supported this idea
·
-
23 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 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
·
-
23 votes
The product team will review this idea for consideration for a future release.
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
·
-
23 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Jeremy Goldstein
supported this idea
·
I understand the annoyance here when you don't use fines, but there are other issues that can occur as well from having a patron record open on multiple workstations.
For a sadly common example among our libraries, if a patron checks out an item at one location, changes their mind, and has it checked back in at another terminal, if the account remained open on the original workstation the checkin will fail to occur without providing much of an indicator of that. In that case the patron now has an item checked out erroneously, and Sierra has incorrect data on where that item is currently located. Because of cases like this I would still want there to be a warning that the patron record needs to be closed, regardless of the fines issue.