- Posts: 24
- Thank you received: 3
CT - Batch Update Items - Implement By Title
10 years 6 months ago - 10 years 6 months ago #60
by Mitake
CT - Batch Update Items - Implement By Title was created by Mitake
Finish implementing the By Title tab in Batch update items. Allow libraries to define actions for items to keep on a title by title basis (e.g. how many copies to keep).
Last edit: 10 years 6 months ago by Mitake. Reason: Attach mockup
Please Log in to join the conversation.
10 years 1 month ago #85
by Mitake
Replied by Mitake on topic CT - Batch Update Items - Implement By Title
This is for adding another tab to the Batch Update Items window - allowing users to process items by title based criteria instead of just item level criteria. For example, currently you can say something like all items that were made lost more than 2 years ago should now be withdrawn - the criteria is based on the information specific to the item. This functionality would allow you to say we want to keep 2 items for titles that meet this criteria.
Keystone knows that this is desired functionality. What we don't know is where it falls on the priority scale for our customers.
Keystone knows that this is desired functionality. What we don't know is where it falls on the priority scale for our customers.
Please Log in to join the conversation.
- joel.henderson
- Offline
- RANK2
Less
More
- Posts: 25
- Thank you received: 1
10 years 1 month ago #88
by joel.henderson
Replied by joel.henderson on topic CT - Batch Update Items - Implement By Title
I talked with our collection coordinator, and she says what would be really useful is if she could import a query not based on a range of book numbers but instead based on a subject. For example, she could import a query of all Westerns in our digital collection, then use the batch update options currently available from there. The feature as it stands now is very useful she says, but being able to import a subject query would be more of a priority than implementation by title.
Please Log in to join the conversation.
Time to create page: 0.046 seconds