...
Portal development coordination is tracked in the Community Portals Jira project. Create an appropriate Epic within your own project (for the computational oncology, systems biology, or neurodegenerative research teams, this should be in the SCIENCE project) to track the overall project. It is the job of the respective portal product manager to triage issues to the engineering team (Alina, Michael and Jay) appropriately. ‘backlog’ label is required to be visible to engineering team and product manager.
Ljubomir Bradic (Unlicensed) is responsible for triaging and assigning design related issues, and Ryan Luce (Unlicensed) for portal engineering compoents.
What are the first steps?
Submit a 1-pager for product and design.
Open a Jira to task the design team with the creation of relevant wire frames. Designers will implement logo and color scheme. Depending on the level of customization or needs for external parties, a complete wireframe may not be required. This is at the discretion of the design team, so don’t plan on not having one unless confirmed with Ljubomir Bradic (Unlicensed) .
A Synapse Project drives the backend of the portal. Make a project (e.g. PEC).
Define a url by opening Open a Jira issue with PORTALS to (e.g. PEC). This creates an empty AWS bucket.
Implement design in the staging site by opening a Jira issue with PORTALS(e.g. PEC)
{TODO:determine what is required to make these connections} Create Table/View architecture
Publications
Tool to scrape Pubmed for relevant publications using grant or pubmed id as input
People
Study
Set schema - note "hint text" is tracked in Confluence page and must be manually set by web developer
General notes about table schemas and column types
Simple markdown (links, bullets, bold, etc) is supported in underlying tables, but you will need to specify which columns have markdown in the schema
if you need to link to multiple synapse IDs, separate the list with commas
...