...
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’ ‘backlog’ label is required to be visible to engineering team and product manager.
...
Fill out the 1-pager for product and design and submit a Jira in the PORTALS project for review.
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).
Open a Jira issue with PORTALS to (e.g. PEC) create required infrastructure. 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
All data View
If you want to surface data entities in the portal,
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
Create Tables and Views in Synapse to drive the Explore and Homepage components of portals. The names and number of tabs nested under Explore is customizable.
Define the schemas for Tables and Views in Confluence pages. Be explicit about the Synapse entity to reference and the number of secondary fields to display in the cards. Secondary fields are defined in the UI Mapping Example schema.
General notes about table schemas and column types
Simple.
Display Name | Column Name | Facet Y/N | UI Mapping | Destination | Searchable Y/N | Search hint text | Markdown Y/N |
|---|
Display Name - The Column Name will be the Display Name unless explicitly specified in the schema. If the Column Name is camelCase, it will automatically display as Camel Case.
Column Name
Facet -
UI Mapping - Define the hierarchy of variables to display on the cards as
title(e.g. Center for Cancer Systems Pharmacology),subTitle(e.g. Harvard University),description(e.g. The Center….),secondaryLabels[0](e.g. INVESTIGATOR),secondaryLabels[1](e.g. GRANT NUMBER) etc.
Destination - Note where a column should hyperlink to other resources within the portal.
Searchable Y/N -
Search hint text -
Markdown Y/N - While simple markdown (links, bullets, bold, etc) is supported in underlying tables,
...
explicitly specify which columns
...
contain markdown in the schema
...
if you need to link to multiple synapse IDs, separate the list with commas
Use these questions to guide conversation with the design team about the homepage:
...
Why/goals/value- what is the focus of this portal
...
Relationship to consortium
...
Fit in ecosystem
...
Type of resources available
...
Diversity within type/amount within type
...
.
...
Progress and future-- living repo/freshness of data
...
Testing on Portals