Page Datafolder: BaileyWeb.University.People

The Page Datafolder BaileyWeb.University.People, titled as University People, is used to store contact information and role details for your institution's employees. Please refer to the Data Model page for information about its relation to other datatypes.

Data Structure

Field: Label: Help: Type: Optional: Widget: Validation: Order: Group:
Id GUID Key
UserId User identification* The UserID of the person, usually the same as their Active Directory or Open Directory ID. Must be unique. String (64) No Text Box None Ascending2
DisplayName Display name* The full name of the person. String (128) No Text Box None Ascending1
Honorific Honorific* The honorific title for the person. Data Reference (Honorifics) No Selector (GetSelectedHonorificsListDictionary) None
Forename Forename* The given name of the person. String (64) No Text Box None
Surname Surname* The family name of the person. String (64) No Text Box None
PostNominalLetters Post-nominal letters The post-nominal letters of the person. Please use correct order for your country. String (1024) Yes Text Area None
JobTitle Job title The job title of the person. String (256) Yes Text Box None
Email Email address The email address of the person. String (256) Yes Text Box None
Telephone Telephone number The telephone number of the person. Please add the international dialing prefix and use E.164 formatting. String (32) Yes Text Box Regular Expression Validation
Mobile Mobile telephone number The mobile/cellular telephone number of the person. Please add the international dialing prefix and use E.164 formatting. String (32) Yes Text Box Regular Expression Validation
Building Building The building location for the person. Data Reference (Buildings) Yes Selector (GetBuildingsListDictionary) None
Room Room The room number/code for the person. String (32) Yes Text Box None
Website Website URL The portfolio website of the person. String (1024) Yes Text Area None
SocialTwitter Twitter username The Twitter username of the person. Please include the @ symbol. String (16) Yes Text Box Regular Expression Validation
SocialFacebook Facebook handle The Facebook handle/username of the person. String (64) Yes Text Box None
SocialLinkedIn LinkedIn username The LinkedIn username of the person. String (64) Yes Text Box None
SocialAcademiaEdu Academia.edu username The Academia.edu username of the person. String (64) Yes Text Box None
SocialGooglePlus Google+ username The Google+ username of the person. String (64) Yes Text Box None
Photograph Photograph A photograph of the person. Square images only. Data Reference (C1 Image File) Yes Image Selector None
PersonalStatement Personal statement XHTML N/A Visual XHTML Editor None
AcademicQualifications Academic qualifications XHTML N/A Visual XHTML Editor None
ProfessionalQualifications Professional qualifications XHTML N/A Visual XHTML Editor None
ProfessionalBodies Membership of professional bodies XHTML N/A Visual XHTML Editor None
TeachingSpecialism Teaching specialism XHTML N/A Visual XHTML Editor None
CurrentScholarship Current scholarship XHTML N/A Visual XHTML Editor None
ExternalExaminers External examiners XHTML N/A Visual XHTML Editor None
OtherExternalRoles Other external roles XHTML N/A Visual XHTML Editor None
ResearchPublicationsOutputs Research publications and outputs XHTML N/A Visual XHTML Editor None
RecentProfessionalUpdating Recent professional updating XHTML N/A Visual XHTML Editor None
Display Display? Display this person on the website (Tick for yes)? Boolean (True) N/A Check Box None

Settings

  • Has caching? No
  • Has publishing? No
  • Localised? No
  • Data URL: ~/people({UserId})

Notes

People are listed alphabetically by the DisplayName field, then by the UserId field.

The String (64) type is used for most fields, as that character length is commonly used for Active Directory fields.

For the PostNominalLetters field, please refer to the guidance on letter ordering in the Wikipedia article of the same name.

There is no regular expression validation for email address, in order to allow for domain names that don't use Western European/Latin characters. If you wish to add validation, we recommend starting with ^$|^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$, as this will cover most examples.

The Telephone and Mobile fields are covered by regular expression validation for E.164 formatting, i.e. +441234567890 for what would be written longhand as +44 (0)1234 567890. This is coded as ^$|^\+(?:[0-9] ?){6,14}[0-9]$.

The SocialTwitter field is covered by regular expression validation of ^$|^@?(\w){1,15}$.


Updated: 24 September 2017