|
| 1 | +--- |
| 2 | +layout: docs |
| 3 | +header: true |
| 4 | +seotitle: Generative AI Lab | John Snow Labs |
| 5 | +title: Generative AI Lab Release Notes 6.8.0 |
| 6 | +permalink: /docs/en/alab/annotation_labs_releases/release_notes_6_8_0 |
| 7 | +key: docs-licensed-release-notes |
| 8 | +modify_date: 2024-08-25 |
| 9 | +show_nav: true |
| 10 | +sidebar: |
| 11 | + nav: annotation-lab |
| 12 | +--- |
| 13 | + |
| 14 | +<div class="h3-box" markdown="1"> |
| 15 | + |
| 16 | +## 6.8.0 |
| 17 | + |
| 18 | +Release date: **11-15-2024** |
| 19 | + |
| 20 | +## Easy Migration to Generative AI Lab - 6.8 |
| 21 | +Generative AI Lab 6.8 introduces new features designed for users migrating from NLP Lab onto the newest version of Generative AI Lab. With the new Backup and Restore feature, you can transfer projects, annotated data, models, and configurations to the Generative AI Lab 6.8 and above. Simply back up your projects and resources to cloud storage services like Azure Blob or AWS S3, then restore them directly into the new environment, entirely through the user interface. |
| 22 | + |
| 23 | +This release also introduces other small enhancements to existing features, including a “None” option in the de-identification dropdown, allowing you to label text without altering the original content. We’ve also added a helpful visual indicator for labels with associated annotation guidelines—now marked with a colored dot matching the label’s color. |
| 24 | + |
| 25 | +## Migrate your NLP Lab Backup to Generative AI Lab |
| 26 | +Migration to the new version is now a seamless process. Users of the NLP Lab can transfer their models, projects, annotated data and configuration settings to the Generative AI Lab using our Backup and Restore feature. Once backed up, configurations can be easily restored to a Generative AI Lab server. To migrate your data, the process is as follows: |
| 27 | + |
| 28 | +### Steps to Backup Data from NLP Lab |
| 29 | +1. **Login** to your current NLP Lab deployment as the admin user. |
| 30 | +2. Go to the **`System Settings`** page. |
| 31 | +3. Navigate to the **`Backup`** tab. |
| 32 | +4. Enter the required **backup details**. |
| 33 | +5. Schedule an immediate backup using the **`Backup now`** feature. |
| 34 | +6. Monitor the **backup pod status** to ensure the process completes successfully. |
| 35 | +```bash |
| 36 | +kubectl get pods |
| 37 | +``` |
| 38 | +**Verify Backup:** Upon completion, your backed-up database and files will be visible in cloud storage. |
| 39 | + |
| 40 | +<iframe width="800" height="450" src="https://www.youtube.com/embed/wUiDq5peZK4?si=v2Q6XCtK01KmcKJa&hd=1" title="NLP Lab to Generative AI Lab migration - Step 1" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> |
| 41 | + |
| 42 | +### Steps to Restore Data |
| 43 | + |
| 44 | +1. **Deploy** a fresh instance of Generative AI Lab version 6.8.0 or higher from the marketplace. |
| 45 | +2. **Login** to the UI as the admin user. |
| 46 | +3. Go to the **`System Settings`** page. |
| 47 | +4. Click on the **`Restore`** tab and fill in the necessary details. |
| 48 | +5. Click on **`Restore Now`** to initiate the process. |
| 49 | +6. Monitor the **restore pod status** to ensure successful completion. |
| 50 | +```bash |
| 51 | +kubectl get pods |
| 52 | +``` |
| 53 | + |
| 54 | +**Verify Restoration:** Access the UI, all projects, models, data and files should now be successfully restored. |
| 55 | + |
| 56 | +<iframe width="800" height="450" src="https://www.youtube.com/embed/8JihFXLfHGc?si=hczRk74snB9cP8Es&hd=1" title="NLP Lab to Generative AI Lab migration - Step 2" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> |
| 57 | + |
| 58 | +## Improvements |
| 59 | +### Exclude Labels from De-identification |
| 60 | +Generative AI Lab 6.8 introduces a `None**` option in the de-identification selection dropdown. When selected, this option will only label the text without performing any de-identification. This provides users with greater flexibility by allowing them to annotate the text while leaving the original content intact. |
| 61 | + |
| 62 | + |
| 63 | + |
| 64 | +### Mark the labels with annotation guideline |
| 65 | +A new enhancement has been introduced to easily distinguish labels with annotation guidelines. Labels that have associated annotation guidelines are now marked with a colored dot at the top-right corner. This feature applies to both NER and VisualNER projects. If the annotation guidelines are deleted for a label, the dot will be automatically removed. |
| 66 | + |
| 67 | + |
| 68 | + |
| 69 | +### Change the pop-up message when the model downloading is canceled |
| 70 | +The pop-up message that appears when a model download is canceled has been updated for better clarity. Previously, the message displayed the title `Warning: Delete Model?`, which could confuse. It has now been changed to `Warning: Cancel Model Download?` with a more accurate description. This update provides clearer communication to users when they choose to stop a model download in progress, improving the overall user experience. |
| 71 | + |
| 72 | + |
| 73 | + |
| 74 | +### Improvements in XML editor |
| 75 | +The issue of overlapping parent option buttons and top child option buttons when hovered, specifically when the `Show parent action buttons on hover` option was enabled, has been resolved. This fix provides a more polished user experience by ensuring the buttons are properly aligned. Now, the buttons no longer interfere with each other, offering smoother interaction with the interface. |
| 76 | + |
| 77 | + |
| 78 | + |
| 79 | +Tooltips have been enhanced to display the correct tag name for each section, improving the usability of the XML editor. Previously, the tooltip and the menu name that appeared on hover were identical for each container, making it difficult to distinguish between them. With this update, each container now has a unique tooltip, ensuring that users can easily identify where they clicked. For example, `Edit Tag` has been updated to `Edit Text Tag` to provide clearer context and improve navigation within the editor. |
| 80 | + |
| 81 | + |
| 82 | + |
| 83 | +A validation error is now triggered when quick filters are incorrectly attached to elements other than labels or ellipse labels. |
| 84 | + |
| 85 | + |
| 86 | + |
| 87 | +The `Maximum rating value` of the `Rating` element now includes validation. A red color warning is displayed when an invalid value is entered. Only positive numbers are allowed, ensuring that users input appropriate values and improving the overall accuracy of ratings. |
| 88 | + |
| 89 | + |
| 90 | + |
| 91 | +### Increased readability for test cases view |
| 92 | + |
| 93 | +Users can now read the test cases better with two-tone text distinguished between test types. |
| 94 | + |
| 95 | + |
| 96 | + |
| 97 | + |
| 98 | +### Bug Fixes |
| 99 | +- **Annotation guidelines now visible in the horizontal layout** |
| 100 | + |
| 101 | +Users can now see Annotation guidelines in the horizontal layout. |
| 102 | + |
| 103 | + |
| 104 | + |
| 105 | +- **Confidence score of classifier is only shown for the first section in SBA text task** |
| 106 | + |
| 107 | + The confidence score is now correctly displayed for predictions across all sections, ensuring consistent feedback throughout the entire task. |
| 108 | + |
| 109 | + |
| 110 | + |
| 111 | +- **Toast Message-warning users of Expiring License with each API call** |
| 112 | + |
| 113 | + The issue with frequent toast message pop-ups has been largely resolved. However, the message may still reappear when the user refreshes the page or navigates to different sections. While the message is now less intrusive, it is still visible during certain actions such as page reloads or navigation. |
| 114 | + |
| 115 | +- **File Backup is uploaded to the DB file backup path** |
| 116 | + |
| 117 | + Users can now successfully designate different paths for ad-hoc backing up databases and files. The system will correctly store database ad-hoc backups in the specified database path, while file ad-hoc backups will be saved in their intended separate location. |
| 118 | + |
| 119 | + |
| 120 | +</div><div class="prev_ver h3-box" markdown="1"> |
| 121 | + |
| 122 | +## Versions |
| 123 | + |
| 124 | +</div> |
| 125 | + |
| 126 | +{%- include docs-annotation-pagination.html -%} |
0 commit comments