Settings and activity
41 results found
-
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.
Joyce Peter
supported this idea
·
-
7 votesJoyce Peter
supported this idea
·
-
10 votesJoyce Peter
supported this idea
·
-
62 votesJoyce Peter
supported this idea
·
-
57 votesJoyce Peter
supported this idea
·
-
46 votesJoyce Peter
supported this idea
·
-
4 votesJoyce Peter
shared this idea
·
-
46 votesJoyce Peter
supported this idea
·
-
9 votesJoyce Peter
supported this idea
·
-
15 votesJoyce Peter
shared this idea
·
-
24 votesJoyce Peter
supported this idea
·
-
26 votesJoyce Peter
supported this idea
·
An error occurred while saving the comment -
20 votesJoyce Peter
supported this idea
·
-
14 votesJoyce Peter
supported this idea
·
-
32 votesJoyce Peter
supported this idea
·
-
39 votesJoyce Peter
supported this idea
·
-
37 votesJoyce Peter
supported this idea
·
-
17 votesJoyce Peter
supported this idea
·
-
42 votesJoyce Peter
supported this idea
·
-
55 votesJoyce Peter
supported this idea
·
An error occurred while saving the comment Joyce Peter
commented
One of our former circ staff members used bulk change to erase the collection code on around 1,500 item records and that was not an easy thing to clean up as it involved dozens of collections. One of the reference staff has changed the ownership field when using bulk change-- and done it more than once even after receiving an admonition from me. I have more examples of unfortunate batch changes, but the bottom line is that if the catalogers or sys admin doesn't want staff to have the ability the modify a single item record-- they certainly shouldn't be allowed to modify thousands through a backdoor.
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.