Code Monkey home page Code Monkey logo

eagle-public's Introduction

eagle-public

Public facing site project for EPIC

Related projects

Eagle is a revision name of the EAO EPIC application suite.

These projects comprise EAO EPIC:

Prerequisites

Note: The following commands work in MacOS bash (not zsh which now default in Catalina). The scripts are currently not fully working in Windows and Linux, so you may need to look at the source of the scripts and manually apply the commands in a right order.

Run the following two scripts to create your environment

#!/bin/bash
.\install_prerequisites.sh
#!/bin/bash
.\setup_project.sh

Fork, Build and Run

  1. After installing Node and Yarn, you can fork or straight download a copy of this application to start your own app.

  2. Run npm start to start the webpack server to run the application on port 4300.

    Go to http://localhost:4300 to verify that the application is running.

    💡 To change the default port, open .angular-cli.json, change the value on defaults.serve.port.

  3. Run npm run build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build, like so: ng serve --prod to run in production mode.

  4. Run npm run lint to lint your app code using TSLint.

CI/CD Pipeline

The EPIC project has moved away from PR based pipeline due to complexity and reliability concerns of the PR based pipeline implementation. The current CI/CD pipeline utilizes Github Actions to build Docker images and push them back into the BC Gov OpenShift Docker registry.

A full description and guide to the EPIC pipeline and branching strategy is available in the eagle-dev-guides repository.

Angular Code scaffolding

A brief guide to Angular CLI's code scaffolding can be found in eagle-dev-guides

Testing

An overview of the EPIC test stack can be found in our documentation guides: EPIC Test Stack.

Instructions on how running tests unit tests and end-to-end tests can be found in our test documentation.

How to Contribute

Feel free to create pull requests from the default "develop" branch, click here to create one automatically: https://github.com/bcgov/eagle-public/pull/new/develop

eagle-public's People

Contributors

a1astair avatar actionanalytics avatar bcgovneal avatar cameronpettit avatar cebergin avatar cebergin-vivid avatar ckoelewyn avatar corey-k avatar danieltruong avatar dhlevi avatar dinesh-aot avatar github-actions[bot] avatar jeznorth avatar kathydo avatar kirstenjvd avatar kitarmstrong avatar marklise avatar maxwardle avatar mtcarto avatar nickphura avatar repo-mountie[bot] avatar rpyyj avatar salabh-aot avatar saravanpa-aot avatar severinbeauvais avatar tolkamps1 avatar vesalink avatar w8896699 avatar wadebarnes avatar

Stargazers

avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

danieltruong maxwardle rpyyj actionanalytics kathydo w8896699 marklise sierrasystems mtcarto baaraakaa a1astair dhlevi vesalink cebergin kitarmstrong wadebarnes nickphura bcgovneal cameronpettit digitalspace salabh-aot dinesh-aot marilynn-stone tolkamps1 kevindesao ckoelewyn tom0827

eagle-public's Issues

ZAP Scan Baseline Report

View the following link to download the report.
RunnerID:95645372

Change EPIC.public Contact Page

As a member of the public

I want the correct email on the contact page

so that I can get in touch with the EAO about my concerns

Acceptance Criteria

Scenario 1:

GIVEN I want to contact the EAO about EPIC.public
WHEN I go to https://www.projects.eao.gov.bc.ca/contact
THEN I see [email protected]

Scenario 2:

xxxxxx

Validation Rules?

(If yes, list here)

Screenshot

(Link above will always be the most up-to-date version.)

Character Limiter on the Name & location fields for the submit comment modal. (150 char)

As a Admin

I want to put a Character Limiter of 150 characters on the Name & location fields for the submit comment modal.

so that the submitters will stop putting their entire comments in the name field.

Acceptance Criteria

Scenario 1:

GIVEN ... (you or your condition)
WHEN ... (what you do)
THEN ... (what you see)

Scenario 2:

xxxxxx

Validation Rules?

(If yes, list here)

Screenshot

(Link above will always be the most up-to-date version.)

Setup Patroni

Install Patroni in all environemnts

  • Back up and restore data to new DB
  • Single DB approach for multiple applications (different schemas)

EPIC+MET

Overview
Includes more issues about MET and EPIC integrations

Show PECP in the project details page as MET

Overview
Given below is the current screen
image (1).png

Replace the above banner with MET banner like the one below

image (2).png

It should redirect the users to MET screen and should be able to view and submit comments from their.

The project details page should be changed with more better UX

Overview
The left panel should be shown information based on the priority. Such as data with more priority should be given importance over the less important ones. The current details page is given below
image.png
UX person should have a look at this issue.

The document search in the project should be reorganized

Overview
The documents can be organized as folders which users might feel more confident to look in to. This require a UX person to participate in the design process.
The folders can be phases-> document types -> documents

CHES credentials to be updated in all environment

What is happening?
Access to our hosted services is migrating to leverage the API Services Portal at api.gov.bc.ca.
The following two APIs are affected:

  • Common Hosted Email Service (CHES)
  • Common Document Generation Service (CDOGS)
    If you currently use either of these services, you will need to request a new set of credentials using the API Services Portal.

Why?
We believe the API Services Portal and Gateway service offered by a dedicated team at the Ministry of Citizen Services will provide a better onboarding service for our API consumers. This move also allows us to reduce duplication of efforts and resources (such as Keycloak realms and the onboarding web interface)

When is this happening?
Please request access through the Portal at your earliest convenience. You are encouraged to start using the new credentials and endpoints as soon as possible.
At the end of December 2022, access to these services using your old credentials will no longer work.

