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

PLSS app - define review process #40

Closed
nathankota opened this issue Apr 12, 2023 · 2 comments
Closed

PLSS app - define review process #40

nathankota opened this issue Apr 12, 2023 · 2 comments
Assignees
Labels
carried forward This task was carried forward into the next quarter paying This issue earns $$

Comments

@nathankota
Copy link
Contributor

nathankota commented Apr 12, 2023

PLSS: Public Lands Survey System

Benefit

Once a PLSS monument record is submitted through the Utah PLSS app, define the next steps to occur within the app for county and UGRC staff to review and ultimately publish the submitted monuments.

Acceptance Criteria

A plan for the next development cycle to fulfill the review process.

Notes

Old Miro board

Risks

  • Clearly defining the review steps
  • Keeping the review process simple to make development manageable
  • Time among other duties

ref: #445

@nathankota nathankota converted this from a draft issue Apr 12, 2023
@nathankota nathankota changed the title PLSS app - review process PLSS app - define review process Jun 3, 2024
@steveoh steveoh added the paying This issue earns $$ label Sep 3, 2024
@DenisePeterson DenisePeterson added the carried forward This task was carried forward into the next quarter label Sep 25, 2024
@steveoh
Copy link
Member

steveoh commented Oct 30, 2024

Adding the process states and mockups lucid documents.

Adding some notes from August

Plan is to move forward with the states up until the blm inclusion with a url like plss-review.ugrc.utah.gov or monument-review.ugrc.utah.gov

  1. show the submissions
  2. allow them to be selected to view the pdf and place on the map
  3. allow them to be approved or rejected with app status update
  4. send them to the counties with status update
  5. after 10 days move them to public location and edit feature service with status update

We’re now waiting for pi planning around october 1 with possible manual run throughs sooner

@seanfernandez
Copy link

This task needs to be moved forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carried forward This task was carried forward into the next quarter paying This issue earns $$
Projects
Status: Done
Development

No branches or pull requests

4 participants