Settings and activity
362 results found
-
2 votes
Shawn P. Farrell
shared this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
18 votesShawn P. Farrell
supported this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
4 votesShawn P. Farrell
supported this idea
·
-
7 votes
An error occurred while saving the comment Shawn P. Farrell
supported this idea
·
-
14 votesShawn P. Farrell
supported this idea
·
-
23 votesShawn P. Farrell
supported this idea
·
-
29 votesShawn P. Farrell
supported this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
4 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
5 votesShawn P. Farrell
shared this idea
·
-
1 voteShawn P. Farrell
shared this idea
·
-
2 votes
An error occurred while saving the comment Shawn P. Farrell
commented
Just a quick correction to something mentioned in the first paragraph above. Courtesy/autorenewal texts ARE available to Sierra libraries. The documentation we received uses the Polaris notification type table & the codes identifying the different notice types were not as aligned as was thought.
That being said, including an item identifier in the reporting would be incredibly useful for tracking & troubleshooting texts (and for that matter, calls made via Vega Interact Voice).
Shawn P. Farrell
shared this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
1 voteShawn P. Farrell
shared this idea
·
-
1 voteShawn P. Farrell
shared this idea
·
CHPL would appreciate this as well, especially if the point at which old notices are purged can be determined by the library. Because of the volume of notices we send out & how long we've been using LX Starter, our performance metrics for configured notice jobs take a while to populate. Retrieving log data can also take quite a bit of time.
Optimally, we'd like to be able to set the same retention limit for logs on all notice types, whether they're e-mail, phone, or print.