Settings and activity
43 results found
-
10 votes
For the withdrawn example, does this really require custom circulation statuses? Or just a way to indicate/query the reason an item was withdrawn?
The reason Polaris has traditional restricted circulation statuses is because of our automated processes around certain statuses. Using the withdrawn example, our automatic Lost/Missing to Withdrawn processing would not know about custom statuses or which one to use.
If we reworked this enhancement as needing to be able to track/report on withdrawn reasons, we could plan for that within the automated processes.
Joyce Peter
supported this idea
·
-
6 votesJoyce Peter
supported this idea
·
-
5 votesJoyce Peter
supported this idea
·
-
10 votesJoyce Peter
supported this idea
·
-
55 votesJoyce Peter
supported this idea
·
-
43 votesJoyce Peter
supported this idea
·
-
4 votesJoyce Peter
shared this idea
·
-
44 votesJoyce Peter
supported this idea
·
-
9 votesJoyce Peter
supported this idea
·
-
15 votesJoyce Peter
shared this idea
·
-
23 votesJoyce Peter
supported this idea
·
-
26 votesJoyce Peter
supported this idea
·
An error occurred while saving the comment -
18 votesJoyce Peter
supported this idea
·
-
20 votesJoyce Peter
supported this idea
·
-
14 votesJoyce Peter
supported this idea
·
-
32 votesJoyce Peter
supported this idea
·
-
38 votesJoyce Peter
supported this idea
·
-
35 votesJoyce Peter
supported this idea
·
-
17 votesJoyce Peter
supported this idea
·
-
41 votesJoyce Peter
supported this idea
·
I also use LAD when gathering inactive patron records to remove. Adding card renewal to the list of activities that modify the LAD is fine; but I wouldn't want just the act of saving a record to trigger an update. Staff may have added a note or done a bulk change that has nothing to do with the patron having actually used the library.