Skip to content
This repository has been archived by the owner on Nov 3, 2022. It is now read-only.

Year filtering behaviour for document linking in aquariam.js #113

Open
brew opened this issue Sep 6, 2017 · 0 comments
Open

Year filtering behaviour for document linking in aquariam.js #113

brew opened this issue Sep 6, 2017 · 0 comments
Milestone

Comments

@brew
Copy link
Collaborator

brew commented Sep 6, 2017

The explorer app requests data from the data-client which is cached as countries.json. This countries list includes data about document availability for specified time periods, e.g.: '2015', '2016', 'December 2016'.

Additional information is added to the country/question entry about document links within Google Drive (driveId and/or groupParentId), that provides the necessary data to the tracker app to build links from a country's availability page to documents within Google Drive. This is achieved by a process of discovering documents and directories within Google Drive, and matching them with availability entries from the Indaba API.

At some point, these year groupings were changed from 'YYYY' to 'Month YYYY' format, to enable multiple releases within a given year.

A starting boundary year exists (hard-coded as '2016') that starts this document linking behaviour from '2016', and all date groupings that match the 'Month YYYY' format.

There is a date displayed on the Availability page describing when the last API update occurred. It is defined manually as an env var, TRACKER_LAST_UPDATE.

brew added a commit that referenced this issue Sep 26, 2017
Linking directly to gdrive documents within their year folders is
problematic given we haven't got a definitive fiscal year property from
the API. Instead we'll now link to the top level report type directory
for the country in question. e.g. Argentina/Year-End Report.

Dots will be linked if a directory for the report type exists on the
gdrive.

Related to #113.
@pwalsh pwalsh added this to the Backlog milestone Jan 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants