More tags for publishing targets, part 2

[saerdnaer]

As of now we only put conference acronym, local frab id and track into the voctoweb tags attribute list.
We should discuss how we get more tags for in individual talk into voctoweb, part 2:
(part 1, see #61)

• add tag for Foundation talks
• use frab's event_classifieres when they reach some specified level (not yet in schedule xml, c.f. Discussion: Expose event classifiers in schedule.xml/.json frab/frab#443 and the orange/blue buttons on https://halfnarp.events.ccc.de
• search title, abstract and description for keywords, c.f. https://github.com/Thorsten-Sick/tags_for_media_ccc_de/blob/master/dropdata.py#L22

[derpeter]

What would be a tag for a foundation talk? Isn't that just a vancy name for an beginner level talk?
In that case i would prefer to use a tag that is not only used by the ccc. If its only a tag nobody will find it execpt the content team. We could think of having somethting like "skill level" as new filed in vocotoweb so we can set it from 1 to 10 where one is "foundation" and 10 "super cyber expert".

Can you tell me more about "use frab's event classfier" i dont get that line.

keyword search sounds interesting, i would ask you to put that into a seperate issue.

[saerdnaer]

@derpeter Could you give an update about the current state of implementation?

[derpeter]

@saerdnaer nothing has changed jet. If you can answer the questions above i will try to give a better answer.

[saerdnaer]

What would be a tag for a foundation talk? Isn't that just a vancy name for an beginner level talk?

Yes and Yes.

frab's event classfier

The speaker can specifiy serveral classfier and select percentage value on that scale:

Which is then displayed in halfnarp,

but not in the schedule.xml. But the other, easier points of the above list, should be implemented first. I can also create a separate Issue, if that helps.

[derpeter]

As we have now target Independent tag propertie we can handle the stuff discussed here globally for all publishing targets.

[Kunsi]

Is the amount of stuff we have in https://github.com/voc/voctopublish/blob/main/voctopublish/model/ticket_module.py#L235-L241 (plus day number, plus target-specific stuff) enough? If yes, i'd vote for closing this ticket.