Code Monkey home page Code Monkey logo

met-public's Introduction

met-public

Lifecycle:Experimental

codecov

Quality Gate Status

The Modern Engagement Tools (MET)

This project is to develop modern engagement tools that address shortfalls identified in the Province’s existing public engagement processes.

Objectives

The goal of this project is to transform B.C.’s public engagement processes and enable the public to provide more value and influence decision-making while generating useful data insights, an enhanced post commenting experience for the user, and minimize rejected comments. The product will be cost effective, leverage investments and successes to date, explore best in class strategies, and be maintainable and continuously improved by government staff. It will be privacy enhancing, and support DRIPA/ GBA+ implementation and analysis, and continuously delivered and tested with users.

Directory Structure

.github/                   - PR, CI action workflows and Issue templates
/docs                      - Miscellaneous documentations
met-web/                   - MET Web application root
├── src/                   - React.js application
└── tests/                 - Application tests
    └── unit/              - Jest unit tests
met-api/                   - MET API Application Root
├── src/                   - Python flask application
│   └── met_api/           - Models, Resources and Services
├── migrations             - Database migration scripts
└── tests/                 - API application tests
    └── unit/              - Python unit tests
notify-api/                - Notification API Application Root
├── src/                   - Python flask application
│   └── notify_api/           - Models, Resources and Services
└── tests/                 - API application tests
met-cron/                  - Job Scheduler Application Root
├── src/                   - Python application
│   └── met_cron/           - Models, Resources and Services
└── tests/                 - Job Scheduler tests
openshift/                 - OpenShift templates and documentation
snowplow/                  - Snowplow custom schemas
CODE-OF-CONDUCT.md         - Code of Conduct
COMPLIANCE.yaml            - BCGov PIA/STRA compliance status
CONTRIBUTING.md            - Contributing Guidelines
LICENSE                    - License

Documentation

Auxiliary Repositories

Getting Help or Reporting an Issue

To report bugs/issues/features requests, please file an issue.

How to Contribute

If you would like to contribute, please see our contributing guidelines.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

License

Copyright 2022 Province of British Columbia

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

met-public's People

Contributors

aforde-aot avatar baelx avatar dependabot[bot] avatar dinesh-aot avatar djnunez-aot avatar jadmsaadaot avatar jareth-whitney avatar natsquared avatar nikhila-aot avatar ratheesh-aot avatar repo-mountie[bot] avatar saravanpa-aot avatar tiagografiti avatar vineetbala-aot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

met-public's Issues

Setup docker

Add docker files to project folders
Add docker compose for postgres, mongo and formio components.

An Admin user can add a image to the Banner (Header) for the engagement page

As an Admin, I want to add a banner (header) image to the engagement
so that the public can visualize the engagement.

Acceptance Criteria

Scenario 1:

Admin is on the create engagement page and clicks the top section of the Create Engagement page to upload an image. Pop-up opens to let Admin select an image from a few Images available. Admin selects a pre-defined image and clicks the save button. Image is added to the "Create Engagement" page.

Scenario 2:

Admin is on the create engagement page and drags and drops a pre-defined banner image in the top section of the Create Engagement page to upload an image.
Image is added to the "Create Engagement" page.

Scenario 3:

Confirm user interface to the visual design
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/32caf4d5-99c5-4df2-9e43-620e6b838203
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/c4541a52-0b8e-40e8-bf9d-78ea1da0404d

Validation Rules?

Screenshot

