---
title: "Historic Assay Loader Release Notes"
canonical: "https://servicedesk.maxgeo.com/space/mxAPI/1986396161/Historic%20Assay%20Loader%20Release%20Notes"
format: markdown
---
<details>
<summary>Historic Assay Loader v2.0.1</summary>

### This release is to enhance the Historic Assay Loader (HAL) extension to align with MDS structure.   
  
The enhancement is perfect for long element names as experienced with Hyperspectral data.

**Key Enhancements:**

·        This data has now been set with the following lengths to avoid data truncation.

·        LabElement - 100

·        OrigMethod - 25

·        Element - 25

·        UnitCode - 25

·        GenericMethod - 25
</details>

<details>
<summary>Historic Assay Loader v2</summary>

*This release of Historic Assay Loader (HAL) extension introduces enhancements to support both ODBC and API connectivity for loading assay data into databases.  Some small improvements have also been added.*

**Overview:**

- This release introduces enhancements to the Historic Assay Loader (HAL) to support both **ODBC** and **API** connectivity for loading assay data into databases.

**Key Enhancements:**

- **API Connectivity Support:**
  - Requires an API license and key (issued via DataShed5Admin).
  - New mxAPI endpoint enables POSTing data to tblSYSAssIncoming.
- **Connectivity Options in DBA Tools:**
  - Users can select between ODBC and API.
  - API setup requires URL and API Key, followed by “API Populate” to load necessary libraries.
  - ODBC setup uses “ODBC Populate” after entering ODBC connection details.
- **Assay Management Integration:**
  - HAL can be launched via the ‘Flat Assay’ button or extASS_HistoricLoaderSub form.
  - Some features are disabled in API Connectivity mode and redirect users to DataShed for completion.
- **HAL Extension Behavior:**
  - Displays current connection mode.
  - API mode includes a “Library Refresh” button.
  - “Libraries” tab is read-only in API mode; updates must be made in DataShed, then Refreshed in extension.

**Other Improvements:**

- **File Types:**
  - File Types selection can be "Microsoft Access (*.accdb)" or "Microsoft Access (*.mdb)"
- **Lower Limit BDL Application:**
  - Automation Detection   
When you do not have the Lower Detection Limit checked (Item 6). HAL will automatically derive and apply the lower limits contained in the file with result value <*   
e.g. if value is <0.01 the Lower limit will become 0.01 and the Assay Status will be set to BDL.
  - Manual Detection by element  
If you have the Lower Detection Limit checked (Item 6), it will apply the same Lower Limit specified in the Lower Det entry (Item 8). Limit box to every element being loaded if you are selecting more than one element at once (i.e. not loading element by element)
- **Element Details:**
  - Basic Unit Codes are applied during Populate Element Details.
- **Import Layout Naming:**
  - After file loading the assays loaded will show in DataShed5 within the Historic section of Assay Manager with a psuedo Import Layout Name - "HAL".

**Known Limitations:**

- **Microsoft Access Constraints:**
  - Access databases may grow large and not release space efficiently.
  - Recommended to use “Compact and Repair” regularly and keep backups during use.
</details>