Issue Details (XML | Word | Printable)

Key: BCMS-44
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Gregory Chomatas
Reporter: Gregory Chomatas
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
BetaCMS

Add the capability to export search results in betacms-webui in Excel

Created: 16/Apr/09 11:19 PM   Updated: 07/Oct/09 12:01 AM  Due: 29/Apr/09
Component/s: betacms-content-api
Affects Version/s: 2.1.0.CR1
Fix Version/s: 2.1.0.CR1

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: 0 minutes
Time Spent - 1 day, 8 hours
Time Spent: 1 day, 8 hours
Time Spent - 1 day, 8 hours


 Description  « Hide
The new unified API provided by apache poi 3.5beta will be used to export search results in betacms-webui module in Excel format.
The implementation will assume that the exported list contains content objects of the same content object type. The first object in the list will be used to determine the content object type for the whole list. If an object is found that has a different content object type it will be omitted.

The exported fields will be the title,description,subject,created,modified fields from content object profile as well as the root content object properties that are not complex. At a future version it will be possible for the user to select the desired field to export.

Multivalue Simple properties are supported. The values are exported in the same cell separated with new lines. The height of the row that contains multivalue fields is appropriately adjusted so that all values are visible.

The width of all columns is also automatically adjusted to present the full contents of each field.

It seems that there is a problem with fields that contain html / xml content. This should be investigated.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Gregory Chomatas added a comment - 07/Oct/09 12:01 AM
Excel export as described in the issue has been implemented. Fields that contain very big strings (i.e. html content) are not properly presented in mac os x word but open office is ok so we assume that is just a presentation issue of microsoft office. The cell content however seems to be properly copied in any case.