Settings and activity
116 results found
-
5 votes
Wes Osborn
shared this idea
·
-
32 votesWes Osborn
supported this idea
·
-
19 votesWes Osborn
supported this idea
·
An error occurred while saving the comment -
6 votesWes Osborn
shared this idea
·
-
87 votes
An error occurred while saving the comment Wes Osborn
commented
This would be very important for any hosted customers who don't have direct access to SQL to perform record set cleanup.
Wes Osborn
supported this idea
·
-
61 votesWes Osborn
supported this idea
·
-
6 votesWes Osborn
shared this idea
·
-
21 votesWes Osborn
shared this idea
·
-
39 votes
An error occurred while saving the comment Wes Osborn
commented
Although in an ideal world, I suppose it might be nice for the patron to have a preferred area for "each" branch. Just extending the single branch + preferred pickup location would be a huge help for us. In fact renaming this setting/option from preferred to default might better reflect that there can only be one per patron account.
Wes Osborn
shared this idea
·
-
15 votesWes Osborn
shared this idea
·
-
11 votesWes Osborn
shared this idea
·
-
14 votes
An error occurred while saving the comment Wes Osborn
commented
How would you propose that bibs that have multiple items with different material types be handled?
-
42 votes
An error occurred while saving the comment Wes Osborn
commented
Just throwing this out here in case anyone sees this and is unaware, but the 970 $h allows you to match on a specific template name rather than the rather unwieldy combination of other codes. I might like to see the length of the $h expanded from 10 characters to allow for more unique template names especially in a consortia environment where the first 3 or 4 characters of the template name are typically the library abbreviation.
-
63 votes
An error occurred while saving the comment Wes Osborn
commented
Saving the information in the browser cache could lead to catastrophic data loss. This renders the offline capabilities of Leap as unusable in many organizations.
Wes Osborn
supported this idea
·
-
32 votesWes Osborn
shared this idea
·
-
35 votesWes Osborn
shared this idea
·
This should also extend to the similar authority processing jobs. I didn't know those even existed and we have them back to 2009! We'll delete them through SQL, but it seems unfair not to extend this to other customers who don't have access to SQL.