Settings and activity
10 results found
-
37 votes
Philip McNulty
supported this idea
·
-
10 votes
An error occurred while saving the comment
Philip McNulty
supported this idea
·
-
9 votes
Philip McNulty
supported this idea
·
-
23 votes
The product team will review this idea for consideration for a future release.
Philip McNulty
supported this idea
·
-
8 votes
The product team will review this idea for consideration for a future release.
Philip McNulty
supported this idea
·
-
10 votes
The product team will review this idea for consideration for a future release.
Philip McNulty
supported this idea
·
-
17 votes
Philip McNulty
supported this idea
·
-
15 votes
Philip McNulty
supported this idea
·
-
23 votes
An error occurred while saving the comment
Philip McNulty
commented
Having a sound foundation for our patron data is important in a variety of our functions, from reporting, to 3rd party integrations, to patron communications. Sierra's weirdly flexible patron input forms require strong back-end tools to make sure this data is correct, and this idea will improve those tools.
Philip McNulty
supported this idea
·
-
147 votes
An error occurred while saving the comment
Philip McNulty
commented
We would need to see this idea implemented before we adopt LX Starter
Philip McNulty
supported this idea
·
Is there a better approach that does not interfere with a patron's ability to manage holds? A more comprehensive locker functionality could recognize when items were committed to and released from lockers, and not send patron hold available notices until committed, and not make items available for holds filling etc until uncommitted.