• Products
  • Solutions
  • Company
  • Resources
  • Docs
  • Pricing

Kili Technology Changelog: March 1st, 2023

We're happy to introduce the changelog of our latest release! Discover what has been launched, updated or fixed on Kili technology these past two weeks.

Kili Technology Changelog: March 1st, 2023
kili face


[Python SDK] We’ve added created_at_gte and created_at_lte arguments to the kili.assets() method. You can use these arguments to filter assets based on their import date in the app.

[Python SDK] Now you have more available filters when accessing your issues programatically: we’ve added new arguments to the kili.issues() and kili.count_issues() methods:issue_type, status, asset_id and asset_id_in.

[Python SDK] We’ve added a new method: kili.data_integrations(). You can use it to get a list of existing data integrations (cloud storage) of an organization.

kili face


[Labeling] In Text projects, to improve the overall content readability:

  • We’ve added padding on all the sides of the interface,

  • We’ve increased the font size to 16px,

  • We’ve added line breaks word breakpoints, to make sure that words are not truncated.

[Labeling] Changing the class of an annotation from the asset viewer used to remove all the values of the existing subjobs for that annotation. We’ve changed this behavior. Now, if you change the class on an existing annotation the contents of existing subjobs will get transferred to the new class.
Consider this example: You have several available car classes, each one of them with the same list of subjobs, like the transcription of a license plate, a single-choice subjob for engine type and so on. You can now change the car class without actually losing any of your completed transcriptions or selections.
Some conditions apply, though:

  • The instructions must be the same

  • The list of possible values must be the same

  • Types of subjobs (for example single-choice or multi-choice classification) must be the same
    Note that if only some of the subjobs meet all of these criteria, their contents will still get transferred.

[QA] When you access the labeling interface, the issue/question panel is open by default when any open issues or questions exist. This way, you’re less likely to miss any new information.

[QA] We’ve changed how resolved issues are presented in the Kili app. You’ll be able to find the information that you’re looking for with fewer clicks.

[Signup] We’ve simplified the signup process for new users:

  • Some of the fields may get automatically pre-filled for you.

  • At the end of the signup process you’re directed to a new page with useful off-the-shelf project templates that you can reuse.

[QA] When open, the Comments and issues pane used to occlude a part of the asset, making it hard to complete some of the labeling tasks without closing this pane or resizing the asset manually. We’ve changed it now: when the Comments and issues pane is opened, the asset gets automatically re-scaled to fit on screen.

[Python SDK] We’ve added two new methods: kili.create_issues() and kili.create_questions() . You can use them to create several issues or questions at the same time. The kili.append_to_issues() method is now deprecated.

kili face


[Labeling] In the thumbnails view, GeoTIFFs were not being displayed properly. We’ve fixed this issue.

[Python SDK] After exporting a project to the COCO format by using the SDK, in the resulting file, the format of the bbox field did not meet the COCO format specifications. We’ve fixed this bug.

To deep dive into the new changes, go read our documentation.

Continue reading
Get started

Get Started

Get started! Build better data, now.