datasets

Hi! I've noticed the doc references postgres for setting up data storage (https://labelstud.io/guide/storedata.html). However, I was wondering whether it's possible to switch to other databases such as MySQL for the same task. If so, more or less how'd the process be? I'm trying to set up label-studio and the environment I'm using only allows MySQL DBs.

Thanks!

How to reproduce the behaviour

The error occurs in the Step 5/9 of the docker build process

fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz: BAD signature
WARNING: Ignoring http

🚨🚨 Feature Request

We need description, citation, license, and version meta info to be added to the dataset.

Is your feature request related to a problem?

Some datasets need this info inside them for legal reasons.

If your feature will improve HUB

Easy to implement, won't hurt for sure.

Description of the possible solution

Currently, we have all metadata store

Describe the event source. What app is this for, and what event does the trigger correspond to?
Slack's API exposes access activity like logins. It's useful sometimes to trigger off of someone's first login to run some welcome actions or log the activity in a database elsewhere. It will probably require some polling, but we could hit the team.accessLogs endpoint periodically to see if anyon

References

• https://www.itu.int/dms_pubrec/itu-r/rec/bt/R-REC-BT.2124-0-201901-I!!PDF-E.pdf

Issue to track tutorial requests:

• Deep Learning with PyTorch: A 60 Minute Blitz - #69
• Sentence Classification - #79

What?

Currently, API manually throws its own messages and errors. We should move them to werkzeug exceptions.