Settings and activity
13 results found
-
9 votes
Alisia Revitt
supported this idea
·
-
6 votes
Alisia Revitt
supported this idea
·
-
5 votes
Alisia Revitt
supported this idea
·
-
5 votes
Alisia Revitt
supported this idea
·
-
6 votes
Alisia Revitt
supported this idea
·
-
10 votes
Alisia Revitt
supported this idea
·
-
12 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.
Alisia Revitt
supported this idea
·
-
13 votes
Alisia Revitt
supported this idea
·
-
4 votes
Alisia Revitt
supported this idea
·
-
8 votes
Alisia Revitt
supported this idea
·
-
11 votes
Alisia Revitt
supported this idea
·
-
4 votes
Alisia Revitt
supported this idea
·
-
155 votes
Alisia Revitt
supported this idea
·
An error occurred while saving the comment
The ENTIRE REASON for us wanting to move to LX starter is to deal with the spam bans. Without this change it is just trading one bad situation for another.