(Link above will always be the most up-to-date version.)
![Screen Shot 2022-06-10 at 12.20.08 PM.png](https://imag![Screen Shot 2022-06-10 at 12.19.49 PM.png](https://images.zenhubusercontent.com/6261bc1a04c6a94c2edadddd/93e60385-3ced-45bb-88a6-18f7bc44ae7d)es.zenhubusercontent.com/6261bc1a04c6a94c2edadddd/69503424-dae5-417c-b415-4cfdc084ad94)

Banner Images
banner-windmill-3-1920x720px.jpg
banner-windmill-2-1920x720px.jpg
banner-windmill-1-1920x720px.jpg

An Admin User can designate "Who is Listening" to the engagement page by adding a widget.

An Admin user can designate "Who is Listening" to the engagement page by adding a widget so that the public knows a human is actually listening. It could be a name and photo. For default it could be the ADM, Communications or the Engagement Officer.

Acceptance Criteria:

User clicks the "Add Widget" button in the widget section.
Selects "Who is Listening" from the widget selection.
The public can see an assigned Government Employee's name, picture and/or contact info on the engagement page.
It may have an email link to a personal or group account

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 it's 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 it, 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
IRR 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 Service Agency
PSSG Public Safety and Solicitor General
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.

An Admin can Log In with IDIR

Description:

As a Admin user I would like to use my goverment account (IDIR) to login into the MET application so that I can manage engagements within the app.

Acceptance Criteria

Users can login using IDIR

Associated tasks -

An Admin User can create a survey directly on the engagement page to add to my engagement

As an Admin

I want to create a survey

so that I can to add it to my engagement

Acceptance Criteria

Scenario 1:

Admin is on the Create/Edit engagement page and Clicks the button "Add Survey" in the Surveys section.

Scenario 2:

Admin sees the "Create Survey" screen.

Section Header: "Create Survey" (+ edit icon = Survey name is editable)
Radio buttons for the following options:
Create a new Survey
Clone an existing Survey
Add an existing Survey to my Engagement

"Save & Continue" and "Cancel" buttons

Admin selects "Create a new Survey", sees the input field "Enter Survey Name" enters Survey Name and clicks on "Save & Continue" button. Survey page opens. Survey is created in database and show on Engagement page & Survey listing page.

Scenario 3:

Confirm user interface to the visual design
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/d5ff35b0-90ea-49eb-a8f2-fe307a156b92
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/bf0d9afb-1c4b-4ab3-a08f-8ed5a7b35163/
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/c180802e-cc2d-4bde-9ae6-231dcce70e65
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/f2b3759e-bacb-41ae-ae84-e74c304877d8/
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/2a77ed82-38d7-4a24-be8a-f6d329a807ed/

Validation Rules?

If admin clicks the button to add a survey (or widget), Engagement must contain at least the engagement name and be saved.

Validation message "Please add the Engagement Name and save the Engagement before adding a Survey."

Screenshot

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

An Admin user can view a calendar of engagements

As an IDIR User I can log in and view a calendar of engagements so that they can see when the sum of the engagements.

Acceptance criteria

Given populated engagements users can view the dates of previously input engagements and engagement periods

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 :)

As an Admin, I want to add a widget to display important documents on the Engagement.

As an Admin

I want to add a widget to display important documents to an Engagement

so that I can create folders and add documents to show on the Engagement.

Acceptance Criteria

Scenario 1:

Admin clicks the "Add Widget" in the Widget section.
Admin selects the "Document" card from the widget cards on the widget selection panel.
Admin sees the "Document" panel.
Section Header: Documents (+ edit icon = widget name is editable)
Checkbox to "Hide Title" (to hide title on published card)
"Create Folder" and "Add Document" buttons
"Save & Close" and "Cancel" buttons

Scenario 2:

Admin clicks "Save & Close" to save the widget. Widget is created (even if no Document has been added).

Scenario 3:

Admin clicks "Cancel" to exit. Widget is not created.

Scenario 4:

Confirm user interface to the visual design
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/cca8437e-bd10-4dc8-b325-d8e824b6ea33,
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/b7897f6a-60ec-43c2-9bd0-4b089861032f

Validation Rules?

(If yes, list here)

Screenshot

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

As an Admin I want to add a question (multiple lines answer) to a survey so that I can use build custom surveys

As an Admin

I want to add a question (multiple lines answer) to a survey

so that I can use build custom surveys

Acceptance Criteria

Scenario 1:

