Settings and activity
11 results found
-
13 votes
An error occurred while saving the comment 
Cameron C
shared this idea
·
-
117 votes
An error occurred while saving the comment Cameron C
commented
This would be nice as well for notifying staff who are using the Item Record set bulk change feature to withdraw swathes of items, potentially with suspended or active bib-level holds that now cannot be fulfilled (and which the system does not notify staff of until deletion of the records, after they've been physically deaccessioned).
While supervisory staff do get a report indicating which holds were unfulfilled in a 30-day period due to withdrawn titles, it would be nice to be proactive in either replacing such items that have holds (or retaining the copy we have) versus having to reactively replace with a delay.
*All of this assuming people aren't using weeding-type record sets to create 'never weed' lists or flag last copies*
Cameron C
supported this idea
·
-
4 votesCameron C
shared this idea
·
-
34 votes
An error occurred while saving the comment Cameron C
commented
We learned recently that there's a workaround to this - through the power of SQL and a neat trick to get SQL to run in the Weeding Template criteria: the magic of the ADHOC!
The following is a very basic example of how you could have a weeding template filter by a relative last check in date (we also found out recently that, despite the name, last circ date includes things like inventory check-in or item record modification and was less useful as a parameter for weeding):
ADHOC="SELECT ItemRecordID FROM CircItemRecords WHERE AssignedCollectionID = int AND CheckInDate < DATEADD(year, -int, CURRENT_TIMESTAMP)"
The above example has to go into the inclusion criteria field with the ADHOC=" " in order to work, and the int values would correspond with your given collection and number of years from the current date you wanted to include.
-
30 votesCameron C
supported this idea
·
-
3 votesCameron C
shared this idea
·
-
14 votesCameron C
supported this idea
·
-
2 votesCameron C
shared this idea
·
-
95 votes
An error occurred while saving the comment Cameron C
commented
I was surprised to learn there was such a blip in status changes not triggering holds... we only noticed it with a recent spate of such 'not supplied' holds. I did not see anything in the IUG forum about this, so I'm glad to see some others have experienced it and are bringing awareness to it!
Cameron C
supported this idea
·
-
4 votesCameron C
shared this idea
·
-
13 votesCameron C
supported this idea
·
A thought came up recently as to a way this could work--given my being a tech novitiate, I have no clue whether this would be easier or harder than the original conception:
What if, as with the weeding record sets when there are item filters in the template, there were exclamation marks next to each MARC field that indicated there were deficiencies or issues with the data?