Export search to excel feature

[lazlo24]

As URD does not have a report feature, and in my mind it should not attempt to do so as it diverts away from what URD is, it would be truly excellent if there was an export search to excel feature

To do it at the moment it is required to do this

1. Using a search create a list of all of the items within the required scope.
2. In the search results window, set the columns you need in the report (Only need to do this once)
3. In the search results window, select all using 'Control A'
4. Copy grid values using 'Control Shift C'
5. Paste into excel.
Now you can play with your perfectly exported data.

It would be great if a search could be configured as an export output meachanism instead of screen display.
The output could specify the name of the excel spreadsheet, (or new), worksheet, including the R&C location to paste.

This would provide a truly excellent customisable method of providing a reporting mechanism for very little development and allows Excel to do what is does best and URD focusing on data handling.

[quant]

Originally posted by lazlo24
As URD does not have a report feature, and in my mind it should not attempt to do so as it diverts away from what URD is

I disagree, if by reporting you mean the functions on attributes (sums, etc....) that are standard in sql databases and are just not implemented in UR. They don't divert, in fact, I think they are sth basic ... see for example InfoQube
http://www.sqlnotes.net/drupal5/index.php?q=node/128

Originally posted by lazlo24

1. Using a search create a list of all of the items within the required scope.
2. In the search results window, set the columns you need in the report (Only need to do this once)
3. In the search results window, select all using 'Control A'
4. Copy grid values using 'Control Shift C'
5. Paste into excel.

1., 2. is one-time procedure. 3,4,5, is a few seconds combination of keypresses. I believe one could use one of the Macro softwares that would do most of the things you are suggesting.

I would much more prefer the calculation on attributes inside UR, and it's already on the Roadmap ...