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

Forms Data Entry Operations #25

Open
Patowhiz opened this issue Mar 14, 2024 · 0 comments
Open

Forms Data Entry Operations #25

Patowhiz opened this issue Mar 14, 2024 · 0 comments

Comments

@Patowhiz
Copy link
Collaborator

Patowhiz commented Mar 14, 2024

Overview:

This proposal outlines Climsoft data ingestion process via user-friendly data entry forms, designed to accommodate the varying operational workflows of users like National Meteorological and Hydrological Services (NMHS). It introduces a flexible forms-based data entry system to meet diverse user needs.

User Stories and Scenarios:

  1. User Story 1 (Hourly Data Entry for Multiple Elements):

    • As an observer at an official station, I need to enter data for multiple elements hourly, directly from instruments or record slips.
  2. User Story 2 (Daily Data Entry for a Single Element):

    • As an observer at a volunteer station, I want to enter data for a single element at a specific hour each day.
  3. User Story 3 (Bulk Monthly Data Entry for Multiple Stations):

    • Responsible for data entry across 10 or more stations, I need a system that allows for the input of multiple elements from monthly sheets.
1

Common Data Entry Case Scenarios:

  • Daily or monthly data entry for multiple elements at a specific hour.
  • Daily or monthly data entry for a single element at a specific hour.
  • Synoptic hour data entry for multiple elements, done daily or monthly.
  • Hourly data entry for multiple elements, done daily or monthly.

Proposal for Data Entry Process:

Administrator Responsibilities:

  1. Set Element Thresholds:

    • Define global and, optionally, monthly upper and lower limits for elements to assist in data validation during entry.
  2. Define Data Entry Forms:

    • Create and configure forms that dynamically generate the required metadata for building the entry interface.
  3. User and Station Assignment:

    • Allocate stations to users to allow access rights.
  4. Station and Element Assignment:

    • Allocate elements measured to at the station to stations .
  5. Station and Form Assignment:

    • Allocate forms to be used to enter data to stations.

Dynamic Form Creation:

  • Administrators can craft forms that mirror the physical layout of record slips or return forms at stations by specifying the structure definitions.
1

User Data Entry Workflow:

  1. Station Selection:

    • Users access stations based on their assigned stations.
  2. Form Access:

    • Forms associated with a station are made available to the user, with form accessibility hinging on station form metadata.
  3. Use of Entry Selectors:

    • Users make selections for data entry using controls defined by the form's metadata.
  4. Data Entry Fields:

    • Users input data via fields that are again defined by the form's metadata.
  5. Data Saving:

    • Once data entry is complete, the user can save the data, with the system validating entries against the predefined element limits and other form's validation parameters.
1

Rationale:

The proposed feature addresses the real-world workflows of Climsoft users, like within NMHS organizations, by creating a customizable, role-specific data entry experience that enhances data integrity and simplifies the entry process.

Request for Team Feedback:

Feedback and suggestions from the Climsoft development team are welcomed and encouraged to refine this proposal and ensure that the final implementation meets user requirements effectively.

@Patowhiz Patowhiz changed the title Forms Definitions and Data Entry Operations Forms Data Entry Operations Mar 14, 2024
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

1 participant