PeopleTitle
People titles
Reusable honorifics such as Dr. or Prof. Add a title here, then select it on a person’s record. Titles in use cannot be deleted.
Fieldsname (unique)
Documentation / Content management
A guide to your
research workspace.
Create complete profiles, connect research outputs, and keep your public information consistent. Start with the workflow, then explore the data reference.
Open the admin workspace ↗Build a complete profile.
Create a person
Add a name, reusable title, affiliation, portrait, and tags in People.
Add their background
Create People Information and select the person. Add a biography, institution, and professional details.
Connect their work
Add social links and research outputs. Include a descriptive title, URL, and any relevant metadata.
Save each record before checking the public profile. If an update is missing, refresh the People page to reload its cached data.
Use the account menu in the admin to choose Light, Dark, or System appearance.
How the data connects.
People is the central record. Detailed background, professional links, and research outputs connect to that person.
People
Identity · reusable title · portrait · tags
People Information
Biography, institution, interests, expertise, qualifications, memberships, badges, initiatives, and research areas.
Links & research outputs
Social profiles and publications, posters, presentations, and other contributions.
API reference.
These read-only endpoints serve the people directory and profile pages. Paths are relative to this backend; a hosting proxy may provide a different public prefix.
| Endpoint | Response |
|---|---|
GET/api/people/ | People, tags, titles, and research links |
GET/api/person-info/<slug>/ | One detailed profile with social and research links |
GET/api/people-all/ | All detailed profiles |
GET/api/tags/ | Directory tags |
Interactive API explorer ↗ · API reference ↗ · OpenAPI schema ↗
Data reference
The building blocks.
Reusable records can be linked to multiple people. The field lists below describe the models; API responses may present related records as names or nested objects.
People
People
The core identity record. Add the person’s name, title, affiliation, portrait, and tags. A unique slug connects the record to its public profile.
Fieldstitle, full_name, association, image, slug, tags, created_at, updated_at
PeopleInformation
People information
Create a detailed profile linked to an existing person. The biography supports rich text. Select reusable interests, expertise, qualifications, memberships, initiatives, research areas, and role badges.
Fieldspeople, about_user, institution, research_interests, areas_of_expertise, key_initiatives, key_research_areas, qualifications, memberships, role_badge, created_at, updated_at
PeopleResearchLink
Research outputs
Add outputs directly while editing a person, or use the research links list. Choose publication, poster, presentation, or other. Title and URL are required; metadata is optional. Lower position values appear first.
Fieldspeople, title, category, url, date, location, authors, venue, doi, description, position, created_at, updated_at
{
"title": "Your research output title",
"category": "poster",
"url": "https://example.org/your-poster",
"date": "2026-06-15",
"location": "Dublin, Ireland",
"authors": "First Author; Second Author",
"venue": "Conference name",
"doi": "",
"description": "A brief summary of the work."
}Dates use YYYY-MM-DD. Enter authors in credited order. Leave DOI empty when an output has no assigned DOI.
Tag
Tags
Group people into categories used by the People page filters. Keep names consistent to avoid duplicate categories.
Fieldsname (unique), created_at, updated_at
ResearchInterest
Research interests
Topics a person investigates, such as cancer genomics or federated data sharing.
Fieldsname, created_at, updated_at
AreaOfExpertise
Areas of expertise
Skills and specialist knowledge associated with a person’s detailed profile.
Fieldsname, created_at, updated_at
roleBadge
Role badges
Short profile labels for responsibilities, affiliations, or achievements.
Fieldsname, created_at, updated_at
KeyInitiatives
Key initiatives
Projects, programmes, or collaborations with a title and a direct external link.
Fieldstitle, url, created_at, updated_at
KeyResearchArea
Key research areas
Broader areas of research, each with a title and a descriptive summary.
Fieldstitle, description, created_at, updated_at
Qualification
Qualifications
Academic qualifications and professional certifications. Add the degree, institution, and other useful context to the title.
Fieldstitle, created_at, updated_at
Membership
Memberships
Professional societies and organisational affiliations.
Fieldstitle, created_at, updated_at
SocialPlatform
Social platforms
Define a platform name and an optional supported icon identifier. The icon is a text key, not an image path.
Fieldsname (unique), icon, created_at, updated_at
| Platform | Icon key |
|---|---|
linkedin | |
| GitHub | github |
| Twitter / X | twitter or x |
| Google Scholar | scholar |
| ORCID | orcid |
| Website | globe |
Unsupported or blank keys fall back to the platform name, then a globe. New icon types require a frontend mapping.
PeopleSocialLink
People social links
Connect a person to a platform and their profile URL. Homepage and Email are exposed separately by the profile API; other platforms appear in social_links.
Fieldspeople, platform, url, created_at, updated_at
FileUpload
File references
Reference an externally hosted document by URL. The file browser requires login. Public access through a file link requires is_public to be enabled and the embargo date to have passed, or to be empty. This model stores a reference; it does not upload a file.
Fieldsurl, filename, slug, is_public, embargo_until, created_at, updated_at
Before you share.
Check names and affiliations, confirm authorship and dates, and open each external link. For files, review public access and embargo settings. Fictional sample records and placeholder links should stay in your local test database.
Return to workspace ↗