Paper
High
Review methodology
Clinical Biomarkers
Research task management
Research tasks do not exist in isolation. They are part of a context.
Organise tasks, assignees, priorities and dates by connecting them with projects, papers, conferences, theses and the rest of your research activity.
Turn day-to-day work into a visible and connected part of your research.
Research Kanban
Workspace work
View by status
Pending
2 example tasks
Conference
Medium
Prepare presentation
Precision Medicine Summit
In progress
1 example task
Project
High
Validate results
Biomarker Validation
Completed
1 example task
Thesis
Low
Review bibliography
Precision Diagnostics
The title is not enough
“Review methodology” does not explain which research it belongs to.
An isolated action forces the team to reconstruct the information that gives it meaning. In KaiperKit, the task can bring that information together within the same record.
Which paper?
Within which project?
Who is it assigned to?
When is it due?
- Context
- Paper · Clinical Biomarkers
- Related
- Project · Clinical Validation
- Assignees
- Laura Martín · Daniel Ruiz
- Priority
- High
- Date
- 18 June 2027
- Status
- In progress
From research to action
Every task retains the relationships that explain where it comes from.
A task can have multiple contexts and multiple assignees. The record adds a status, priority and optional date to turn scientific work into a manageable action.
ContextPaper · Clinical BiomarkersProject · Clinical Validation
↓
ActionReview methodologyDescription available
↓
AssigneesLaura · Daniel
PriorityHigh
Date18 JUN
StatusIn progress
ProjectClinical Validation→Validate results
ThesisPrecision Diagnostics→Review results chapter
ConferencePrecision Medicine Summit→Prepare presentation
The same work, two views
Kanban to understand status. Calendar to understand timing.
Tasks with a `due_date` and deadlines appear in KaiperKit's internal calendar. There is no need to present both concepts as though they were the same object.
KanbanWork by status
Pending · In progress · Completed
Review methodologyPaper · 18 JUN
Prepare presentationConference · 24 JUN
Validate resultsProject · 21 JUN
Review bibliographyThesis · 12 JUN
CalendarWork by date
Internal view
MTWTFSS
14151617
18Task · Methodology
1920
21Deadline · Submission
2223
24Task · Presentation
252627
Two different objects
Not every date is a task. And a task with a date does not become a deadline.
KaiperKit keeps the work that needs to be completed separate from the time-critical milestones that need to be monitored.
Review methodology
- Status
- In progress
- Priority
- High
- Optional date
- 18 JUN
- Assignees
- Laura · Daniel
- Context
- Paper · Project
Manuscript submission
- Type
- Submission
- Priority
- Critical
- Date and time
- 21 JUN · 14:00
- Condition
- Hard deadline
- Status
- Pending
There is no direct technical relationship between Task and Deadline. Both can share context, assignees and calendar visibility, but they are managed as independent records.
Research deadlines
Critical dates with an identity of their own.
A deadline records a title, description, type, date and time, status, priority, hard-deadline condition, creator, members and related contexts.
DeadlineManuscript submission
Hard
Contexts
Paper · Clinical Biomarkers
Project · Clinical Validation
- Type
- Submission
- Status
- Pending
- Priority
- Critical
- Members
- Laura · Daniel
Assigned work
The operational view also respects each collaborator's participation.
Collaborators see tasks they have created or been assigned to in Kanban and calendar views. They can create tasks within entities in which they participate, assign those tasks to themselves and update tasks they created or were assigned to.
CollaboratorDaniel Ruiz
Visible work
Created by DanielReview sample selection
VisibleAssigned to DanielValidate results
VisibleNeither created nor assignedPrepare administrative proposal
Not visible
Supported contexts
Five research structures can generate work and critical dates.
Tasks and deadlines can be related to several contexts at the same time. Funding does not appear as a direct context in either of these modules.
01Projects
Actions and dates within project execution.
02Papers
Work and dates throughout the publication process.
03Research lines
Activity associated with the scientific framework of a research line.
04Theses
Actions and dates linked to doctoral research.
05Conferences
Preparation and deadlines related to the event.
Frequently asked questions
Tasks, dates and research context.
The current scope of operational work management in KaiperKit.
Yes. The Kanban board organises tasks into Pending, In progress and Completed and lets users update their status.
Not currently. The product does not implement checklists, subtasks or nested steps within a Task.
Projects, papers, research lines, theses and conferences. A single record can contain multiple contextual relationships.
A Task represents an action with a Kanban status and an optional date. A Deadline represents a date with its own type, priority, status and hard-deadline condition. They are independent entities with no direct relationship between them.
Tasks with a `due_date` and all workspace deadlines visible to the user. It is an internal calendar; the product does not currently demonstrate synchronisation with external calendar services.
Action in context
Make sure every task retains the research that made it necessary.
See how KaiperKit connects operational work, its assignees and its dates with the team's scientific structure.