Settings and activity
83 results found
-
17 votes
Kimberly Allen supported this idea ·
-
10 votes
Kimberly Allen supported this idea ·
-
12 votes
Kimberly Allen supported this idea ·
-
12 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Kimberly Allen supported this idea ·
-
6 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen supported this idea ·
-
10 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen supported this idea ·
-
7 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen supported this idea ·
-
12 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen supported this idea ·
-
5 votes
Kimberly Allen supported this idea ·
-
6 votes
Kimberly Allen supported this idea ·
-
2 votes
Kimberly Allen supported this idea ·
-
24 votes
Kimberly Allen supported this idea ·
An error occurred while saving the comment -
29 votes
Kimberly Allen supported this idea ·
-
17 votes
Kimberly Allen supported this idea ·
-
6 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Kimberly Allen commented
Our database management group has a number of cleanup projects going, especially with gov docs and serials. Being able to add multiple items to a review file at one time would be handy.
Kimberly Allen supported this idea ·
-
5 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Kimberly Allen commented
Definitely a yes. A history is supposed to provide sufficient information to track down who did what. The current implementation does not.
Kimberly Allen supported this idea ·
-
10 votes
Kimberly Allen supported this idea ·
-
16 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Kimberly Allen commented
This should be an Opt In|Out or have a way to limit the depth of the histories. With larger libraries this could have data storage implications. My library has more than 7 million volumes and there are a number of reasons why an item might be edited multiple times over its life time. (Transfers, call number updates, local notes...)
-
10 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Kimberly Allen commented
Agree with all of the above. We have several collections, which could benefit from this.
Kimberly Allen supported this idea ·
-
10 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen supported this idea ·
If you are an academic with multiple libraries across campus, this is a must have to avoid very annoyed patrons.