...
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.
A Synapse Project drives the backend of the portal. Make a project (e.g. PEC).
Define a url by opening a Jira issue with PORTALS (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
Setting Views and Tables
If you set a facet in a Table or File View, it will be displayed in the portal. It will also come at a cost - the more facets, the slower the performance.
Portals can be driven off of both Views and Tables. Key considerations when determining which to choose:
By design, Tables are not public. Therefore, Portal Tables must be explicitly whitelisted by governance and someone on the leadership team in order to make them public. This is required any time the schema changes or values are added.
Files are only available to bulk download through Views. (Bulk download feature not exposed in the web UI in Tables).
There is potentially a performance hit in Views (in dispute; has not been fully tested) if there are varying access permissions across the set of files and many facets.
Use these questions to guide conversation with the design team about the homepage:
...