Conversation
…x.md, create files restricted-audience.md and discounts.md, move content from index.md there, write intros
…intro and option A
…onal except for add-ons and cross-selling
…onal except for add-ons and cross-selling
…week calendar view
…ng general remarks
| See the article on [check-in lists](check-in-lists.md) to learn more. No newline at end of file | ||
| See the article on [check-in lists](check-in-lists.md) to learn more. | ||
|
|
||
| You can use **custom check-in rules** to place restrictions on the validity of tickets based on time, number of previous entries, ticket type, gate, and other conditions. |
There was a problem hiding this comment.
You can use custom check-in rules to place restrictions on the validity of tickets based on time, number of previous entries, ticket type, gate, and other conditions.
"gate" scheint mir sehr spezifisch. "access location"? "access control location"?
| Enter a name for the new check-in list and check the boxes next to any tickets you want to include on it. | ||
|
|
||
| If you want to implement a use case similar to the example provided above, name the check-in list "Fast lane". | ||
| If you want to implement a use case like the one described under [General usage](#general-usage), name the check-in list "Fast lane". |
There was a problem hiding this comment.
If you want to implement a use case like the one described under General usage, name the check-in list "Fast lane".
Hier, noch mehr als in Z. 58 (basic access tickets), fehlt mir dringend ein "For example, if you want to ..." oder "... a use case like the example described ..."
|
|
||
| Click the :btn:Save: button. | ||
|
|
||
| A merchandise table may seem like a very different use case from a check-in, but a check-in list is still useful for keeping track of who has bought which merch, and who has picked it up already. |
There was a problem hiding this comment.
A merchandise table may seem like a very different use case from a check-in, but a check-in list is still useful for keeping track of who has bought which merch, and who has picked it up already.
Bitte dringend das Wort "preordered" irgendwo einfügen; andernfalls sind wir nicht mehr bei Check-in-Listen, sondern bei POS.
| This is unavoidable due to the flexible nature in which prices are being calculated. | ||
|
|
||
| ### Assigning tax rules | ||
| sp### Assigning tax rules |
There was a problem hiding this comment.
sp### Assigning tax rules
Ohne das sp vorne dran ^^
| If the proposition `∀xP(x)` is meaningless to you, ask a philosopher, a linguist, an electrical engineer, or a programmer. | ||
| Alternatively, contact our support. |
There was a problem hiding this comment.
I just found this by accident because I was looking for the draft docs on this feature, and I don't like this at all. (a) it feels a little condescending, (b) it's perfectly possible to be a great programmer without any training in formal logic syntax and (c) no formal logic syntax is required for the feature.
(Yes, the idea of predicate logic is required, but there are many people who understand predicate logic without knowing that it is called "predicated logic" or what ∀xP(x) is, and scaring them off in the "prerequisites" feels hostile.)
3 participants
How to manage the check-in at your event. Check-in lists and pretixSCAN