Data collection via data browser (EBS)
Domain | Core Breeding |
|---|---|
Tool | Data Collection |
User Type | Member, Non-member |
Role | Team Member, Data Collector |
Once users have collected data through their preferred data collection tool, such as Field Book or a spreadsheet file, it is important to save it as a properly formatted data file, such as CSV format.
The Data Collection tool’s data browser serves as a vital interface for uploading, viewing, and committing raw data, systematically categorized as transactions. The browser consists of three main parts: the (1) topmost section, (2) table headers, and (3) table of transactions.
Topmost section
The (1) topmost section hosts the main toolbar with the tool’s main functionalities. Users are also notified about the number of items displayed in the browser and the number of selected items.
| Variable | Functionality |
|---|---|---|
a. | Page title | Displays the tool name as the page title (e.g., “Data Collection”) for clear user orientation. |
b. | Page Description | Provides a summary of the tool’s core functionality displayed in the active window. |
c. | Toolbar | Hosts the essential icons and action buttons, enabling users to efficiently plan out their experiments. |
d. | View Item Count Summary | Displays the total number of occurrences currently visible in the browser. |
Table headers
The (2) table headers provide users with search, filter, and sorting functions, facilitating efficient access to relevant transactions.
By default, users can see all uncommitted transactions (transactions with uploaded status). To view all transactions, remove the filter under the Status column.
Check out this infographic to review the transaction statuses.
Transactions Table
The (3) Transactions table presents the actual data entries in an organized format. This design ensures that users can efficiently access, interpret, and manage their data.
| Variable | Functionality |
|---|---|---|
a. | Status | Measures the experiment’s overall progress by tracking how user actions within each occurrence affect its status. |
b. | Location Name | Designates the name of the operational unit used to organize and manage occurrences, whether they are created automatically or by users. It doesn’t necessarily represent a geophysical place, but it helps track, group, and control occurrences |
c. | Occurrence Name | Assigns a distinctive name to each occurrence, whether automatically generated or manually customized by users, to ensure clear identification and streamlined tracking. Users can click the occurrence name to view its information in Experiment Manager. The dropdown button also expands to view the collected trait variables. |
d. | Uploader | Designates the individual who uploads the raw data into the Data Collection tool, ensuring accountability and traceability throughout the data management process. |
e. | Uploaded Timestamp | Captures the exact date and time at which the raw data is uploaded into the Data Collection tool. |
f. | Committer | Designates the individual who conducts the quality check and finalizes the raw data within the Data Collection tool, upholding data accuracy and ensuring the reliability of the finalized dataset. |
g. | Committed Timestamp | Captures the exact date and time at which the raw data undergoes quality checking within the Data Collection tool. |
h. | Origin | Notifies users of the source from which raw data is recorded, whether through the upload of a template file or via integration with external data collection devices such as Field Book or Hiphen. |
i. | Remarks | Displays the remarks entered by users during the quality checking process, such as suppression notes or validation comments. |
Great job! What to do next?
Continue navigating the tool and exploring its functionalities
Ready to upload a new dataset?
Need to upload time-series data?
Need to record post-harvest data?
Need to manage the open and committed transaction?