innbyggerpanelet's Introduction

Innbyggerpanelet

For nå er utviklingen av innbyggerpanelet satt på vent

Environmental variables

In order for this project to run in a local development environment you will have to configure an .env file. Most of the fields can be configured as you see fit, however there are OIDC keys which requires you to be a part of the @team-researchops namespace in order to obtain.

Please post in #researchops for more information/help.

Commit naming conventions

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

The commit contains the following structural elements, to communicate intent to the consumers of your library:

fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).
BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.

innbyggerpanelet's People

Contributors

Stargazers

Watchers

innbyggerpanelet's Issues

Insight API integration

Models
Services
Routes
Fetching

Implement data structure

Find a better way of casting queries

Fix react modal warning

Basic implementation of consents

Criteria admin panel

Reference to data structure issue for clarification.

Originally posted by @amundlrohne in #20 (comment)

Azure AD auth

Employee facing auth

A administrator must be able to view their profile

A administrator must be able to CRUD a type of user insight for a user insight project

It should include:

Information about the specific user insight
Number of candidates needed
Time period for the user insight
Specific criteries for the specific user insight
What kind of consents are needed for the specific user insight
Auto-generated list of suitable candidates

Add error handler for API

Add rate limiter to the API

It is possible that this is handeled by NAIS, but it should be explored

Pseudonyms for candidates in insight works

Add field for pseudonyms in the candidate table, could be randomly generated for each user and be unique to the insight work in question.

Add feedback on user actions

Fix modal error

Messes with universal access.

Deploy on frontend is failing

Syntax error in a yaml file

Logging: user and data identification

Inbox and messages for invitations

Add routes for the frontend

Admin dashboard

Features:

Ability to edit criterias and their categories.
Add new admins
Manual creation of candidate profiles?
Should be restricted to users with the "admin" role.

On insight creation, database gives error

This error is given from the database:
ERROR: insert or update on table "insight_consents_consent" violates foreign key constraint "FK_1da52183b251702acfa22b09718"

Roles and permissions

Implement roles and restrict routes based on those roles.

Slugs for project and insight names

Suggestion

If we add slugs based on the names of projects and insight work, our URLs will have better readability and enable us to have "pretty" breadcrumbs effortlessly.

Examples

Current version of a frontend url and breadcrumb
/prosjekt/1
Hjem / Prosjekt / 1

Suggested version
/prosjekt/bidrag-til-særlige-utgifter
Hjem / Prosjekt / Bidrag til særlige utgifter

Not entirely sure if ÆØÅ can cause problems with the approach.

Update service classes to follow the base entity class

Project API integration

Models
Services
Routes
Fetching

Add cypress testing

Add linting for imports

Add NAV employee landing page

Check if breadcrumbs creates XSS vulnerability

Logging: debug levels based on environment

More detailed error messages in dev env.

Design the data structure for the application

Blocked untill a more settled design is completed

Add validations to the frontend

Decide which routes are to be protected and to what level

Add logging on the API

Add physical diagram to documentation

A administrator must be able to CRUD a new user insight project

It should include:

Details about the specifc user insight project
A list of team members responsible for the user insight project
List of all the specific user insight that is included in the user insight project

User API integration

Creation of new users.
Edit old users.
Differentiate between NAV team members and candidate users.

Candidate API integration

Models
Services
Routes
Fetching

A candidate must be able to se his/her profile

Find solutions for patching data

Need to make designs for how updating information should be handled, and what restrictions need to be put in place.

A candidate should be able to get a more detailed view of insight work participated in, at their profile

Update github workflows

We should consider updating the github workflows and split them up, as they are now always running on each push on every branch. There might be times when we want the workflows to run at different times.

My suggestion: