Skip to content

B.C. Data Catalogue Development Wiki Roadmap

Jump to bottom
Greg Lawrance edited this page Nov 3, 2016 · 16 revisions

B.C. Data Catalogue Roadmap & Development Wiki

With our move to 'open development' this wiki intends (it is draft) to describe the broad objectives and longer-term roadmap of development efforts for the British Columbia Data Catalogue application. While individual issues are tracked in the relevant CKAN core and BCGOV specific repos and assigned to specific release milestones this wiki provides a way to learn about higher-level objectives associated with each release and what is on the horizon. This wiki also serves to document how we manage our repos and backlog - with respect to labeling, documenting releases, testing etc.

Backlog Pipeline

Issues move through the following states:

  • New Issues - contains issues not assigned to a spring backlog
  • In Progress - work is assigned
  • Code Complete - code has been created however it may not be deployed
  • Review / QA - code is implemented in our test instance for quality assurance
  • Verify - a final verification of the code Production can be made
  • Closed - ticket has been resolved and verification in production has been made

Versions / Milestones

1.3:

  • implement 2.3.4
  • update page header/footer
  • fix Google Analytics
  • investigate timing associated with less privileged roles
  • purge ghost users

1.3.1:

  • hotfix to deal with MapQuest maptiles change in service

1.4

  • confirm functions of OFI API will work for DWDS interface
  • upgrade to CKAN 2.5.2

1.5

  • include information on date of update and filesize for filestore resources
  • determine if issues with DataPusher/DataStore and latency remain
  • determine if timing of organization views and record updates remain for editors
  • investigate potential to merge record schema / use scheming

1.5.3

  • resolve issue with Google Analytics recording
  • resolve issue with mult-language availability - remove to prevent indexing by bots
  • minor change to UI for lineage and purpose
  • remove not used fields in apps and webservice schema
  • resolve unable to add new organizations
  • modify ini to support grid_view resource_view
  • resolve issue with editors removed from an organization continuing to receive email

1.6

  • implement integrated geographic data extraction into UI - OFI
  • implement Swagger based Console for API experimentation
  • create dashboard to show organizations an editor has access to
  • implement DCAT

1.7

  • map preview
  • update schema
  • move from sectors to subjects
  • include layernames in schema and UI

1.8

  • implement 3rd party authentication
  • establish high-availability
Clone this wiki locally