textcat: 2-level hierarchical classification

[ryanwesslen]

hi @blue482!

Thanks for your question! This is a good question.

First, it is important to note that (see the docs):

Multiple blocks of the same type are only supported for the text_input and html interface. For text input blocks, you can use the "field_id" to assign unique names to your fields and make sure they all write the user input to different keys. For HTML blocks, you can use different "html_template" values that reference different keys of your task.

[
  {"view_id": "text_input", "field_id": "user_input_a", "field_rows": 1},
  {"view_id": "text_input", "field_id": "user_input_b", "field_rows": 3},
  {"view_id": "html", "html_template": "<strong>{{content_a}}</strong>"},
  {"view_id": "html", "html_template": "<em>{{content_b}}</em>"}
]

So blocks of the same type (i.e., choice / categories), can't be used.

However, this post outlines how to create a simple HTML template (which can be duplicated in blocks) with a checkbox and a small JavaScript script that listens to the checked event of the box and updates the task with whether it's checked.

Asking multiple questions in one task (different input types)

Hi! That's an interesting question Since you can only have one instance of an interface per task (because the data would overwise get messy and have conflicts), I would probably do something like this: blocks = [ {"view_id": "choice"}, {"view_id": "html", "html_template": HTML_TEMPLATE, "javascript": JAVASCRIPT}, {"view_id": "text_input"} ] For the choice block, your task could specify a list of "options" that's displayed. For the html block, you could hav…

If you use multiple check boxes, I think it's possible to do something very similar to the multi-level example you showed.

There's an example recipe in that same chain that can get you started:

Asking multiple questions in one task (different input types)

Hi @ines , thanks for your timely reply! Given your code, I got two follow-up questions: If the HTML checkbox is checked in one task, it will also be checked in the next tasks, so users will have to manually click or unclick it every time. I tried to unset it using some simple javascript (see recipe below), but this does not work. Perhaps because the javascript is executed only once when the webapp is started up? What would be a suitable spot do unset the checkbox? EDIT: It seems the js-code …

Can you take a try?

We'd be interested if you're able to make any progress!