Anne S.

My feedback

17 results found

  1. 241 votes
    How important is this to you?

    Hi all, we're working on analyzing the request for batch item description updates and would love your input to make sure our solution fits your needs.

    I would like to propose the following:

    The "Rebuild Physical item description" job currently allows auto-generating a description for a set of items (based on enum/chron data) - this option will be kept as is, but the job would allow selection to either auto-generate the description (existing) or enter a description value as free text (meaning all items in the set would get the same description). The free text option would also support updating the field with an empty value as exists in other jobs.


    1. What are some examples of descriptions that would be relevant across an entire set of items?

    2. As discussed in previous comments, changing the description of an item (manually or via job) causes the pending requests for that…

    An error occurred while saving the comment
    Anne S. commented  · 

    Many of our records migrated with just a volume number in the description field. These are mostly analyzed series monographic records where the volume number is already in the call number field so it's redundant. It would be nice to be able to delete the volume number from the description field for all volumes in the series by set & job. I did discover a work around after I had voted to support this idea though and that was to use the "Rebuild item description" job which cleared the description field (provided there was no other enum/chron data.)

    Anne S. supported this idea  · 
  2. 7 votes
    How important is this to you?
    Anne S. supported this idea  · 
  3. 76 votes
    How important is this to you?
    Anne S. supported this idea  · 
  4. 50 votes
    How important is this to you?
    Anne S. supported this idea  · 
  5. 55 votes
    How important is this to you?
    Anne S. supported this idea  · 
  6. 56 votes
    How important is this to you?
    Anne S. supported this idea  · 
  7. 2 votes
    How important is this to you?
    Anne S. shared this idea  · 
  8. 74 votes
    How important is this to you?
    Anne S. supported this idea  · 
  9. 108 votes
    How important is this to you?
    Anne S. supported this idea  · 
  10. 3 votes
    0 comments  ·  Alma » Analytics  ·  Admin →
    How important is this to you?
    Anne S. supported this idea  · 
    Anne S. shared this idea  · 
  11. 58 votes
    How important is this to you?
    Anne S. supported this idea  · 
    An error occurred while saving the comment
    Anne S. commented  · 

    Agree with Betsy R. it would be ideal to have all the enum/chron fields on one tab. Some of the other fields on the first tab such as Inventory & Retention information are rarely used and if you had to have a second tab that would be a better place to put those so there is room enough for all the enum/chron fields on the first tab.

  12. 59 votes
    How important is this to you?
    Anne S. supported this idea  · 
  13. 73 votes
    How important is this to you?
    Anne S. supported this idea  · 
  14. 25 votes
    How important is this to you?
    Anne S. supported this idea  · 
  15. 22 votes
    How important is this to you?
    Anne S. supported this idea  · 
  16. 99 votes
    How important is this to you?
    Anne S. supported this idea  · 
  17. 142 votes
    How important is this to you?
    Anne S. supported this idea  · 

Feedback and Knowledge Base