Settings and activity
84 results found
-
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
·
-
9 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen
supported this idea
·
-
15 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen
supported this idea
·
-
7 votes
Kimberly Allen
supported this idea
·
-
16 votes
Kimberly Allen
supported this idea
·
-
4 votes
Kimberly Allen
supported this idea
·
-
42 votes
Kimberly Allen
supported this idea
·
-
34 votes
Kimberly Allen
supported this idea
·
-
8 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment
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
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
·
-
15 votes
Kimberly Allen
supported this idea
·
-
25 votes
This enhancement is planned for Sierra 6.6.
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...)
-
11 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
·
-
16 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen
supported this idea
·
-
31 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen
supported this idea
·
-
15 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
The product team will review this idea for consideration for a future release.
Kimberly Allen
supported this idea
·
-
8 votes
The product team will review this idea for consideration for a future release.
Kimberly Allen
supported this idea
·
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.