Each submitted spatial file overwrites the last for a specific submission type - i.e.: Cut Block submission 2 overwrites cut block submission 1. However, if the client accidentally submits a road file instead of an intended cut block file, there is no way to delete that road submission.

Users would like the ability to delete a submitted spatial file.

Business would like to list submissions made on the upload screen with a trash can icon or some method of deletion beside each

This issue transferred from Jira (FOM-112)

On the summary screen, relabel "Irrelevant Comments" to Non Applicable Comments

Issue transferred from Jira (FOM-113)

. In order to facilitate the publishing of the initial notice on a government website, we need to add a tab/screen to the software. The idea is for FSP holders to fill out a form that contains all legally required notice content ( i.e. Company, contacts, place of business, business hours etc.). Once the form has been completed, a “prefabricated” official notice should be published on the new notices tab/page every time a FOM of the respective user opens for commenting ( switches from publish to commenting open).

This issue transferred from Jira (FOM-111)

![screenshot-1.png](https://images.zenhubusercontent.com/61f87aa78804f87afc5530bd/02e09882-5f62-4c5a-8eea-
a92ae6e4b039)

In order to gain the trust of DBAs, data stewards, data architects, etc. FSA needs a well thought-out data data governance process that applies to APIs that expose data to systems, authenticated (and authorized) users, and the public.

WIP: https://apps.nrs.gov.bc.ca/int/confluence/display/FSAAR/API+Data+Governance

Acceptance criteria:

• Document the requirements for a governance framework
• Propose a simple, github-enabled process to start out with
• Get feedback from stakeholders

Shared realm manangement

Need to be able to run FOM in Docker Compose

On Finalize of the FOM, send the notice to the inbox belonging to each district.

Spreadsheet of email addresses to be attached.

This list is likely to be updated

This issue transferred from Jira (FOM-116)

PDF attached converted from GOVERMNET_GROUP.xls attached to FOM-116. The spreadsheet content is related to the SQL query:

select gg.GROUP_NAME, gg.EMAIL_ADDRESS from app_rrs.government_group gg

https://app.zenhub.com/files/452009299/e48c9002-e41e-4e67-bd26-d472223ed3b8/download

This issue doubles as an epic for Greenfield-Template, via ZenHub.

https://github.com/bcgov/greenfield-template

Currently when clicking on an object, the pop-up will appear at the geographical centre of the object. This is an issue if you are zoomed in on the map so you don’t see the whole object; the popup may appear off map. It would be better to show up in the location the user clicked. Another example is a really long road, in the image below, the red circle denotes where I clicked on the road, and the popup appears well outside the extent of the blocks themselves.

https://app.zenhub.com/files/452009299/8b54aa4c-f2ff-4092-86ea-bb49cc613823/download

This issue transferred from Jira (FOM-114)

• implement a simple datafix for Anne Marie using the on prem. Jenkins cron service.

First attempt of this task Consists of:

1. Getting the scripts that Anne Marie runs
2. Putting scripts into a github / or other repo (includes parameterize / extraction of any data that might be private (db link names as an example)
3. Create a jenkinsfile that will run the scripts

• long term think about running this work in Openshift as a cron job and pipe the results / logs to the observability stack

FOM has a requirement for a list of forest districts. It is hard-coded in FOM at present.

Just a local FlywayDB run in a local container. Not in EC2 (yet).

The data governance process is here: https://apps.nrs.gov.bc.ca/int/confluence/display/AR/Data+Integration?

First step is :

Has the Team identified the data\information required for the business needs?
Has the Team documented the business needs as related to the data sought. (If so provide source/link/documents)

Documented on GitHub wiki:
https://github.com/bcgov/forest-client-api/wiki/Business-Requirements

Security concerns vs GHA

Include names, specialties and maybe interests. Could be useful for finding areas of expertise and escalations in a pinch.

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!

The IRS entry for FOM is lacking information.

As an IRS user
I want the IRS entry for FOM to be accurate
so that I can rely on the information to support business processes.

Acceptance Criteria:

• The Technologies, External Services, Participants, and Technical Resources, URL fields reflect current status

Definition of Done

• Ready to Demo in Sprint Review
• Peer Reviewed by 2 people on the team

Please replace personal email with distribution list email for things like alerts, certs, and reports:

Distribution List: LWRS SIBI FSA-Fingerprints
Distribution email: [email protected]

Current members of the list include:

• derobert
• GATITEBI
• ptollest
• KJNether
• mrdouvil
• tagbaje

Let me know if anyone else should be added.

Partnership agreement

In order to request activity from a DBA, they need to have a database script that they can run (and re-run if necessary). This is usually provided to them in the form of a zip file. We created a new GitHub repo to store the scripts that we want them to run: https://github.com/bcgov/nr-fsa-scripts

DBAs need to be able to download a single zip file to run their scripts. Even though it is a manual process that could possibly invalidate the version control of these scripts, we decided that a simple solution was to check in a zip file with the scripts along with the scripts themselves. We can then give them a link to the zip file in GitHub. Since it is a public repo, they don't need to have a GitHub account or use any git commands locally.

In order to help them understand and feel confident that the link we give them cannot change, we need to document this process.

AC: Readme.md on the nr-fsa-scripts repository that explains to the DBAs the process that we use for developing scripts and zipping them up for consumption via https download.

Make sure that you capture the fact that you need to create a JIRA ticket. The way that change management works is that each project needs its own JIRA project. Any request to an infrastructure team has to have a JIRA ticket.

1Team vs Platform Services

MariaDB Walkthru from 1Team

Intregration with Liquibase/FlywayDB

Dynamic secrets

See comments on this issue for the full story...

TLDR: Forest client data classification was done in a Jira ticket

It would be useful to have the spatial objects linked to the table below the map. This way if you clicked on a record in the table, it would either highlight, flash or zoom into the corresponding spatial. This could be an option if labels are too much

NOTE: Julius Huhs Product Owner identifies this as higher priority over FOM-114

This issue transferred from Jira (FOM-115)

https://app.zenhub.com/files/452009299/3d479f9d-eeda-4a11-bc43-b8b2a2a9c64f/download

FOM has a requirement to allow a submission to be associated with an FSP ID. Currently, the user just inputs an FSP ID and there is no validation that it is a real FSP ID. In order to validate, an API would be useful.

Instructions for developers here: https://github.com/bcgov/nr-fsa-scripts/wiki/Developer-Process

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

Pro Tip 🤓

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