-
Notifications
You must be signed in to change notification settings - Fork 23
ChangeLog
Mike Dunham-Wilkie edited this page Feb 25, 2019
·
35 revisions
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
| Table Of Contents |
|---|
| Unreleased |
| Released |
- Reverted this as it had unintended consequences: Bug: Cannot add OFI resources in the add dataset workflow
- Catalogue Administrators can report on web analytics using Snowplow Analytics provided by GDX
- Additional Download Audience choices to the “Who can download this dataset”
- Add additional audience choices to the “Who can view this Data”
- Better checking for chrome browser support.
- Permalink Button Appears to do Nothing
- Amend incompatible browser error message
- ‘Resource Storage Location’ no set correctly for POW resources.
- Changed the language on the error for a bad browser.Show the same unauthorized page as the datasets show for consistency. datasets show for consistency.User page gives server error when not logged in.
- Organization name of records should link to organization page not dataset page.
- Register API button had an invalid URL and was hard-coded.
- Sub-Organization "About page" is broken.
- Exception when setting the ‘Resource update Cycle’
- Formatting of metadata element headings in Additional Information section is inconsistent
- Delete icon broken in organization members list
- Fix tab issue on input screen
- The Contact Sub-org list blanked out when you enter a contact email address
- Correct spelling of centroid in geographic dataset addition page
- Links to ‘Markdown Formatting’ in ‘Manage BCGW Resource’ form do nothing
- Bug: Cannot add OFI resources in the add dataset workflow
- OFI resource still available even after the table name has been changed.
- Fixed
clippingMethodTypeso that secure orders from the Persistent Order Widget (POW) can succeed. The user story linked to this:
As a logged in user, use the POW to submit an order for a geospatial dataset that is restricted to IDIR download
- Remove snowplow code snippet - testing is complete and it can be removed from all environments.
- The
clippingMethodTypefix listed above, and configuration changes deliver value on the following stories:
As a user with a BCeID Business Account, I want the ability to download restricted data, BCeID restricted and Named BCeID user restricted, as I am able to do using the current (to be retired) distribution interface so that my ability to download and use BC eID restricted data continues after the old distribution interface has been shut down and replace by the Persistent Order Widget (POW).
- Removed hard-coded default settings for Persistent Order Widget (POW) order submission. The hard-coded values defaulted to an Area Of interest (AOI) that would cause orders to fail.
- To submit orders for IDIR restricted datasets, a parameter is passed to the
POWsecureSite. This parameter was incorrectly being set from a setting in the ckan.ini. The parameter is now determined by testing if there is a logged in user. The incorrect value meant that IDIR restricted datasets could not be ordered. - The signature of configuration settings used in helper functions was incorrect. Because there were default values in the calls the issue never presented as a bug. The signatures for the settings has been corrected.
- 440 metadata records containing a total of 736 resources omitted the
resource_storage_locationschema element; On 2018-10-27 the field and an appropriate value, was configured using a maintenance script (python). This was a one-time fix. All new records will include this field and have a value set.
- There were a number of hard-coded values in modules. These have been removed and made into ini settings
- In the POW order object, a required parameter was missing
aoi. Because this value was absent order could not use Mapsheets to limit Area Of Interest (AOI).
- Removed a hard-code value. This value incorrectly configured the url for the Order Fulfillment Interface (OFI) API call. This prevented Orders from being submitted to the API.
- Corrected incorrect reference in code to ini settings. Defaults were used and masked the issue.
- Fixed error message presented to user when they omit supplying a value for the new mandatory field:
resource_storage_location
- Resources added through OFI records added 'Formats' with incorrect case.
- Resource
last modifieddate is presentingGMTrather than local time. -
EPSG_3005 - NAD83 BC Albersnot default projection on resources for geographic datasets. -
HTTP 500generated when non-truthy or non-falsy values set forall_fieldsparameter. - dataset type facets do not function on search page
- list alignment in desktop browser
- Resource "Supplemental Information" markdown not being rendered.
- Data Explorer not working in CAT, works in CAD
- Activity Stream" link in dataset page is broken
- There are two Data API buttons in CAD
- Search for
traplinefails to return results.
- Rebase bcgov/ckan based on ckan/ckan 2.5.4 to 2.7.2
- POW/OFI Integration (Persistent Order Widget and Order Fulfillment Interface)
- Add SPATIAL_DATA_TYPE to core BCGOV Schema
- Add
SOURCE_DATABASEto core schema - Add "Dataset Usage" tab to Data Catalogue banner
- Move back to core ckan
- Return to PIP core release using 2.5.3BC
- Update to Postgres 9.5.x
- Navigating back from a selected sub-organizationdoes not correctly return the user to the parent organization in the Organization page.
- Add number of record views and resource download to the record page and its search results summary
- Adopt Standard Header on Data Usage Page
- Remove "Record Last Modified" from display in search results
- OFI orders for entire province no longer send a bounding box.
- Upgraded to latest patch of CKAN - now on v2.5.5
-
organization_list_relatedcorrectly parsesorganizationsparameter. - inconsistencies and problems with
recline_map_viewresolved with cache flush and correct revision of leaflet. - Reference to bootstrap CSS resource from OpenLayers resolves correctly. (FAIL) moved to 1.7
- StatsTrack failures resolved :
ckanext-ga-reportusing a deprecated metric from google analytics. - API console fixed for remote resources
- Turn of KML preview for resources.
- Remove the URL link on Geographic Record Resources
- MarkDown syntax works in
Data Quality,Lineage, andPurposefields
- Geographic Metadata Records creation interfaces general cleanup.
- Geographic Metadata Records creation streamlined -- draft records can be saved without adding a resource. -- draft records are view able to all branch editors -- links to the Order Fulfillment Interface (OFI) for each resouce type is now a button click.
- 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
- recline map background
- problems with OFI record creation and deletion
- resolve issue with Google Analytics recording
- resolve issue with mult-language availability - remove to prevent indexing by bots
- resolve unable to add new organizations
- resolve issue with editors removed from an organization continuing to receive email
- minor change to UI for lineage and purpose
- modify ini to support grid_view resource_view
- remove not used fields in apps and webservice schema
- 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
- upgrade to CKAN 2.5.2
- confirm functions of OFI API will work for DWDS interface
- hotfix to deal with MapQuest maptiles change in service
- implement 2.3.4
- update page header/footer
- fix Google Analytics
- purge ghost users
- investigate timing associated with less privileged roles
- 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.
- All the metadata previously found in the Geographic Data Discovery Service is now in the B.C. Data Catalogue.
- Retired the Geographic Data Discovery Service.