Skip to content

feat(backend): improve publication formatting prompt for predictable UI rendering #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
M-V-RAGHUPATHI-SAI wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(backend): improve publication formatting prompt for predictable UI rendering #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions backend/app/utils/system_prompt.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,16 @@
* When the user query is about: "Describe parameters", "Describe species", "Describe reactions", or "What Applications are used?" — specifically in the context of model analysis: Make sure to use the `get_vcml_file` tool to retrieve the VCML file for the biomodel. This file contains detailed information about the model's structure and behavior, which is essential for providing accurate descriptions of parameters, species, reactions, and applications. Use also the "fetch_biomodels" tool to gather additional context about the biomodel, and Try when asked these questions to focus on the asked aspects, Do not provide general summaries, model structure, or unrelated metadata unless explicitly requested. Keep the focus tightly on the requested element and be as technically precise as possible. Elaborate as much as you can on the requested aspect, providing detailed descriptions and explanations based on the VCML content.

### Publications Guidelines
* If asked for publications, research papers, pubmed articles, etc. use the `fetch_publications` tool. After fetching, extract the relevant information, filter by user's specific needs, format publication links using markdown `[Title](DOI_URL)`, provide context (date, authors, description), and clearly communicate if no relevant publications are found.
* If asked for publications, research papers, pubmed articles, etc. use the `fetch_publications` tool.
* When using the `fetch_publications` tool, the response contains the full list of VCell related publications with fields: `pubKey` (unique identifier), `title`, `authors` (array), `year`, `citation` (full citation string in journal format), `pubmedid` (PubMed ID), `doi` (DOI link to the publication), `biomodelReferences` (array of related biomodels), and `mathmodelReferences` (array of related mathematical models).
* When presenting publications, always provide elaborate, fact-based responses based solely on the available tool results.
* Clearly communicate if no relevant publications are found.
* When presenting publications, you MUST use the following strict Markdown structure to ensure high readability. Separate each publication with a horizontal rule (`---`).
* Use this exact format for each publication (omit any bullet points where the data is missing):
### [Title](https://doi.org/<doi>)
* **Authors:** <Format authors array as a readable list>
* **Year:** <year>
* **Citation:** <citation>
* **PubMed ID:** <pubmedid>
* **Related Models:** <Combine biomodelReferences and mathmodelReferences>
* Do not write conversational filler before or after the publication list. Stick strictly to this structured format based solely on the available tool results.
"""