Betsy R.
My feedback
13 results found
-
32 votes
Betsy R. supported this idea ·
An error occurred while saving the comment -
39 votes
Betsy R. supported this idea ·
An error occurred while saving the comment Betsy R. commented
Us too!
-
222 votes
Betsy R. supported this idea ·
-
24 votes
Adi Alter responded
Submitted by Ex Libris PM on behalf of our customers
Betsy R. supported this idea ·
-
35 votes
Betsy R. supported this idea ·
-
10 votes
Betsy R. supported this idea ·
-
58 votes
Betsy R. supported this idea ·
An error occurred while saving the comment Betsy R. commented
Please make ALL Enum Chron fields available on the first screen. Toggling back and forth is a pain and just begs for errors. Worse, when receiving a new issue, you have to actually save and leave the item record, then relaunch the item editor in order to finish entering the complete data. Very time inefficient!
-
115 votes
Betsy R. supported this idea ·
-
94 votes
Betsy R. supported this idea ·
-
78 votes
Betsy R. supported this idea ·
-
197 votes
Betsy R. supported this idea ·
-
96 votes
Betsy R. supported this idea ·
-
14 votes
An error occurred while saving the comment Betsy R. commented
Yes!! This would be very good for running lists for weeding, etc., where I want to pull a series of reports limited by location or call number range. Please add this!
Yes!!!! My computer programming instructor would have failed me if I had written code that allowed the deletion of data that was still in use by another process without so much as an error message or request for confirmation. And that request needs to be specific, i.e. "This set is referenced xyz job [or even "a job"]. Are you sure you want to delete?" Generic "Are you sure you want to delete this set" messages that appear for all deletion requests are completely useless. Generic "are you sure you want to delete this set" messages that only come up when there is a conflict, but don't tell you what the conflict is are only slightly better than useless.