This article outlines the major enhancements introduced to MX Deposit as part of an update performed on Jan. 15, 2018.
MX Deposit now fully supports point data in the new Points module.
Notes about points:
- Headers are now categorized by either "drilling" or "point" headers (hole number vs. point number)
- Header fields (and associated lists) can be shared across drilling and point headers
- Activities are now categorized by either "drilling" or "point" activities
- A point activity can only use a point header
- A point activity can use any table (there is no point vs. drilling in tables)
- Point activities use all the same sampling options as drilling activities (sample type, control types, etc.)
- Projects can contain both drilling and point activities
- All existing data management modules (import, export, project summary, home feed) are extended to include point data
- Points are also available in the MX Deposit mobile app for offline data entry
If you have any questions about the new point module or are curious how it could be applied to your project, please contact support at email@example.com.
Data table type
Tables can now be designated as interval or depth (current options), or with the new "data" table option. The main difference is that a data table has no interval or depth association (no from/to or depth columns). The primary purpose of data tables is to support the new Point module, but data tables can also be used in drilling activities if desired.
A new "create rows" feature is available to auto-create rows to a set depth. This can be useful in scenarios where the interval length remains the same (e.g. RQD, core boxes, etc.) up to a set depth.
How to use it:
In the web app, click on the "more" button (...) on the table status bar, and select the "Create rows" option in the menu.
A dialog will appear with the required parameters to create new rows.
The Start depth defines where the intervals will begin, the End depth defines where the intervals will end, and the Interval length defines the length of each interval. For the end depth, you can alternatively choose to use the [Target depth] value on the Header to determine where the intervals should end. NOTE: if no [Target depth] value has been entered in the Header - this option will not appear.
Once you have entered all required parameters, click the Create rows button and the new rows will be created. Any columns that have default values defined will be populated with the default value.
Web app improvements
Tables can be given a label that is different from the table name. The label is what is displayed to the user in the data entry screens. This can be particularly useful for organizing tables across projects, or when using child tables.
By default, the table label will be the same as the table name - but you can change the table label at any time to something more user-friendly. The table label will also be used when exporting data.
Export files option
Users now have the option to include files when performing a bulk export. If this option is enabled, all files for the selected list of holes will be included in the export .ZIP file.
A folder will be created for every hole (or point) that has associated files, and within each folder, two sub-folders will be created named "Attachments" and "Photos" (the difference between image files and everything else). The filename for every file is also derived based on the hole (or point) number, the table + column + interval, and finally the existing file name. This is done to ensure uniqueness across files, and to provide context for each file.
Activity logging options
The following new options are available in the Logging step of the Activity configuration screen:
"Auto create rows for new drill holes"
This feature can be used to pre-populate intervals based on known interval lengths (and depths). When you enable this option, some additional options appear to control the behaviour:
These parameters determine where the pre-populated intervals should start (start depth), where they should end (end depth), and what the interval length should be. You can also choose to use the target depth value in the header as the end depth.
If this option is enabled, the create row function will be triggered when a user clicks the "start logging" button. If any default list values have been set, they will be used for the pre-populated rows.
"Limit entry to single row"
This feature can be used to limit entry in a table to a single row of data. This might be useful particularly in point activities where you want to limit observations to a single row, but could also be used for drilling activity tables used to capture supporting information (project info, drill hole info, etc.).
Activity sampling defaults
It is now possible to designate a default sample type and a default control type to be used when creating new samples. This can be used in conjunction with the new "auto create rows" feature so that the pre-populated rows have the correct sample type value.
Landing screen layout
The height of the list card items has been reduced to allow for more objects to appear on the screen:
Also, all right-click actions and the "Go To" menu option have been consolidated into a new "More" button represented by three dots "..." when you rollover one of the list items:
Sample type and status breakdown
Both the sample dispatch and lab certificate landing screens now provide a breakdown of the various sample types and status options to give an overview of what's included in the dispatch or certificate. The main view now shows a count of how many samples are in each certificate or dispatch. If you click on the "x samples" link, the card will expand and show a breakdown of samples by type and by status.
The main search bar at the top of the screen is now case-insensitive (e.g. entering "dd" will find holes named "DD" or "Dd" or "dd").