Bug 772110 - CSV export has incorrect headers
Summary: CSV export has incorrect headers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-06 02:05 UTC by Dana Mison
Modified: 2014-08-04 22:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-02 00:26:51 UTC


Attachments (Terms of Use)

Description Dana Mison 2012-01-06 02:05:21 UTC
/CustomSearchTopicList.xhtml


/CustomSearchTopicList.xhtml

The columns in the CVS export do not match the data.  Some of them I didn't see any data in any of the samples I looked at so I don't know if they are correct, although in some cases the heading is one that is clearly a different column.

To avoid issues with commas in fields, the fields that could have commas should be enclosed in quotes.  Most spreadsheet apps give you the option to ignore delimiters in quoted strings.

Also the fields that contain multiple entries currently have [] around each entry.  This is harder to parse than simply using a different delimiter.  Something like | could be more useful.

What the columns are labelled:
Topic ID,
Topic Title,
Topic Text,
Topic URL,
Assigned Writer,
Audiences,
Book,
Common Names,
Concerns,
Engineering Priority,
IA Priority,
Nav Priority,
PM Priority,
Release,
SME Priority,
SME Reviewers,
Special Tags,
Technologies,
Topic Lifecycle,
Topic Types,
Writer Priority

What they appear to be:
Topic ID,
Topic Title,
Topic Text,
Topic URL,
,
Concerns,
Technologies,
Topic Types,
Topic Lifecycle,
,
,
,
IA Priority,
,
,
Assigned Writer,
,
,
Release,
,
Common Names

Comment 1 Matthew Casperson 2012-01-31 03:14:06 UTC
Fixed in 201201131-1311

Columns now line up, and multiple tags are listed as id: name separated by commas.


Note You need to log in before you can comment on or make changes to this bug.