Difference between revisions of "Documentation:At-Event"

From Facilitation Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
=== Documentation Checklist: At the Event ===
 
=== Documentation Checklist: At the Event ===
  
−
'''Who is involved:'''
+
* At start of event: explain notes/documentation model
−
* Facilitator
+
** Set expectations regarding shared responsibility for note-taking
−
* Documentation lead
+
** Remind facilitators to ensure notes are captured in their sessions
−
* Note takers (co-organizers; or participants, taking turns, not more than once during the event)
+
** Explain how and when notes will be used and/or made available after event
  
−
'''Checklist:'''
+
* At start of session blocks during agenda
 +
** Documentation lead should verify who is taking notes in all sessions per time slot
 +
** Note takers should follow [[Documentation:Process for Session Types|notes capture processes based on the type of session]]
  
−
1. Facilitator to explain notes capture model in opening circle
+
* After sessions: Documentation lead gathers session notes
 +
** Engage each note take to confirm submission of notes
 +
** Provide multiple options for submitting notes
 +
*** Email
 +
*** Upload
 +
*** Etc
  
−
2. Documentation lead to follow at-event [[Documentation:Process_for_Session_Types|notes capture processes per session type]]
+
* Managing notes
−
 
+
** Documentation lead should post notes to main notes capture location on a rolling base, in collaboration with note takers.
−
3. Documentation lead to gather the session notes collected (either as text file, or picture of notes not yet typed up) accordingly to the Aspiration file-naming convention.
+
** When naming notes documents, it is advisable to follow file naming conventions, e.g.
−
 
+
*** AspirationEventNameSessionNameNotes.txt
−
The Aspiration file-naming convention can have multiple parts:
+
** Save notes in inter-operable, hopefully-open formats:
−
* Aspiration, if Aspiration is the organization creating the documentation. Use the full name consistently to avoid sorting errors
+
*** Text as .txt or .pdf
−
* Organizing entity or project. Write it capitalized or as acronym if longer than 10-15 characters
+
*** Images as .png or .jpg files
−
* Name of the meeting. Write it capitalized
 
−
* Name of the session. Write it lower case
 
−
* Content type. Write it capitalized, e.g. "Notes"
 
−
* Number, if there is a series of files with same file name and file extension, e.g. multiple photos documenting the notes of the one single session. The first value is 01, then 02 and so on
 
−
 
 
−
Example: AspirationABCDigitalRightsSummitspeedgeeking01
 
−
 
 
−
Please note:
 
−
* Never use punctuation or spaces when creating file names
 
−
* Always save pictures as .jpg files and texts as .pdf files
 

Latest revision as of 04:12, 28 July 2017

Documentation Checklist: At the Event

  • At start of event: explain notes/documentation model
    • Set expectations regarding shared responsibility for note-taking
    • Remind facilitators to ensure notes are captured in their sessions
    • Explain how and when notes will be used and/or made available after event
  • After sessions: Documentation lead gathers session notes
    • Engage each note take to confirm submission of notes
    • Provide multiple options for submitting notes
      • Email
      • Upload
      • Etc
  • Managing notes
    • Documentation lead should post notes to main notes capture location on a rolling base, in collaboration with note takers.
    • When naming notes documents, it is advisable to follow file naming conventions, e.g.
      • AspirationEventNameSessionNameNotes.txt
    • Save notes in inter-operable, hopefully-open formats:
      • Text as .txt or .pdf
      • Images as .png or .jpg files
Retrieved from "https://facilitation.aspirationtech.org/index.php?title=Documentation:At-Event&oldid=195"