This applies to the keywords field on datasets and the iso topic category field on resources. Behaviour is not exactly the same but code is similar so will look at both at once

@BrandonSharratt commented on Thu Feb 28 2019

See epic but allow the adding and editing of resources on the standard dataset type. Only need to make sure that csv and xlsx work by default but if 'trivial' to support add more types. Support preview of csv/xslx

The design for the following views has been modified to add icons adjacent to the existing labels:

• Dataset view;
• Resource view;
• Organization view; and
• Group view

Currently, iMap has its target for form submission set to _top, the highest level window of the page (for some reason). Changing this to _self would still preserve prod functionality in pop-up window while allowing functionality to be contained within an iFrame.
Reference re form object => https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form.

Change facets on the beta ui.

Some of the logic for how to display/sort objects is in the vuex store, we should move things that don't affect lists (at least) the backend bridge in an attempt to normalize the data so if the backend changes with a new version of CKAN or if the backend isn't CKAN it would be easier to change it.

@BrandonSharratt commented on Fri Mar 22 2019

Add the user profile to the new ui

The history router is broken investigate and fix. (This is the router that removes the # from the url and allows people to url link to specific pages)

Creation of a groups view.

Implement the splash view.

implement the dataset list tweaks from the ux feedback

Create view for Datasets List.

Geographic resources need to be preview-able via map component

Filters as required to replace the existing filters.

Implementation of resource view from ckan-ui#39

@BrandonSharratt commented on Fri Mar 22 2019

Add the user profile to the new ui

@SteveChapmanBCDX commented on Fri May 24 2019

Issue moved to bcgov/ckan-ui #14 via ZenHub

Admins need to be able to create and edit orgs

@BrandonSharratt commented on Fri Mar 08 2019

Create a Docker container and a helm chart to simplify deployment of the new ui

@BrandonSharratt commented on Thu Feb 28 2019

See epic but for adding and editing records in the new ui

depends on the login functionality

@BrandonSharratt commented on Thu Feb 28 2019

See epic but add the ability to login, probably keycloak related. Depends on Mikes user stories that come of this, but investigate for now

@BrandonSharratt commented on Tue Mar 05 2019

ckanext-keycloak exists and although buggy does work with minor changes for us. It will even tie into existing users.

The ui uses keycloak authentication and then uses the jwt to authorize with ckan.

Keycloaks default timeout is 5 minutes on the token so we'll need to build renewal into the token

@BrandonSharratt commented on Tue Mar 05 2019

I've made it refresh tokens in the window between expired and refresh tokens being valid (keycloak default is access expires in 5, refresh expires in 10, so therefore it would refresh the token on a call made between 5 and 10).

Implement datasets view.

@BrandonSharratt commented on Fri Mar 22 2019

Add the organization list page to the new ui

Design the dataset view.

Design of splash view.

Build Organizations view.

See required updates here => https://github.com/bcgov/ckan-ui/network/alerts

Creation of a datasets view.

Prepare a report that summarizes the research findings to date. Include report methodology. Include recommendations for UI/UX modifications, additional research and other pertinent issue. Link recommendations to evidence developed from research.

@BrandonSharratt commented on Thu Feb 28 2019

See epic but for dataset view page

The splash view includes three main placeholder views. These views need to be populated.

Resource list on dataset page loads correctly initially but when the full details are fetched one of the resources will overwrite other resources randomly

Create the organization view.

Implement Dataset View based on #36

Bucket to document backlog items as they arise.

We might want to change this down the line. There are a lot of orgs - when open, it takes up a lot of room.

Post MVP, do we want to change this to scroll (or some other solution)?

The new UI has an increasingly high time to load as we add libraries and code, investigate ways to speed up page load.

In CADI and CATI, the back end will occasionally fail with no error message. The behaviour from the user's perspective is a perpetual spinner (that is, the failure is not graceful).

How do we handle this error more gracefully? Reviewed with dev group => recommended implementation is timeout that alerts user that there has been a failure and invite user to reload application.

Related, but not pertinent - Issue may arise from config differences between CADI and CATI. Probably best to diff the containerization setup between CADI and CATI.

Create an organizations view.

Create a group view.

Design the Resouce View.
Design these ancillary views:

• Resource Preview view; and
• Resource View Schema view

Load up a dataset page, the loader will spin indefinitely when schema isn't already pulled from the api.

You can simulate this by logging in or out on that page.

See if you can fix and also increase performance (speed up page load)

Probably cache the schema in the backend bridge. delete the old view fallback, and have a "This is taking a long time to load fall back instead"

@BrandonSharratt commented on Thu Feb 28 2019

See Epic but for dataset list

As a user,

I want a new ui

so that shiny.

As a developer,

I want a new ui

so that concerns are separated thus making maintenance is easier.

Prepare user experience map for end user.