#220808: Batch/bulk export to ZIP archive is a must have feature! What about it, thanks to the views_bulk_operations.module? Help to the http://drupal.org/project/bulk_operations module author required first!

#220812: A "add to/delete from bookmark" action/operation to be called by other modules eg. with VBO: for easy creation of carts such as a "shopping cart" or any other kind of node cart, "basket", "panier", "caddy", "trolley" or whatsoever!

# Any other idea?

  • Feel free to reference some other operations that would benefit to the drupal project thanks to the great views_bulk_operations.module!

PS.: I'm not a developer... I don't promise anything nor garanty any development. I do *not* intend to press/stress/impose the people who already give so much to the community. Respect!

Comments

infojunkie’s picture

infojunkie
Location Vancouver
commented

Hello,

I don't understand what's reported or suggested here. Please elaborate on the purpose of this issue.

infojunkie’s picture

infojunkie
Location Vancouver
commented

I understood! Cheers :-)

Actions is a great mechanism for wrapping business logic in a user-callable package, that's what prompted building VBO in the first place. IMO, different modules should expose actions that encapsulate the functionality they provide. But I don't think VBO should be concerned with module-specific actions.

doc2@drupalfr.org’s picture

doc2@drupalfr.org commented

I'm just "referencing" the feature where it might give a great "colateral" benefit, for interested users to follow up the link to the main feature request issue of the specific module, so that they can "poll/vote" there if they like the idea (+1 for this feature) :) I wish you do!

In French, it *might* be called "dumping", although I'm not sure whether it is accepted in such drupal issues forums or not.

I should have renamed the topic to
- "Referencing Wanted Collateral OPERATION features" or
- "Referencing Wanted Contibuted modules OPERATION features", or
- with ACTIONS instead of OPERATIONS for each previous suggestion... (not sure if this is correct English)
Feel free to do so if you reply!

cornmuffin’s picture

cornmuffin commented
cornmuffin’s picture

cornmuffin commented

I think a compare operation would be very useful especially if integrated with CCK. This module could additionally be called subview or something similar. I imagine it would work something like this.

  1. Select multiple nodes for comparison from within view bulk operations.
  2. Select "Compare" or "Construct subview" from the operations dropdown.
  3. Select which CCK fields to display.
  4. If multiple view styles available select one. (i.e. Node in columns, rows, or in a list style view).
  5. Select how the nodes should be sorted based on their field values.
  6. Submit!

I am using drupal to track sample information and analysis and this woudl be useful to compare data for multiple samples. I can this type of functionality having widespread use in E-commerce sites where for example you can often compare vehicles, spa packages, health care plans etc..

infojunkie’s picture

infojunkie
Location Vancouver
commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

I'll close this since the thread seems to have dried.

asak’s picture

asak commented

hey cornmuffin - have you managed a way to get what you've described done? ;)

That is preciesly what i need now + a print botton at the end (which is the easy part...)

I want users to gather info from the database, construct it as they wish (selecting view type and excluding/manipulating fields), give it some basic theming (predefined templates would be cool) and export it to print/pdf. sounds like what you were talking about.

Thanks !