Admin has created a Survey (https://app.zenhub.com/workspaces/met-ops-6254279dcfa60b0010ea5a0d/issues/bcgov/met-public/47 OR https://app.zenhub.com/workspaces/met-ops-6254279dcfa60b0010ea5a0d/issues/bcgov/met-public/97 ) and sees the Survey screen.

Scenario 2:

Survey screen

Section Header: (+ edit icon = widget name is editable)
Search Question Types
Left Side Question Selector
"Save & Close" and "Cancel" buttons

Scenario 3:

Admin drag and drop "Multiple Lines Answer" on the right to add question.
Fills in the modal with question details. Modal only has fields required. (https://docs.google.com/spreadsheets/d/1icshGjXzZb-kAXINKXnaxDt_TW-uqcqxQMjHra188Dc/edit?usp=sharing)

Scenario 4:

User Inferface is similar to:
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/e17bccde-cc66-4e52-8f47-4c9afaa79c0f

Validation Rules?

(If yes, list here)

Screenshot

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

As an Admin, I want to save an Engagement as draft.

The user interface must follow the visual design as per https://xd.adobe.com/view/7360b654-4a25-4140-9670-a56f4adabe7a-2633/screen/c50b5e94-c060-44d5-a636-4be6c3004e64 (Engagement saved as draft shows on table with status of "Draft") and https://xd.adobe.com/view/7360b654-4a25-4140-9670-a56f4adabe7a-2633/screen/32caf4d5-99c5-4df2-9e43-620e6b838203

Admin User clicks "Save Engagement Draft" button at the bottom of the Create Engagement page.
Draft Engagement is saved.
Draft Engagement shows up on Landing page table with a status of "Draft".

An Admin can add a question (single line answer) to a survey

As an Admin

I want to add a question (single line answer) to a survey

so that I can use build custom surveys

Acceptance Criteria

Scenario 1:

Admin has created a Survey (https://app.zenhub.com/workspaces/met-ops-6254279dcfa60b0010ea5a0d/issues/bcgov/met-public/47 OR https://app.zenhub.com/workspaces/met-ops-6254279dcfa60b0010ea5a0d/issues/bcgov/met-public/97 ) and sees the Survey screen.

Scenario 2:

Survey screen

Section Header: (+ edit icon = widget name is editable)
Search Question Types
Left Side Question Selector
"Save & Close" and "Cancel" buttons

Scenario 3:

Admin drag and drop "Single line Answer" on the right to add question.
Fills in the modal with question details. Modal only has fields required. (https://docs.google.com/spreadsheets/d/1icshGjXzZb-kAXINKXnaxDt_TW-uqcqxQMjHra188Dc/edit?usp=sharing)

Scenario 4:

User Interface is similar to:
https://xd.adobe.com/view/e38dc788-12d5-4844-87ca-149d1d32d395-b6de/screen/e17bccde-cc66-4e52-8f47-4c9afaa79c0f

Validation Rules?

(If yes, list here)

Screenshot

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

A user can validate their email address to access a survey

A user can validate their email address so they can access a survey.

Acceptance criteria

Scenario 1:
User clicks a link to access the survey link, sees the "verify email" modal:

Header: Verify your email address
Text: To provide you with the best experience possible, we require you to validate your email address. (i icon, content tbd)

You will receive a link to access the survey at the email address you provide.
Box: T&C (TBC)
Checkbox: I agree to the Terms and Conditions above.
Input:
Email address

Buttons: "Cancel" & "Submit"

Scenario 2:
User adds their email address and clicks "Submit".

Modal:
Header: Thank you
Text: We sent a link to access the survey at the following email address:

Bold Text: Please click the link provided to access the survey.
The link will be valid for 24h.

Button: "Close"

User returns to Engagement page

Scenario 3:
User adds their email address and clicks "Submit".

Modal:
Header: We are sorry
Text: There was a problem with the email address you provided:

Bold Text: Please verify your email and try again.

If this problem persists, contact

Button: "Try Again" & "Return to Engagement"

Scenario 4:
Matches wireframes:

https://xd.adobe.com/view/c19819d0-bedb-4427-93c3-d06f784fc2af-94cb/screen/a1efade1-d448-48da-ab15-3974b36c2dd3/specs/
https://xd.adobe.com/view/c19819d0-bedb-4427-93c3-d06f784fc2af-94cb/screen/342e6adc-7b0d-4feb-a271-cec3d2aed777/specs/
https://xd.adobe.com/view/c19819d0-bedb-4427-93c3-d06f784fc2af-94cb/screen/fb21a8fe-7f6e-4de8-b05e-e3e3db88569b/specs/

Create React Front end skeleton

Create base/empty reactJs project and add it to our github repo.

The repo folder structure might look something like this:

met-public
web (frontend - reactJs code)
api (backend - python flask code)

Create reactJs app
Create unit tests project

Lets use common phrasing

TL;DR 🏎️

Teams are encouraged to favour modern inclusive phrasing both in their communication as well as in any source checked into their repositories. You'll find a table at the end of this text with preferred phrasing to socialize with your team.

Words Matter

We're aligning our development community to favour inclusive phrasing for common technical expressions. There is a table below that outlines the phrases that are being retired along with the preferred alternatives.

During your team scrum, technical meetings, documentation, the code you write, etc. use the inclusive phrasing from the table below. That's it - it really is that easy.

For the curious mind, the Public Service Agency (PSA) has published a guide describing how Words Matter in our daily communication. Its an insightful read and a good reminder to be curious and open minded.

What about the master branch?

The word "master" is not inherently bad or non-inclusive. For example people get a masters degree; become a master of their craft; or master a skill. It's generally when the word "master" is used along side the word "slave" that it becomes non-inclusive.

Some teams choose to use the word main for the default branch of a repo as opposed to the more commonly used master branch. While it's not required or recommended, your team is empowered to do what works for them. If you do rename the master branch consider using main so that we have consistency among the repos within our organization.

Preferred Phrasing

Non-Inclusive Inclusive
Whitelist => Allowlist
Blacklist => Denylist
Master / Slave => Leader / Follower; Primary / Standby; etc
Grandfathered => Legacy status
Sanity check => Quick check; Confidence check; etc
Dummy value => Placeholder value; Sample value; etc

Pro Tip 🤓

This list is not comprehensive. If you're aware of other outdated nomenclature please create an issue (PR preferred) with your suggestion.

Create Python Flask Skeleton

Create base/empty python flask api project and add it to our github repo.

The repo folder structure might look something like this:

met-public
web (frontend - reactJs code)
api (backend - python flask code)

  • Create python api using flask
  • Create unit tests project

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.