Skip to content

Releases: socialsensingbot/frontend

Release 2.6

04 May 18:31
Compare
Choose a tag to compare

What's Changed

Support for historical scroll bars.
Added API : https://socialsensing.readme.io/reference
Map window now 7 days not 4 days.

Full Changelog: 2.5...2.6

2.5

04 May 18:28
Compare
Choose a tag to compare
2.5

What's Changed

Full Changelog: 2.3.2...2.5

Release 2.4.4

04 Feb 14:02
ae93e85
Compare
Choose a tag to compare
Merge pull request #427 from socialsensingbot/release/2.4.4

Release/2.4.4

Release 2.4.3

04 Feb 14:01
ae93e85
Compare
Choose a tag to compare
Merge pull request #427 from socialsensingbot/release/2.4.4

Release/2.4.4

Release 2.4.2

08 Dec 13:55
95998f5
Compare
Choose a tag to compare

Release 2.4 bugfixes

Release 2.4.1

08 Dec 13:55
93034eb
Compare
Choose a tag to compare

Release 2.4 bugfixes.

Release 2.4

25 Nov 18:41
2ec8851
Compare
Choose a tag to compare

App Changes

  • Date range chooser in analytics to choose what time period to graph data over - mainly useful for the hourly queries.
  • Day/Hour choice in analytics.
  • Filter by Region uses the title not the id of a region when autocompleting.
  • NUTS1, ISO Countries and UK Countries are now supported as region types.
  • Retrospective tweets can now be displayed previously determined by the existance of html field - no longer required. NB: if the profile picture is broken nothing is shown.
  • Lots of small changes to help support retrospective data display made to support the demo environment.
  • Filter by Region gets it's filter list from ref_geo_regions now. ref_geo_regions is the authoritative source of region data from now onwards.
  • The countries available in the 'countries to download' dropdown are now configured via the preference 'countryDownloadRegionType' the regions in that region type are presumed to be countries and are made available in the dropdown.

Server (Lamda) Changes

  • The server call for the new stats calculation uses the same REST request, the old one is now .../complex-stats ready for the addition of more complex criteria.
  • All data from the server over a specified limit is now GZIP'ed.
  • Geography is loaded one region at a time as the size of the data broken API Gateway's limit.

Database Changes

  • Three different stored procedures are called, one every 5 mins, one every hour (approx) and one every day (approx). They update the various materialized view tables so that we have quick current data, hourly 4 day window updates (for Twitter compliance) and daily complete refreshes (for new regions being added). To avoid locks on tables, these are called sequentially from a single even.
  • Event Scheduling is also now turned on (see above)
  • mat_view_regions is now calculated using geographic function to compare the location in live_text with the boundary in ref_geo_regions
  • mat_view_days and mat_view_hours are additional tables which help query performance they contain all days and all hours respectively for which there exists data.
  • mat_view_timeseries_date and mat_view_timeseries_hour are now periodically updated to contain data to be used by the timeseries analytics graphs.
  • Scheduled task also rebuilds the tables with OPTIMIZE TABLE every day
  • Internal_debug table stores the debug logging from stored procedures
  • The materialized views for the analytics timeseries now have a prefix in source_text which is the MD5 hash of source + ":" + hazard + ":" + region, boolean searches are now prefixed with something like +(5675675675de65ed76e cf45f765765f6f567f) which means that the text search should also match one of the hashes. This effectively creates a combined free text and field index 😄
  • The possible enumerated and boolean criteria (which I refer to as the common criteria) are listed in the table mat_view_map_criteria. This is to support faster exceedance calculations.
  • The table mat_data_days has been added, this contains the total number of days for the common criteria that have data. Used for exceedance.
  • The table mat_view_text count contains the daily totals for the common criteria. Also used for exceedance.
  • The most common use case of exceedance has been optimised
  • Unused tables deleted.
  • Virtual region types now supported table ref_geo_virtual_regions allows the mapping of a virtual region_type to existing regions with varying region_types (used for CSV country download). The mapping is exposed in the view view_geo_regions_with_virtual used to create the mat_view_regions table and as metadata for the app in general.

Test Changes

  • All the tests have been reworked for a new end date (16th Sept) which has a little more data than the previous one.
  • All tests have been fixed and several timing issues (especially in analytics) have been fixed.
  • New test 13_url_state_through_components_spec.js added to deal with issues moving between the application parts and maintaining/shedding state as required.

Issues resolved

  • Region selection box on Analytics #310
  • Empty Drop Downs #311
  • Graph Menu #309
  • Loading page #306
  • PWS - 3.3 Add export function to save tweet data to local file. #248
  • Create test for the EOC value, selected county and layer being passed between parts of the app. #337
  • PWS - 3.2a - Display in local time t #251
  • PWS - 3.3 Add export function to save tweet data to local file. #248

Release 2.3.3

11 Oct 12:05
3ce2021
Compare
Choose a tag to compare

What's Changed

  • Better caching of stats and recent tweets. Also synchroized their end… by @neilellis in #341

Full Changelog: 2.3.1...2.3.3-ammended

Release 2.3.2

01 Oct 16:17
f9bcb35
Compare
Choose a tag to compare

Bugfixes

Release 2.3.1

29 Sep 14:01
33b0840
Compare
Choose a tag to compare

Bugfixes for 2.3