[Feature Request]: Study Area Data Entry
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Background
Populate study area attributes with relevant information such as study authority(s), the district executing the study, and the NFS
User Story
PTL will add the required study area attributes and all the information required.
Purpose
Define study area, & planning reach boundaries and study details.
Workflow
Roles include:
- PTL
Workflow
No response
Requirements
No response
Misc. Notes
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, tests, or entry points are named. Start by identifying where study-area data entry is implemented and clarify the required attributes, authority and district fields, NFS meaning, and boundary workflow with the project team. Done means PTL can enter and save the agreed study-area information.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100