Sharable Research Summary outline to html converter
(to edit use * = tab)
Large presentation font
no
yes | selftest
SUMMARY Title: * BACKGROUND * GOAL * METHOD * FINDINGS * EXPLANATION * COMMENTS about the Background: * Comments about the Goal: * Comments about the Methods: * Comments about the Findings: * Comments about the Explanation: * Additional Comments: * CREDITS *Source Article: **Article Author(s): ***First Author: ***Institution: ***Email address: ***Email subject line: ***Other Authors: **Article year: **Article title: **Article Journal: **Article Journal Volume: **Article Journal Issue: **Article Journal Pages: **Database: PsycArticles **Search keys: Student Author(s): *First Author: **Institution: Douglas College **Email address: **Email subject line: * *Content licensed under a
Creative Commons License
. **You are free: to copy, distribute, display, and perform the work Under the following conditions: **1) Attribution. You must give the summary authors credit. **2) Noncommercial. You may not use this work for commercial purposes. **3) No Derivative Works. You may not alter, transform, or build upon this work. **During development, I give permission for non-commercial copying for educational and review purposes. *After publication in a Learning Object Repository, all text and code will be released under the Free Software Foundation’s
GNU Free Documentation License
. Faculty Reviewer: Bruce Landon, Ph.D. *Institution: Douglas College *Email address: Bruce_Landon@douglas.bc.ca *Email subject line: *Faculty Review: *Faculty Rating: Updates: *
Copy output below into notepad and Save As a file ending in .html
00. (optional review a good model of a sharable research summary) 01. find an interesting cognition article in PsychArticles published after 2002 02. study the article (PRTR style: Preview Read Think Review) 03. decide you can summarize the article (arrange for help or find another article) 04. fill in the reference data into the sharable research summary format: srsblank.txt 05. find and summarize the hypothesis or goal 06. find and summarize the methods 07. from the introduction make an outline of the logic to the hypothesis or goal 08. find and summarize the key results that support or fail to support the hypothesis (both the introduction and the first part of the discussion may be helpful here) 09. find and summarize the explanation of the results from the discussion 10. find and summarize the implications of the findings from the discussion 11. check that your summaries are consistent with the Abstract 12. reread your draft summary and reread the article appling critical thinking analysis (make notes by section of your criticisms and observations of the article) 13. Write your comments sections 14. check that your comments and your section summaries are consistant 15. reread aloud and edit your whole summary assignement to make it smooth sounding prose 16. listen to your summary or enlist some to critically listen to find any confusing parts 17. fix the confusing parts (spell check, grammar check, and reading level check) 18. make a copy of the sentences in each section for developing the self test questions 19. for each important sentence try to make it into a fill-in-the-blank self test item (edit the better self test items to replace pronouns so they make sense out of context) (the format for selftest question is starting a margin and 2 underlines and a space on both sides of the answer ie each question will have a one or two word __answer__.) (the selftest questions should be in the respective parts of the assignment) (the intention of the selftest questions is to facilitate remembering the important concepts so in general the answer should be an important 1 or 2 word phrase) (do not use numbers for answers and in general avoid personal names as answers) 20. proof and edit your entire summary checking for typos, thinkos, and incomplete parts. 21. select the intellectual property licence for distribution 22. preview your summary in the sharable research summary converter: showdraft.html 22. submit the summary on schedule for marking by the instructor 23. make appropriate edits to address the comments from the instructor. 24. submit the final version for publication in the learning object repository. 25. make a backup copy of the final version for safe keeping. //////// further example of other uses for the javascript program /////// Just below this is an example of an outline text block that can be converted into a webpage to be saved replace this heading with your own then replace the points like this one then replace points with local links [selftester.htm] other web links need full address [http://Bruce-Landon.douglas.bc.ca/] after that replace this heading and this bullet point text may include html tags but the tags are not checked just replace all of this outline with your outline if tabs do not seem to work then begin bullet lines with * *this is also a bullet line heading lines must begin at left margin MENU When a heading starts in with a word in all capitals This heading is made into a navigation label the slide numbers will be used on other slides for example 1 2 3 4 IMAGES 6 7 this is an example of a label type of heading IMAGES can be easily include and sized
200x200 background blue_water.jpg with alt='tile of blue_water.jpg background' 50x50 thumbnail size clickable image button link.gif
FINAL POINT: This is the last bullet slide (and the tricky part) after your presentation is in the textbox below you must copy it and save it to a html file (save by copying it into notepad and then use save as from notepad) after it is saved (myfile.html) then you can view that file in your browser also set your browser font (view menu-text size) to large for best results THANKS for your Attention The output file should be accessible to persons with disabilities. All images should have alt tags explaining the image and navigation should be straight forward. In the output files the navigation is at the top of the screen like the browser menus and the Back and Forward links are also similar to their location in most browsers. Cascading Style Sheets are used to separate page formatting from the content of the output. When using IE browser a sample popup will be generated in a window and the source file can be saved by clicking view and then source. The source file is presented in notepad and can be saved from there or from this textarea. The difference between IE and other browsers is the ability to use images as buttons and to save source code from notepad. Using netscape or other browsers actual buttons are used instead of images. The slides can be used with audio from the actual presentation or from prerecorded files. It is assumed that there is one sound file for each slide starting with s1.wav or s1.mp3 (depending on which format is being used) which are located in the same folder. When played through winamp player it is possible to also use a plugin called pacemaker that allows the user to control the speed - tempo of the playback to suite their needs. This file can be used like a cgi script to process an outline sent from a textbox of another page by setting the form action="outline2.html" in the directory where this file is located and naming the sending text area to be name="outline" so that the sent text replaces the example text in this page. An example page with a form is file: textout2.html The benefit of this is that serveral such pages can be prepared to have boilerplate text outlines and instructions to facilitate the process or provide for specialized assignments.
defaults:
Meta tag
Backgound
white, or smallgrid.gif or
FontFace
arial
blanklines
30
menu color
gainsboro
menu border
black
menu font
black
link gif
info.gif (image links instead of text only)
link label
popup only if link gif is blank for text only
popup width
640
popup height
480
logo
SCORM
SCO (SCO enables sharable content object)
(adds javascript entry and exit to the page for LMS control)
Audio files for the slides:
none
wav
mp3
narration transcripts
no
yes (in files s1.html s2.html ...)
comments and suggestions to
Bruce_Landon@douglas.bc.ca
OpenSource javascript1.1 updated April 25, 2004