Settings and activity
200 results found
-
10 votes
Alison Pruntel
supported this idea
·
-
19 votesAlison Pruntel
supported this idea
·
-
22 votesAlison Pruntel
supported this idea
·
-
20 votesAlison Pruntel
shared this idea
·
-
17 votes
An error occurred while saving the comment -
7 votesAlison Pruntel
supported this idea
·
-
9 votesAlison Pruntel
supported this idea
·
-
19 votesAlison Pruntel
supported this idea
·
-
5 votes
An error occurred while saving the comment Alison Pruntel
commented
Linked accounts in Sierra (not sure about Polaris) are not the same as managed accounts in III mobile. We use linked accounts for children/parents, and allow for people to check out items for each other with linked accounts (paperwork involved). Anyone can add any library card to the mobile app under managed accounts.
-
5 votesAlison Pruntel
supported this idea
·
-
6 votes
An error occurred while saving the comment Alison Pruntel
commented
This continues to happen with us, as often times our orders are status "a," fully paid. Very confusing for the patrons.
Alison Pruntel
supported this idea
·
-
37 votesAlison Pruntel
supported this idea
·
-
2 votesAlison Pruntel
supported this idea
·
-
5 votes
79% of strategic partner feedback identified PayPal as the preferred payment for integration.
Alison Pruntel
supported this idea
·
-
6 votesAlison Pruntel
supported this idea
·
-
11 votesAlison Pruntel
supported this idea
·
-
75 votes
This idea was selected in MEEP voting for Sierra 6.5.
An error occurred while saving the comment Alison Pruntel
commented
Functional requirements need to include the ability to edit the patron record, etc., from a review file. That's when we find this the most frustrating. I hope that's possible, can't tell by the description below.
An error occurred while saving the comment Alison Pruntel
commented
This would certainly save a lot of time. Would also like to be able to open the patron record (and edit) from a review file.
Alison Pruntel
supported this idea
·
-
41 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Alison Pruntel
supported this idea
·
-
4 votesAlison Pruntel
supported this idea
·
-
28 votes
This report is considered a bug and we will be including the fix of it with the relevancy improvements and updates that we plan to make this year.
Alison Pruntel
supported this idea
·
.jpg){kind=link}
Our fines paid in Vega are assigned a stat group (as is the checkin of the item)...I vaguely remember this being part of our setup (we were an early adopter). I did learn that Sierra REST API requests (for renewals at least) aren't assigned a staff group, and I would like for that to be the same stat group that we're using for the fines paid/and any associated checkin (if paying the replacement cost of an item).