Views bulk operation

Created on 25 June 2024, over 1 year ago

Problem/Motivation

I would like to summarize many existing nodes.

Workflow:
1) Setup interpolation on the field
2) Run interpolation on historic nodes in bulk by using VBO β†’ module, which allows to filter and choose a lot of nodes with views.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡±πŸ‡ΉLithuania mindaugasd

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mindaugasd
  • πŸ‡±πŸ‡ΉLithuania mindaugasd

    In my case filling a single field on many nodes (no chaining).

  • πŸ‡±πŸ‡ΉLithuania mindaugasd

    Mostly I am looking forward to use this feature with AI β†’ module automator's. In the meantime will do it programatically: db query, a batch and AI module's abstraction API.

  • πŸ‡±πŸ‡ΉLithuania mindaugasd

    Renamed "interpolator" with "automator" in description.

  • πŸ‡¬πŸ‡§United Kingdom yautja_cetanu

    Yes very good idea. This is similar to what Martin says of there being UI triggers so similar to widgets except in this case the UI trigger is a bulk operation

  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    We are doing some issue management housekeeping and adding/removing components.

    We are removing the "Code" component and want people to categorize issues with the best module/submodule component.

    Moving this issue to "...to be triaged" as I'm not sure where the best place is.

    If we have a new project to move this to, we can optionally do that as a secondary step.

    See πŸ“Œ Update AI module project components Active for more details.

  • πŸ‡©πŸ‡ͺGermany marcus_johansson

    So this is how it should work to make sense.

    Add a new processor called "Views Bulk Operation".
    When an automator has this processor, it will becomes a deriative action available for VBO.
    That Automator will ever only run on VBO action and an entity selected.
    Add a possibility for processors to have subforms.
    Let the user decide per field if it always overwrites the value or only sets if the value is set.

Production build 0.71.5 2024