lzim / teampsd

Team PSD is using GitHub, R and RMarkdown as part of our free and open science workflow.
GNU General Public License v3.0
9 stars 23 forks source link

2024_08 #story_b: MTL 3.7 Consult Manual QA/QC content checks #3093

Closed ljmoody closed 1 month ago

ljmoody commented 7 months ago

FYI: Manual CONTENT is being tracked in #3168

Leanest guide/manual updates we could do:

Updates, changes, & checks:

Find & Replace:

ljmoody commented 7 months ago

@tejaspesquare - please change the name of this dashboard as shown in the screenshot: image

fyi: @lijenn, @lzim

lzim commented 6 months ago

wk4 2024_mar_epic

The outline for the MTL 3.7 Consult Manual needs to be finalized in wk1 2024_apr_epic @lzim is working on this to discuss at the #support_workflow 3rd hour of #consult_workflow prep Tues 04/02 at 10AM Pacific

image.png
ljmoody commented 4 months ago

Hi @lzim, how is the order of information for the consult manual coming along? Do you need any help Jenn or I can provide? I plan on joining the last hour of wk3 May #systems_sme_workflow tomorrow, so it's possible we can touch on this there.

fyi @lijenn

lzim commented 4 months ago

wk3 2024_06 @ljmoody @lzim @lijenn

Assets Required/Developed

Chapter 1 Why use Modeling to Learn

Chapter 2 How to use Modeling to Learn

Chapter 3 Technical Documentation

Functional Requirements - Public-facing manual (not a lot of internal links on GitHub; link to within VA via Teams)

1. Why place a Modeling to Learn 3.7 Consult? (10 chapters/videos)

2. How can Modeling to Learn help?

lijenn commented 2 months ago

Discussed 7/19 Team Praxis Call:

ljmoody commented 1 month ago

8/1/2024 update:

fyi: @jamesmrollins @lijenn @matthewtomo

ljmoody commented 1 month ago

Breaking remaining tasks in this card down into manageable chunks and closing this card with points revised reflect work effort.