Skip to content

Add "skipped" count on bulk action results page #4900

@estanfor

Description

@estanfor

In addition to Total/Success/Failed, include a "Skipped" count of the items where the action could not be performed because the item did not fit the criteria or the action would have no impact.

Actions:

  • "Open versions" action: items that were already open
  • "Close versions" action: items that were already closed
  • "Update content type" action: items with no resources of the resource type specified in the bulk action

There's also a set of actions that update descriptive or administrative metadata. Currently, in at least one case ("Upload descriptive metadata"), items where the new metadata values are identical to the old ones are getting counted as "failed", and in other cases ("Apply APO defaults") they're getting counted as "successful". If we are not checking for no-change changes, I think it's OK to keep counting these items as "successful". Otherwise:

  • Upload descriptive metadata: "skipped" if new metadata is identical to old metadata
  • Update rights: "skipped" if new metadata is identical to old metadata
  • Update licenses and rights statements: "skipped" if new metadata is identical to old metadata
  • Update governing APO: "skipped" if new APO is identical to old APO
  • Apply APO defaults: "skipped" if new metadata is identical to old metadata
  • Update source ID: "skipped" if new metadata is identical to old metadata
  • Update collection type: "skipped" if new collection is identical to old collection
  • Import structural metadata: "skipped" if new metadata is identical to old metadata
  • Import tags: "skipped" if new metadata is identical to old metadata
  • Add workflow: "skipped" if workflow is already present

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions