Settings and activity
134 results found
-
9 votes
Susan Millwater
supported this idea
·
-
5 votesSusan Millwater
supported this idea
·
-
12 votes
An error occurred while saving the comment Susan Millwater
shared this idea
·
-
59 votesSusan Millwater
supported this idea
·
-
18 votesSusan Millwater
supported this idea
·
-
9 votesSusan Millwater
supported this idea
·
-
30 votesSusan Millwater
supported this idea
·
-
26 votesSusan Millwater
supported this idea
·
-
16 votesSusan Millwater
supported this idea
·
-
13 votesSusan Millwater
supported this idea
·
-
22 votesSusan Millwater
supported this idea
·
-
14 votesSusan Millwater
supported this idea
·
-
11 votesSusan Millwater
supported this idea
·
-
11 votesSusan Millwater
supported this idea
·
-
32 votesSusan Millwater
supported this idea
·
-
4 votesSusan Millwater
supported this idea
·
-
17 votesSusan Millwater
supported this idea
·
-
11 votesSusan Millwater
supported this idea
·
-
32 votes
An error occurred while saving the comment Susan Millwater
commented
This continues to happen when staff are updating a patron registration using the staff client. I think it happens when they are updating the birthdate and inadvertently click on the checkbox for the registration date which clears the date. If you save the changes, the registration date will then be set to NULL value. You can also clear the field in Leap, but this is not as easy to do accidentally.
Can the checkbox be removed that is next to the registration date in the patron registration? Can the registration date be required (staff client, Leap, API, etc.)?
Susan Millwater
supported this idea
·
Susan Millwater
shared this idea
·
-
32 votesSusan Millwater
supported this idea
·
SIP should handle foreign characters (diacritics) correctly. When a patron's name or an item's title has a diacritic then it throws an error. For some vendors, it breaks the application and prevents customers from logging in and/or accessing their checked out or held items.