While developing demonstration narratives for the EFI-EST Apps, I realized that some steps require non-intuitive and poorly documented (on the KBase side) user actions. I've got some quick and dirty screenshots of the steps to follow, specifically for the importing of a protein sequence FASTA file into a SequenceSet object to then be used in the EFI-EST FASTA app. These images won't go into any documentation for this repo but will be used in markdown cells within the demo narratives.
I'm thinking a subdirectory tree like ~/data/screenshots/{narrative_id}/, within which the screenshots for that narrative will be stored. I can include a README file to specify metadata/extra information about the narrative and screencaps. The images will be named {img_number}_{some_descriptive_text}.png to keep things organized and clear.
While developing demonstration narratives for the EFI-EST Apps, I realized that some steps require non-intuitive and poorly documented (on the KBase side) user actions. I've got some quick and dirty screenshots of the steps to follow, specifically for the importing of a protein sequence FASTA file into a SequenceSet object to then be used in the EFI-EST FASTA app. These images won't go into any documentation for this repo but will be used in markdown cells within the demo narratives.
I'm thinking a subdirectory tree like
~/data/screenshots/{narrative_id}/, within which the screenshots for that narrative will be stored. I can include a README file to specify metadata/extra information about the narrative and screencaps. The images will be named{img_number}_{some_descriptive_text}.pngto keep things organized and clear.