Term |
Definition |
Action |
See Permission Action. |
Applies To |
Defines the list of users that are will affected. This list is overruled by the Does Not Apply To list. ie. If a user is in both lists then the Does Not Apply To is used. |
Approved Booking |
A Calpendo booking whose status is approved. |
Approved User |
|
Bakery |
An editor which allows the user to create, delete and update BiskitDefs and their properties. The Bakery also allows editing of Mapped Strings, Mapped Integers and Units. |
Biskit |
A Biskit is an object stored in the database that has a custom type. It will have whatever properties are specified by its BiskitDef. |
BiskitDef |
Defines the properties associated with a particular type of Biskit and how those properties should be stored in the database. |
Biskit Type |
Each Biskit has a type. Biskits with the same type, have the same property definitions. See BiskitDef. |
Bit Set |
A Bit Set is a type of integer property that results in a drop-down that can take multiple values. |
Booker |
A Calpendo concept defining which user has made a particular booking. |
Booking |
A Calpendo concept of a reservation of a resource at a particular time. |
Bookings Calendar |
A Calpendo page which provides a graphical view of bookings by day, week or month. |
Booking Rule |
A Calpendo concept, setting up restrictions relating to which bookings can be made. |
Booking Status |
A Calpendo concept that shows the condition of the booking. |
Booking Type |
A user-defined Booking taxonomy. |
Bookmark |
A Calpendo concept defining a collection of resources to be displayed in the Bookings Calendar. |
Condition |
Allows the user to specify under what circumstances an action such as generating an email, granting or refusing permission etc. will occur. Conditions work logically together using information from the database to reach a True/False result. |
Data Explorer |
A page that shows Biskits. |
Data Type |
See Biskit Type. |
Does Not Apply To |
Defines the list of users that an operation (Rule, Permission etc) will not affect. This list overrules the Applies To list. ie. If a user is in both lists then the Does Not Apply To is used. |
Event |
A point in time when a task needs to occur. These may be such things as filling in forms, setting up appointments or phoning a subject. An event has a status, may be allocated to a specific user or user group and may have some sub tasks. |
Events Calendar |
A page which provides a graphical view of events by day, week or month. |
FAQ |
Frequently Asked Questions, this page lists the FAQ's for the facility. |
Follower |
A task whose time and/or status is affected by the time or status of another task. |
Global Preferences |
Specifies settings that change the way Exprodo SDM operates. |
Group Report |
A report that lets you break down data by any number of properties. |
History |
The audit log kept by Exprodo SDM that shows what has been changed, when and by whom. |
Jobless |
A task that is used as a holder with no actual work required. |
Layout Editor |
The Layout Editor allows the user to define how the properties of a Biskit will be displayed. |
List Report |
A report that shows a list of Biskits. |
Mapped Integer |
A Mapped Integer relates text labels to integer values. An integer property on a Biskit may use a Mapped Integer so that a user would see a drop-down with each of the text labels when they edit it. The related integer value is stored in the database rather than the text. See also Bit Set. |
Mapped String |
Similar in concept to a Mapped Integer, but instead of storing an integer in the database, a text value is stored instead. This means that a Mapped String is an association of one set of strings to another set of strings so that you see a drop-down of text values, but the value stored in the database does not have to be the same as the displayed value. |
Meta-Property |
1) Attributes that define how a Biskit or a Biskit's properties work. 2) A type of property used in Conditions when you want to specify a relation about who performs an action or when. |
Network Metrics |
A record of how long communications between web browsers and the Exprodo SDM server take. |
Nobody |
A special user used for Permissions to control what information may be written into emails. |
Owner |
A Calpendo concept defining who owns a booking, bookmark or project. |
Permission |
How the administrator determines which user may have access to what information and under which circumstances. Permissions may have many layers allowing fine grained control over who can perform what action on which Biskit. |
Permission Action |
An operation that can be performed on a Biskit. The most common actions are Create, Read, Update and Delete. |
Process |
A means of editing a Biskit in multiple steps |
Project |
A Calpendo concept, a project allows an administrator to link together users, resources and costs. |
Project Group |
A Calpendo concept grouping similar projects together for use in Rules, Permissions, Time Templates or Automatic Emails. A project may belong to many groups. See also Project Type. |
Project Resource Settings |
A Calpendo concept creating a list of resources that a project may use with project specific information for that resource. |
Project Status |
A Calpendo concept showing the current status of a project. This can be Requested, Approved, Denied, Unbookable or Terminated. |
Project Type |
A Calpendo concept grouping similar projects together. A project has only one type. See also Project Group. |
Property |
An individual piece of data attached to a Biskit. A property will have a name, a type and a label as well as other meta properties defining how it is organised. |
Property Path |
When adding a property to a report, or placing a condition on a property, you can choose a property of a property. This is known as a property path. For example, if you want a Permission to prevent creating reports that are scheduled to run daily, you would need a condition on the the report schedule's repeat type. This is found in the property path reportSchedule.repeat.repeatType. |
References |
Biskit properties may have various types, such as integer and string. One such type is Biskit, which means that a Biskit may reference another Biskit. The References for a Biskit is the list of all such referencing Biskits. |
Relation |
Provides a means of comparing the value of a property to another value e.g. equals, less than etc. |
Repeat |
|
Requested Booking |
A Calpendo concept of A booking that has been created but not yet approved. |
Resource |
A Calpendo concept, defining a room, person, instrument, or anything else that that must be booked before it can be used. |
Sequence |
A set of related tasks to be completed over a time period. |
Settings |
See User Settings. |
Single Item Report |
Shows a report of a single item of the appropriate Biskit Type. |
Subject |
A person, animal or object that you are studying. Each subject will have a (potentially large) number of properties to store gathered information. The subject may also have a sequence associated with it. |
Summary Report |
A report like a spreadsheet pivot table that can automatically count or sum data. |
System Event |
Various things that happen within Exprodo SDM are recorded as a System Event. For example, a system event is recorded each time an email is sent or an error is detected. |
System Usage Statistics |
These are statistics that may optionally be kept to track how much each user has been using Exprodo SDM. |
Task |
An individual action that needs to be performed. See also Event. |
Time Accuracy |
An indication of how accurate the timing of a task is. |
Time Template |
A Calpendo concept allowing an administrator to assign an acceptability rating to bookings depending on when they are booked, who makes the booking and the project the booking is for. |
Trigger |
|
Units |
A method of displaying different measurement types such as feet and metres. |
User Approval Process |
|
User Group |
A way of grouping similar users together. A user may belong to many groups. See also User Type. |
User Project Association |
A Calpendo concept which contains a list of projects the user is associated with. |
User Roles |
Users may be assigned roles, and then Permissions can be configured to use those Rules. For example, by default, users with the Admin role can modify more things than users without the Admin role. |
User Settings |
Specifies settings that change the way Exprodo SDM operates for this user. These will override the Global Preferences. |
User Status |
The current status of the users account. This may be one of Requested, Normal, Password must be reset at next login, Blocked or Denied. |
User Type |
A way of grouping similar users together. A user has one type. See also User Group. |
Workflow |
A way of automating additional functionality in Exprodo SDM. |
Workflow Action |
|
Workflow Event |