10 The state in which a resource is public, regardless of the status
11 that is inherited from the parent resource.
14 Ideas or summary of a presentation/contribution, often assigned to
15 a track. Once accepted becomes a contribution.
18 A register, associated with a user, and that enables him/her to
19 authenticate his/her identity. Indico supports local accounts (no
20 longer used at CERN) and NICE accounts (centrally registered at
21 CERN, and authenticated through SSO).
24 An "Avatar" is a representation of a user in the Indico database.
25 It usually contains all the user's personal info (that is extracted
26 from the NICE database the first time the user logs into Indico).
27 These data can be explicitly modified by the user. An Avatar is
28 normally associated with one or more accounts.
31 A pause in the schedule of a meeting/conference. Breaks can be
32 placed inside sessions/slots or at the top level.
35 A container for events. Categories can contain either other
36 categories (sub-categories), or events, never both at the same
37 time. The category hierarchy of Indico resembles a tree where
38 categories that contain events are the "leaves".
41 Cloning a meeting means replicating it (with the exact same
42 information) on a diferent date. This is normally useful for series
43 of meetings whose participans and/or contents don't change
47 The most complex kind of event, containing the same as a meeting,
48 plus support for registration, abstract management, and other
49 features that are specific to this kind of event.
52 Usually a presentation taking place within a session or slot.
55 A poll, that is conducted normally after an event takes place, so
56 that the organizer can gather feedback about it. It can be applied
57 to any event, and the results can be exported as stylesheets.
60 An event is either a Lecture, Meeting or Conference.
63 In the context of Indico, this is a resource that links to a
64 physical file, contained in Indico's "archive". Files are stored
68 A presentation, normally done by one or more speakers. It doesn't
69 contain any "substructures" such as contributions.
72 In the context of Indico, a Link is a resource that links to some
73 other resource on the Web, specified by a URL. Links exist inside
77 A Material is a container for Files and Links, it groups resources
78 of the same nature (i.e. slides, documents, drawings...). Materials
79 can be attached to Categories (quite rare), Events, Sessions,
80 Contributions and Subcontributions.
83 A kind of event that implies some degree of participation from
84 different participants, over different topics (Contributions).
85 Contributions can be placed into Sessions, for better organization.
86 Slots can also be used, but they are disabled by default.
89 Minutes are annotations produced by participans in a meeting. They
90 can be associated with Meetings, Sessions, Contributions and
94 A status in which a resource cannot be accessed by users that do
95 not accomplish certain criteria (i.e. being in a list, or coming
96 from a specific IP domain...).
98 Restricted by Inheritance
99 A status in which an resource is private just because its parent
100 resource was set as private (either by inheritance, or
104 A status in which a resource is publicly accessible, with no
105 constraints. This status can be overriden, if the parent resource
106 is set as private (see Restricted by Inheritance).
109 In the context of this document, a Resource is a category, event
110 (lecture, meeting or conference), session, contribution,
111 subcontribution, material, link or file. It is basically any
112 information-bearing object in Indico's domain.
115 A time slot to help organise your conference timetable. Can contain
116 slots, contributions and breaks.
119 A session can be split into slots, can be used when the session
120 happens over more than one period of time. Can contain
121 contributions and breaks.
124 A subdivision of a contribution.
127 Tracks define the main divisions/topics of your conference. You can
128 attach contributions and abstracts to tracks.
131 In the context of Indico, Visibility usually refers to the extent
132 to which an event can be seen in the event overview page. This
133 attribute sets whether the event can be seen as belonging to the
134 top level class (and all those below), to none of them (invisible),
135 or to one of the intermediate classes (and all those below).