Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflows #165

Open
LeScruf opened this issue May 18, 2023 · 4 comments
Open

Workflows #165

LeScruf opened this issue May 18, 2023 · 4 comments

Comments

@LeScruf
Copy link
Collaborator

LeScruf commented May 18, 2023

A straight-forward (we hope!) work flow for the tree farmer system which applies to all data entered. This is bad design because the Land Management Officer stands to become a major bottleneck in the publishing of data to the system.

One solution to this design issue is simply to be able to assign other selected users equivalent permissions to approve / reject the data entered and submitted for approval (the easiest option).

Another option is have all data fields being marked as either needing to be approved or not needing to be approved (and perhaps this is something that can be exposed as an administrator table - so that this binary option can be adjusted for each data field). Or alternatively (and less desirably in terms of flexibility) is for the workflow to be hard coded to select specific data fields and not others.

Image

@peacog
Copy link
Contributor

peacog commented Jun 6, 2023

@LeScruf Do we want to moderate all types of content? The content that is created manually is:

  • Farmer details
  • Offer/License
  • Sub-area
  • Charge
  • Fee Payment NFA
  • Starting amount
  • Historical payment
  • Land rent rates (we can upload these from a spreadsheet so maybe should not be moderated)

Do data entrants, field officers and field managers enter all of these, or are there some that don't need to be moderated because they are entered by an LMO?

@peacog
Copy link
Contributor

peacog commented Jun 14, 2023

  • Farmer details - No moderation (but if possible a check to prevent duplicates) - Field Officer and Data Entrants
  • Offer/License - Moderation - Data Entrants
  • Sub-area - Moderation (because this impacts land rent) - Field Officer and Data Entrants
  • Charge - No moderation - LMO only (for now)
  • Fee Payment NFA - No moderation - Field Officers
  • Starting amount - LMO / Power user only - No moderation
  • Historical payment - LMO / Power user only - No moderation
  • Land rent rates (we can upload these from a spreadsheet so maybe should not be moderated - LMO only - no moderation)

@peacog
Copy link
Contributor

peacog commented Jun 14, 2023

Hi @Rashids2021 @LeScruf . Can you confirm the following roles/permissions please?

Data entrants are users with one of these roles:

  • Range power user
  • Sector power user
  • HQ power user

When power users create or edit Offer/license and Sub areas they are subject to moderation. Changes must be approved by the LMO.
Power users can create/edit other content without moderation.

We will create an LMO (Land management officer) role with permission to approve and publish the moderated offer licenses and subareas

All other roles, including NFA Staff, Non-staff will have read-only permission on all content types.

Questions
What is a Field Officer?
What is the difference between a field officer and a data entrant?

@ygoex
Copy link

ygoex commented Jun 22, 2023

LMO (Land management officer) > HQ moderator
Field Officer > Sector power user
Field manager > Range power user

We should moderate the farmer details content type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants