Closed aaron-collier closed 2 years ago
A few notes on current behavior in the bulk updates (this came up recently in dlss-aaas Slack):
The second box behaves differently depending on how you get the list of druids:
Users have requested that the box auto-populate when pasting in a druid list. See https://github.com/sul-dlss/argo/issues/741
Alternatively, we could provide some other mechanism for retrieving existing tags for an arbitrary set of druids. If users could update multiple hitherto-unrelated druids at once this would greatly help them.
A prime use case for bulk tag updates is adding a tag to many objects that, prior to adding the tag the user is trying to add, have not been grouped together.
Another bit of current behavior that seems important: Argo overwrites the current tags with whatever is supplied in the bulk tag update. This seems to be why it's necessary to retrieve the current tags before making edits.
One way around retrieving current tags would be to provide bulk "add a tag" functionality where the tag is added to the current tags rather than replacing them.
@aaron-collier @andrewjbtw I think we ought to meet soon to discuss the requirements for this work.
@aaron-collier @andrewjbtw we should discuss this to unblock it. Moved to backlog.
Discussed with @aaron-collier and @andrewjbtw and we came up with the following:
We will use #2007 as an epic for replacing the tags bulk update with new bulk actions. It will wrap the following tickets:
I think we can consider this complete as we have import/export tags functionality in the bulk actions. We may finally want to retire the old way to update tags but that can be a separate ticket.
Part of #1914
Port the updating of tags from a bulk update to a bulk action
NOTE
s in code)