# data[].attributes.body
Clear leadership from Brian and TISLab

# data[].attributes.body
Clear articulation of what was added to infrastructure, who was responsible, and timeframes in advance

# data[].attributes.body
Lots of upfront effort on process (roadmap, org charts, RACI matrices, architecture / data flow diagrams, etc.) that weren't consistently followed or used

# data[].attributes.body
especially compared to V1. Better understanding of infrastructure helped streamline the handoff

# data[].attributes.headline
taking advantage of the DMC/DPC structure - this can be uniquely better than just taking KF and splitting it in half

# data[].attributes.subject
taking advantage of the DMC/DPC structure - this can be uniquely better than just taking KF and splitting it in half

# data[].attributes.headline
streamline the clinical data ETL, taking advantage of LinkML features

# data[].attributes.subject
streamline the clinical data ETL, taking advantage of LinkML features

# data[].attributes.body
When new ideas were brought up, it wasn't always clear whether they should be prioritized for the next release or added to the "big picture" backlog

# data[].attributes.body
their expertise helped rapidly resolve technical issues

# data[].attributes.headline
tasks were more organized on GitHub rather than Slack

# data[].attributes.subject
tasks were more organized on GitHub rather than Slack

# data[].attributes.body
Messaging to users that they are encouraged to come to the portal, test it, let us know how their experience is, help us make it better

# data[].attributes.headline
Would be really great to convince ABC-DS to allow more of their data in the portal

# data[].attributes.subject
Would be really great to convince ABC-DS to allow more of their data in the portal

# data[].attributes.headline
Clinical data model will need to continually evolve

# data[].attributes.subject
Clinical data model will need to continually evolve

# data[].attributes.body
with each release, get more granularity

# data[].attributes.headline
more granularity for how clinical data was obtained (self report, genetic test, etc.)

# data[].attributes.subject
more granularity for how clinical data was obtained (self report, genetic test, etc.)

# data[].attributes.headline
How much of curation will be self-service?

# data[].attributes.subject
How much of curation will be self-service?

# data[].attributes.headline
What will be the strategy for integrating DMS plans from contributors?

# data[].attributes.subject
What will be the strategy for integrating DMS plans from contributors?

# data[].attributes.headline
would like researchers/community members to be able to share non-data items in the portal - e.g. research results from the portal, protocols, publications, narratives, tools, cognitive test modifications, etc. - like CCKP

# data[].attributes.subject
would like researchers/community members to be able to share non-data items in the portal - e.g. research results from the portal, protocols, publications, narratives, tools, cognitive test modifications, etc. - like CCKP

# data[].attributes.headline
can/how should users start using Synapse/Cavatica earlier in the process

# data[].attributes.subject
can/how should users start using Synapse/Cavatica earlier in the process

# data[].attributes.body
Research stories from people using the data that is currently in the Hub. Possibly even provide a metric on data reuse

# data[].attributes.headline
be able to show that we improved statistical power from v2 to v3

# data[].attributes.subject
be able to show that we improved statistical power from v2 to v3

# data[].attributes.headline
how to identify participants in multiple studies & issue common IDs

# data[].attributes.subject
how to identify participants in multiple studies & issue common IDs

# data[].attributes.headline
add most popular queries (with permission), or other way to capture what users are looking for

# data[].attributes.subject
add most popular queries (with permission), or other way to capture what users are looking for