1

I have a content type for manuals that has a vocabulary for "Model Year" and another for "Model Name" with a file upload that is for owners manuals for the specific Model Name + Model Year.

I want to push this content type into a view to provide a table where the years are columns and the model names are rows with the resultant cells having the download link.

---------------------------------------
        | 2016     |  2015   |  2014   |
---------------------------------------
Model 1 | download |download |download |
---------------------------------------
Model 2 | download |download |download |
---------------------------------------
Model 3 | download |download |download |

I've been wrestling with the views all night and the table. I can't seem to get close to what I want. I've tried making sure all the taxonomy terms were added as a relationship.

If I use fields and bring the content of the year and the model forward I can display them, but not as columns, only rows and not as rolled up results in a year - so 10 2016 column instead of one 2016 columns with 10 rows.

I've tried the Views Flipped Table module, but that didn't solved the problem.

1

The Forena module can be used for this type of reporting. More specifically by using its facility to create a Display of a table in crosstab format.

A crosstab table is a table with a special layout. It is formatted as a grid, with:

  • the rows representing one or more (combinations of) facts, such as countries or regions, names of persons (or users) like employees / salespeople (or user IDs / user names), names of Models, etc.
  • the columns representing one or more other facts, such as periods (months of a year, years, etc), available types/flavors of something (like types of errors), etc.
  • the intersections of rows and columns containing the actual information (data), such as summarized information (counts of something), timestamps, etc. and which might (optionally) include a hyperlink to a drill-down report.

Below is a sample of such crosstab report (including drilldown links also, i.e. the numbers in red in it):

enter image description here

Refer to my comment in the Forena issue queue for more details about the above screenshot. And/or have a look at the video about How to generate crosstab reports with graphs (Forena also supports charting of those data, a typical related requirement ...).

In this specific case, if I was to create such crosstab table, for "the resultant cells having the download link" I'd create a hyperlink which would actually mention the number of manuals corresponding to the selected combination of Model Name and Model Year. And by following such link, you'd get a drilldown report with links to the actual manuals.

Disclosure: I'm a co-maintainer of this module,
I hope this does not violate the site's policy on self-promotion.

0

It's simple.

In your content type (lets pretend its called Cars) add various (1 value) download fields, like this

  • download 2016
  • download 2015
  • download 2014

Add nodes/pages to your Cars content type

  • Ford
  • Ferarri
  • Honda

Upload the corresponding files to each download field.

Add all the fields to your view. For field Label you delete the download part and just leave the year.

No need to use taxonomy terms here.

  • There is a need for the taxonomy terms for relationships for other views that are built with the same content type, at least that's the path that's already been plowed. You could provide a solution that doesn't require the use of the terms, but the content type itself needs the terms. – Erik Hanson Nov 10 '15 at 23:51
  • Your current system is flawed. "Model Name" should not be a taxonomy vocabulary. If you want to link or "File Under" other stuff to the respective model name, you should use Entity Reference. You need download and install the Entity Reference module.. – No Sssweat Nov 11 '15 at 0:36
  • If you want years to be a taxonomy term. Then you need to create a Download content type and create new content (nodes) for each download file and do a tax term reference (which is way overkill) when you can do it my way. – No Sssweat Nov 11 '15 at 0:38
  • The Model Name vocabulary and terms is used in other content types throughout the site. The system may be flawed if this need were the only use case, but it's a taxonomy in place that serves other purposes and does it's job well. This is a "Manual" content type, specifically used to house manuals for download, segmenting those by years and models makes a whole lot of sense to me. I do have other stuff filed under years, and I have other stuff filed under Model Name. – Erik Hanson Nov 11 '15 at 2:59
  • I'll try to build the table using your current system. I don't know if it's even possible. – No Sssweat Nov 11 '15 at 3:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.