Hi Chris

First and foremost, output is determined by the report that is being run on the warehouse. This determines the columns being retrieved from the database and the parameters it supports. You can see this at https://code.google.com/p/indicia/sourc … e_list.xml

To show the last 'n' records you need to introduce a 'limit' clause in to the query. As far as I can see, this is not possible in this case as it is overriden by the pager code. I don't seem to be able to turn the pagers off. There might be a lingering bug if this is a use-case that has not been tested till now.

To show dates for the last n days needs a 'where' clause in the query. The report does not contain a date parameter but we might be able to supply one. The report_grid function can take a filters parameter which you could provide in the Form Structure.
Theoretically, I thought

@filters={"date_start":"2015-02-04"}

would select records from that one date or

@filters={"date_start":["2015-02-04","2015-02-05","2015-02-06"]}

would select from all those dates. I haven't got this to work in the course of trying to give you an answer here but this is an option I have never tried before so I might be doing it wrong. As for a date which is of the form "date > now - offset", I think that is beyond what we can do through the  Form Structure. Writing a custom report would be a solution.

Regarding the species name, you can see from the report that it is returned by the query snippet

CASE WHEN o.preferred_taxon=o.default_common_name then o.preferred_taxon ELSE o.preferred_taxon || COALESCE(' | ' || o.default_common_name, '') END

I.e if the preferred name is the same as the common name then you just get that; if there is no common name you just get the preferred name; if there is a preferred name and a common name then you get both.

Since this is your starting point, there are no built in options I can think of in the client code to manipulate this. Again a custom report would get you what you want. Alternatively, there could be another report in the library which is better suited to your needs.

The warehouse just provides the data needed and it is formatted by the code in the client_helpers library on your server, notably in the functions of the report_helper file.

Sorry this does not really include any easy answers. The way forward may depend on just what you want to achieve. You could
- go back to the simpler Report Grid form, perhaps with the library/occurrences/occurrences_list.xml report which incudes a common name column and date parameters.
- try to use a new filtering feature which is mentioned in passing at http://indicia-docs.readthedocs.org/en/ … orts.html. 
- create a custom report.

I'm going to have to leave it at that as I had so much else planned to do today.

Jim Bacon.

Hi Chris.

Believe me, it is little more obvious to you than me. In attempting to answer your question I was combining a bit of knowledge with trying to read the code. Some of the time I was using a debugger to inspect what was going on. I always struggle when I try to do something a bit different. I spent several hours on the answer which is why I had to quit in the end.

A run report button may imply that the report is needing some parameters to be supplied before it runs. If that is the case and the parameter values are known in advance then the configuration of the form allows you to supply those values so that the report can run without operator input. I'm ad-libbing a bit there and haven't done a test.

Custom reports cannot be installed without server access which we do not grant to anyone not employed by CEH. You would have to work with me to arrange that which, of course, I am happy to do.

Jim Bacon.

Good work.

If you look at the report you are using, which can be found in the code repository (now on Github https://github.com/Indicia-Team/warehou … /reports), you will see there is a <params> section which lists all the parameters including their names. Since there can be any number of reports and the parameter names are arbitrarily chosen by the report writer, the source is the most reliable place to obtain this information.

For info, I am on leave next week.

Jim Bacon.

Hi

You are mixing up two different things there. When you select 'Freeform report' you are choosing  a prebuilt form (https://github.com/Indicia-Team/client_ … report.php) which you can then configure to use any of the report files you want from the location mentioned previously.

Jim.

You would be looking at creating your own pre-built form I would say.
See http://indicia-docs.readthedocs.org/en/ … index.html

If the Freeform Report is nearly what you want then sub-classing it can be a very economical approach. Alternatively you could copy and modify it.

Jim Bacon

Thanks for the feedback. I've updated the documentation.

I don't know of a report that meets the criteria you have set out. I note that in many cases a user can sort tables by clicking on the column heading and that the site admin can alter the number of rows in output tables by a configuration setting called "Items per page".
I also have a recollection that you can pass a limit value through to a report request in the extraParams part of the options so that any report can be limited without needing to write that in to the report.

If you do write a custom report then send it to me and I can install it on the test warehouse.

Jim Bacon.

I've only ever seen and used the documented form of the report files so I'd have to recommend going with that. Your second example is also 2 years more recent than the former.

There is a very old schema diagram at https://code.google.com/p/indicia/wiki/DataModel. I am investigating whether I can generate something more up to date.

Given an occurrence_id of xxx there are two ways to get the associated taxon group. The long, slow way

SELECT tg.title 
FROM occurrences o
JOIN taxa_taxon_lists ttl ON ttl.id = o.taxa_taxon_list_id
JOIN taxa t ON t.id = ttl.taxon_id
JOIN taxon_groups tg ON tg.id = t.taxon_group_id
WHERE o.id = xxx

or using the cache

SELECT taxon_group 
FROM cache_occurrences 
WHERE id = xxx

Jim Bacon.