What should You do?

  1. Go to the API Services Portalhttps://api.gov.bc.ca/devportal/api-directory and find the CHES and/or CDOGS API in their Directory.
    Click ‘Request Access’ and sign into the portal. Fill in our request form and choose the environment you want to access. Please provide contact information of the Product Owner as well. This must be repeated for each environment.
  2. The Common Service Showcase team will complete the request and notify you soon after and your credentials will become active.
  3. Update your client application with the new credentials and API endpoints.
    Important Notes:

ZAP Scan Baseline Report

View the following link to download the report.
RunnerID:332206091

ZAP Scan Baseline Report

View the following link to download the report.
RunnerID:789845804

Adding Dispute Resolution to the EA process dropdown

As a member of the public

I want to see Dispute resolution as an option in the EA process menu

so that I can learn more about how the EAO works

Acceptance Criteria

Scenario 1:

GIVEN I select the EAO process dropdown menu
WHEN I select DR from the list
THEN I see a page that has the below text and link

Scenario 2:

GIVEN I am on the DR page
WHEN I select the link
THEN I am taken to this e-guide page: https://www2.gov.bc.ca/gov/content/environment/natural-resource-stewardship/environmental-assessments/dispute-resolution

Validation Rules?

(If yes, list here)

Screenshot

The EA Process:
Dispute Resolution
Learn about dispute resolution between First Nations and the Province

Page Description:
Supporting reconciliation with First Nations is a key purpose of the Environmental Assessment Office (EAO). The EAO collaborates with First Nations throughout the assessment process and involves First Nations in the decision-making on projects that may affect them.

The EAO seeks consensus with First Nations at key points in the environmental assessment process. Dispute resolution is intended as a tool to support consensus-seeking. If consensus is not reached, dispute resolution is a collaborative and principled process to resolve the dispute consistent with the United Nations Declaration on the Rights of Indigenous Peoples.

Under the Environmental Assessment Act, dispute resolution is available at key decision points in the environmental assessment process. An experienced, third-party facilitator may be appointed to help guide the Province and participating Indigenous nations when they are unable to reach consensus on their own.

Link: [Dispute Resolution with First Nations - Province of British Columbia (gov.bc.ca)](https://www2.gov.bc.ca/gov/content/environment/natural-resource-stewardship/environmental-assessments/dispute-resolution)

Comment tab in the project details page redesign

Overview
CommentTab

The XD link is given below
https://xd.adobe.com/view/e2831462-9efd-4312-9879-bb765be852bd-b7d0/screen/61bc3e9d-5e25-4f54-a66f-0fae9b5e2677/

Here, also, data can be pulled from EPIC for now at least to get started with integrating the design. Later, this can use APIs from MET to get the engagements corresponding to a project.

Up on hitting the "View Enagements" button, the user will be navigated to the MET engagement screen where they can deal with the engagement such as commenting and all.

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

  • If this product is being actively maintained, please close this issue.
  • If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Add MET Survey banner in EPIC

Overview
Integrate the survey banner in the landing page of EPIC public portal. The design can be found in the below URL
https://xd.adobe.com/view/e2831462-9efd-4312-9879-bb765be852bd-b7d0/specs/

The survey URL should be able to be integrated from externally, like using an environment variable.
We can add ENV variables in the deployment config and add the line code in the below mentioned file.

https://github.com/bcgov/eagle-public/blob/develop/openshift/templates/nginx-runtime/s2i/bin/run

Plus, we need to add this in the template file for future deployments.
https://github.com/bcgov/eagle-public/blob/develop/openshift/templates/angular-on-nginx/angular-on-nginx-deploy.json

This file will get executed and generate a js file, which will get bundled during the build process and cause the corresponding local storage item to be created in the browser. You can see, they have injected the backend api URL in the same way.

Remove the white background from the left panel of project detail page

Overview

Try to browse this URL
https://eagle-test.apps.silver.devops.gov.bc.ca/p/6269d0c4ff01950022317d11/project-details
You will be able to see a white background in the left pane where it shows the basic details of project. See the difference in the production.

This is not just for this specific project. This change happened in the test environment because of the banner colour change made in the landing page. We need to keep that banner style change also has to be able to manage to get this detail page as the current production.

API Integration for loading open engagement data to be shown in the project detail page

Overview

Show the open engagement in the banner section of the project details page. Integrate the API from MET for that. The API is not available at the moment.
The front end can still consume one of the EPIC APIs and it the EPIC API which can call MET to get the data. In that way, the frontend would always have only one endpoint to interact with.

Add project lifecycle badge

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 181 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

  • If this product is being actively maintained, please close this issue.
  • If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Add missing topics

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

add a topic

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

  • If your org is not in the list below, or the table contains errors, please create an issue here.

  • While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

  • Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

  • If your application is live, add the production URL.

Ministry Short Codes

Short Code Organization Name
AEST Advanced Education, Skills & Training
AGRI Agriculture
ALC Agriculture Land Commission
AG Attorney General
MCF Children & Family Development
CITZ Citizens' Services
DBC Destination BC
EMBC Emergency Management BC
EAO Environmental Assessment Office
EDUC Education
EMPR Energy, Mines & Petroleum Resources
ENV Environment & Climate Change Strategy
FIN Finance
FLNR Forests, Lands, Natural Resource Operations & Rural Development
HLTH Health
FLNR Indigenous Relations & Reconciliation
JEDC Jobs, Economic Development & Competitiveness
LBR Labour Policy & Legislation
LDB BC Liquor Distribution Branch
MMHA Mental Health & Addictions
MAH Municipal Affairs & Housing
BCPC Pension Corporation
PSA Public Safety & Solicitor General & Emergency B.C.
SDPR Social Development & Poverty Reduction
TCA Tourism, Arts & Culture
TRAN Transportation & Infrastructure

NOTE See an error or omission? Please create an issue here to get it remedied.

Add project lifecycle badge

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.