General glossary

Description of the different terminology used in FULL FABRIC

ClΓ‘udia Duarte avatar
Written by ClΓ‘udia Duarte
Updated over a week ago

Don't you just hate lawyer jokes? 😀 Nobody gets them! …Nobody except those who are familiar with the topic, that is. πŸ™Œ And it's much the same with all technical jargon: not at all intimidating once you understand it, and then quite useful and even delightful in its ability to quickly convey specific concepts, actions and functions. πŸ’ͺ

FULL FABRIC has its own set of terms with very particular, high-context meanings, so we put together a brief dictionary for you. This glossary deals with lingo from all around the portal, except Core (a.k.a. the Affairs module), which has its own glossary here.

Let us know if we missed off something and we'll add the missing term! πŸ˜‰

Programme – A combination of subjects that develop expertise in a given field or skill set and lead to a particular degree or certificate.

Subject – A unit of study within a programme (e.g., a BSc in Mathematics could have subjects such as Calculus, Probability and Statistics, among others).

Evaluations – The structured and methodical process of appraisal conducted by staff, by use of custom evaluation templates, to decide whether to accept or reject a submitted application or registration, on the basis of its performance against the criteria set out in the template. Evaluation templates can take the form of screenings, interview record sheets, etc., as fits the school's modus operandi.

Organisations – A directory of organisations that are somehow relevant or connected to the school. Organisations are automatically collected from profiles' place of employment, but can also be manually inputted (e.g., to record information relating to school partners, agents, and so on).

Contacts – A repository of points of contact associated with a given organisation, listing, for instance, the company's CEO, HR Manager, and other departmental managers and verified intermediaries.

Community – A self-running repository of applicants, students and alumni from your school that are professionally linked to a given organisation.

Events – A landing page builder to promote your events, drive registrations, engage with your audience, manage certain aspects of the event (such as sending out reminders, sharing information on time, etc.) and track attendance.

Forms – A form building tool to capture a diverse array of data (e.g., newsletter signups, brochure requests, job applications, customer feedback, etc.), manage submissions in a single page and engage with submitters (e.g., send supplementary data upon submission, transition submitters to a different state, etc.). Forms can be embedded on your website, hosted on a unique landing page or be inserted into a page of your application portal.

Portal – The website builder where you can create, curate and publish the pages that make up your application portal (i.e., the pages your profiles see when they sign in to your school's instance). Depending on the context, the term "portal" can both describe your school's application portal or the module where it was built.

Profile state – The current point in the profile lifecycle that a profile has reached. This is tied to the successive phases of the Recruitment, Marketing, Admissions and Enrolment processes, which themselves vary from school to school (an example would be: initial contact, qualification, application, review, interview, enrolment, etc., and accordingly, a profile would be prospect::engaged, prospect::qualified, applicant::started application, and so on).

Class state – The present status of a class, usually based on the timeframes defined in the system (namely, application starting and closing dates, and class starting and ending dates). Class states are, in this order: NEW, OPEN APPLICATIONS, CLOSED APPLICATIONS, IN PROGRESS and DONE.

Substitution tags – Special codes that stand in for server-generated data  – whereby each code is equivalent to a datum –, as a means of personalising emails for each user. What happens is that, upon the email being sent to one or more recipients, the substitution tag pulls the information FULL FABRIC has about each user and replaces it by the specific value that it corresponds to. Thus, what looks on the editor like, for instance, "Dear |first_name|", will be sent out as "Dear John", "Dear Susan", "Dear Richard", and so forth, without having to write and send these personalised emails one by one.

Merge fields – Similarly to substitution tags, merge fields are system tags that pull in appropriate content about someone, but on document templates created in Microsoft Word.

Source category – The source whence a lead originated. The list of possibilities is determined by the school: e.g., Fairs, School events, Recommendations, Publications, etc.

Source method – The method through which a profile was created in FULL FABRIC. These methods are fixed and are as follows: API, Events, Forms, Import, Sign Up and Staff.

Schema – An area containing input fields. For instance, the content of the profile Info tab, inside application forms, etc.

Journey – A schema that's introduced near the bottom of the profile Info tab whenever a profile is added to a certain class, with the purpose of storing unique class-centric information such as registration ID, daytime or evening track, part-time or full-time mode, etc. Consequently, a profile added to multiple classes will have multiple journey schemas (one for each).

Class schema – A customisable area, found in General settings > Institution > programme > class > Data, to store any extra piece of information not covered in the class Details tab, such as comments, other relevant dates, etc.

Segment – A filtered list showing a subset of users with shared characteristics set by you using rules. E.g., "profile β‡’ is a β‡’ applicant::admitted & profile β‡’ has not β‡’ withdrawn". Segments can be built in many areas of FULL FABRIC, including campaign audiences.

Shared segment – A segment specifically built in General settings > Shared segments, where it's shareable with other staff members and retrievable by the modules in FULL FABRIC that target segments.

Campaigns – Bulk emails sent through the Campaigns module, our powerful email editor.

Overview – The main page of a module, through which the respective data (i.e., a list of profiles, a list of upcoming or sent emails, a list of shared segments…) is accessed (e.g., the application overview, the class overview, the campaigns overview, etc.).

Shared email templates – A master list of email templates available under General settings > Shared email templates, where they're accessible and usable by all staff members. Shared email templates can be uploaded onto one-to-one emails and campaigns.

Automations – A chain of events which you can set to occur when one or more conditions are met, thereby combining triggers, actions and logic (often referred to as a workflow). For instance: send users a brochure upon submitting a form, send registrants a QR code to mark their attendance upon registering for an event, etc.

Institution-level application templates – Application templates associated to more than one class.

Class-level application templates – Application templates exclusively associated to one class.


PUBLISHED: October 23, 2019
​LAST UPDATED: August 18, 2020 at 1:04 p.m.

Did this answer your question?