-
Notifications
You must be signed in to change notification settings - Fork 23
B.C. Data Catalogue Development Wiki Roadmap
Mathew Brown edited this page Jun 22, 2017
·
16 revisions
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.
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
January 1, 2015
- Retired the Geographic Data Discovery Service. All the metadata previously found in that service is now in the B.C. Data Catalogue.
- added a permalink feature at the top of each package to easily reference the immutable Unique Identifier.
- made the data lineage field visible.
- removed the redundant Database ObjectName field from the Additional Information section.
- removed the ISO standard classification tag from the tabular dataset package types.
- implement 2.3.4
- update page header/footer
- fix Google Analytics
- investigate timing associated with less privileged roles
- purge ghost users
- hotfix to deal with MapQuest maptiles change in service
- confirm functions of OFI API will work for DWDS interface
- upgrade to CKAN 2.5.2
- 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
- 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
- fixed recline map background
- fixed problems with OFI record creation and deletion
- 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
- made it easier for editors to create geographic records by allowing draft records to be saved without any resources. These draft records are now viewable to all branch editors. Once BCGW resources have been configured for downloaded they can be added.
- general cleanup of the UI for geographic records
- markdown now works on ‘Data Quality’, ‘lineage’ and ‘Purpose’ fields
- map preview update
- update schema to include additional elements
- move from sectors to subjects taxonomy
- include cartographic layernames in schema and UI
- implement DCAT
- implement 3rd party authentication
- establish high-availability