Cadasta / cadasta-platform

[DEPRECATED] Main repository of the Cadasta platform. Technology to help communities document their land rights around the world.
https://demo.cadasta.org
GNU Affero General Public License v3.0
54 stars 81 forks source link

Enhancing Cadasta Outputs :: PDF Reports (Default and Custom) #1609

Open dpalomino opened 7 years ago

dpalomino commented 7 years ago

Problem Statement

The end goal of Cadasta is to simplify workflows and speed up land documentation processes. Printing PDF reports are one major way that partners can finalize the land documentation process. The needs can be broken up into three main stages:

(1) printing default reports from the platform, (2) printing custom-formatted reports (table views, different layouts, field orders, multiple parties per location, multiple locations per party) and (3) printing summary and filtered data views.

The map view, fields, and formatting will differ partner by partner.

Context/Use cases

Stage One (Default Reports) (1) Paper versions of the data collected:

(2) Report for community data validation (can be supported on the platform or through QGIS at the moment)

Stage Two (Custom-Formatting Report) (1) Report for formal recognition of the land.

Stage Three (Summary and Filtered views) (1) Report for individual data validation

(2) Report for harmonization of geometry boundaries

Requirements and User Stories

Stage One (Default Reports)

CURRENT WORKAROUNDS FOR THESE LATER STAGES ARE QGIS PRINT COMPOSER

Stage Two (Custom-Formatting Report)

Stage Three (Summary and Filtered views) These print capabilities adds complexity and sorting to the reports. Users have the ability to print out a map view of (1) one geometry, (2) multiple geometries associated with one party or (3) geometries contained in a defined area (selected with a drawing tool on the map).

Misc

Notes

It is challenging to build a GUI for custom reports. If we decide to do the printing in-app (which I recommend as I think reports are a key end product for many users), as a first step, we could use allow the ability to write HTML and python. Then later we can create a front end for that work. Alternatively, we could integrate with a third party tool for the complex front end interactions-- something like jsreports.net or webmerge.me.

For many partners, exact formatting (to apply for recognition of property rights to the local authorities) will be very important. Some partners will need exact formatting or they will not be able to use use the platform or have to add another step to the workflow, which could be quite cumbersome.

Fonts are also a key point, as reports may need to be generated with non-latin scripts.

As a nice to have, bulk printing of multiple reports would be useful for partners, so they design first the template to use and then print that report for all the selected locations.

The custom reports for more than one geometry could be better managed with QGIS plugin, but it's been included here for open discussion.

SteadyCadence commented 7 years ago

TO DO:

dpalomino commented 7 years ago

Tentatively doing the research (production of the DR) for the custom reports in Sprint 19.