System use case specification view specimen data change requests - ESG-Project/documentation GitHub Wiki


Identification	UC31
Use case	View Specimen Data Change Requests
Actors	Administrator, Moderator
Stakeholders and interests	Data Administrator: Needs to efficiently track and manage all pending data modification requests for quality control.
Pre-conditions	The Administrator/Moderator is logged into the system. There are change requests pending review.
Minimum guarantees	System displays an empty list or appropriate message if no requests are found.
Success guarantees	A sortable and filterable list of all specimen data change requests is displayed for review.

Main Success Scenario

User Action	System Response
1. This use case begins when the Administrator/Moderator accesses the dedicated section for managing change requests (e.g., "Data Review" or "Change Requests").	2. The system retrieves all pending, approved, and rejected specimen data change requests from the database.
	3. The system displays a table listing all change requests. Columns include: Request ID, Affected Specimen ID, Species (current and proposed), DBH (current and proposed), Height (current and proposed), Requesting User, Associated Phytosociological Analysis, Request Date, Status (Pending, Approved, Rejected), and User Comment.
4. The Administrator/Moderator can filter the list by status, requesting user, or associated analysis. They can also sort the list by any relevant column.	5. The system dynamically updates the displayed list based on the applied filters and sorting.

Displayed Information: List must include Request ID, Specimen ID, current and proposed data (for changed fields), Requesting User, Date, Status, and Comment.
Filtering: List must be filterable by status, user, and analysis.
Sorting: List must be sortable.