System use case specification import specimens in batch - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
|
|
| Identification |
UC27 |
| Use case |
Import Specimens in Batch |
| Actors |
User |
| Stakeholders and interests |
Forest Inventory Analyst: Needs to efficiently upload large volumes of field data collected offline, saving manual entry time. |
| Pre-conditions |
The user is in the "Species Data" section of an active Phytosociological Analysis (UC24 has been executed). The user has a spreadsheet file (.xlsx or .csv) containing specimen data. |
| Minimum guarantees |
System provides clear error reporting for invalid data rows. |
| Success guarantees |
Valid specimens from the uploaded file are successfully added to the Phytosociological Analysis. |
Main Success Scenario
| User Action |
System Response |
| 1. This use case begins when the user accesses the "Batch Import" functionality in the "Species Data" section. |
2. The system displays the batch import interface, offering an option to download a standard template. |
| 3. The user (optionally) downloads the standard template, fills it with data, and saves it. |
4. The user selects their prepared file (.xlsx or .csv) for import. |
| 5. The user initiates the import process. |
6. The system processes the uploaded file, performing validations on file structure (columns and order), data types, data ranges, and mandatory fields for each row. |
|
7. If errors are detected in any rows, the system displays a detailed list of errors (e.g., "Error on line 5: Species missing", "Error on line 10: Height value invalid"). |
| 8. The user reviews the errors and chooses to either correct the file and re-upload, or proceed by importing only the valid data. |
9. The system imports only the rows with valid data, adding the new specimens to the current analysis. |
|
10. The system confirms the successful import of valid specimens and informs the user about any skipped invalid rows. |
Alternative Flows
7a. Invalid File Format/Structure
| User Action |
System Response |
|
1. The system detects that the uploaded file is not in .xlsx or .csv format, or its structure (e.g., column headers) does not match the expected template. |
|
2. The system displays an error message indicating the file format or structure issue. |
| 8. The user corrects the file and re-uploads. |
9. The system re-processes the corrected file and returns to step 6 of the Main Success Scenario. |
Special Requirements
- Supported Formats: Accepts .xlsx and .csv files.
- Template Provision: A standard template with mandatory columns must be available for download.
- Comprehensive Validation: Validates file structure, data types, ranges, and mandatory fields.
- Detailed Error Reporting: Provides specific error messages (e.g., line number, reason).
- Partial Import Option: Allows importing valid data even if some rows contain errors.
Related Documents