Documentation:At-Event - Revision history

Wikiadmin: /* Documentation Checklist: At the Event */

2017-07-28T04:12:50Z

Documentation Checklist: At the Event

Wikiadmin: /* Documentation Checklist: At the Event */

2017-07-28T04:11:48Z

Documentation Checklist: At the Event

Wikiadmin: /* Documentation Checklist: At the Event */

2017-07-27T17:51:37Z

Documentation Checklist: At the Event

Beatrice at 13:48, 25 May 2016

2016-05-25T13:48:14Z

Beatrice: /* Documentation Checklist: At the Event */

2016-05-25T13:47:28Z

Documentation Checklist: At the Event

Beatrice: /* Documentation Checklist: At the Event */

2016-05-24T21:24:23Z

Documentation Checklist: At the Event

Beatrice: /* Documentation Checklist: At the Event */

2016-05-24T21:23:51Z

Documentation Checklist: At the Event

Beatrice: /* Documentation Checklist: At the Event */

2016-05-24T21:21:15Z

Documentation Checklist: At the Event

Beatrice: /* Documentation Checklist: At the Event */

2016-05-19T13:47:21Z

Documentation Checklist: At the Event

Beatrice: /* Documentation Checklist: At the Event */

2016-05-19T13:37:21Z

Documentation Checklist: At the Event

@@ Line 3: / Line 3: @@
 * At start of event: explain notes/documentation model
 ** Set expectations regarding shared responsibility for note-taking
-** How facilitators will be oriented to assure notes are captured
+** Remind facilitators to ensure notes are captured in their sessions
 ** Explain how and when notes will be used and/or made available after event

@@ Line 1: / Line 1: @@
 === 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
+** How facilitators will be oriented to assure notes are captured
-* 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
-. Facilitator to explain notes capture model in opening circle
+* After sessions: Documentation lead gathers session notes
-. 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.
-. 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

@@ Line 26: / Line 26: @@
 Please note:
 * Never use punctuation or spaces when creating file names
-* Always save pictures as .jpg files and texts as .pdf files
+* Always save notes in inter-operable, hopefully-open formats:

@@ Line 10: / Line 10: @@
 . Facilitator to explain notes capture model in opening circle
-. Documentation lead to follow at-event [[Documentation:Process_for_Session_Types|notes capture processes per session type]]
+. Documentation lead to follow at-event [[Documentation:Process for Session Types|notes capture processes per session type]]
 . 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.

@@ Line 10: / Line 10: @@
 . Facilitator to explain notes capture model in opening circle
-. Documentation lead to follow at-event [[Documentation:Process for Session Types|notes capture processes per session type]]
+. Documentation lead to follow at-event [[Documentation:Process_for_Session_Types|notes capture processes per session type]]
 . 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.

← Older revision		Revision as of 21:24, 24 May 2016
Line 11:		Line 11:

	2. Documentation lead to follow at-event [[Documentation:Process for Session Types\|notes capture processes per session type]]		2. Documentation lead to follow at-event [[Documentation:Process for Session Types\|notes capture processes per session type]]
−
−	~~Documentation process of specific session types~~
−
−	* Agenda brainstorming
−	** Documentation lead and/or volunteering participants to transcribe post-it content in text document or spreadsheet (as preferred by the organizers), taking each thematic column as a separate list (a bullet-point list on a text document; a column in a spreadsheet)
−
−	* Spectrogram
−	** Documentation lead to collect separately in different lists to be transcribed:
−	*** Read statements. And for each of these, take note of the approximate positioning of participants along the Agree-Not Sure-Disagree line and most relevant movements. E.g. "50% Agree, 10% Not Sure, 40 % Disagree; by the end of the debate, 50% Agree and 50% Not Sure"
−	*** Top level statements
−	*** Other statements
−
−	* Working session
−	** Before the session starts:
−	*** Facilitator to invite each group to have a volunteering note taker, taking notes on personal device or on paper, following the model agreed with event organizers (online or offline documents, etc.)
−	*** Documentation lead to ask each group at the beginning of the session to communicate the name of the note taker (for future reference and contact)
−	** At the end of the session:
−	*** Facilitator to remember note takers to share notes with the documentation lead
−	*** Documentation lead to verify that all notes have been collected, and, if anything is missing, follow up with responsible note taker to agree on collection method and timeframe (recommended: collect all notes by the end of the day the session has been taken place on)
−
−	* Skill share
−	** Documentation lead to take note of the titles of the skill share conversations taking place
−
−	* Speed geeking
−	** Basic documentation: documentation lead to visit each speed geeking station and take notes
−	** More detailed documentation: designate one note taker for each station, to take notes of the all the conversations taking place during all rounds

	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.		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.

@@ Line 12: / Line 12: @@
 . Documentation lead to follow at-event notes capture processes per session type
-Documentation process of the most popular session types
+Documentation process of specific session types
 * Agenda brainstorming

@@ Line 8: / Line 8: @@
 '''Checklist:'''
-. Facilitator to explain notes capture model in opening circle.
+. Facilitator to explain notes capture model in opening circle
-. Documentation lead to follow at-event notes capture processes per session type.
+. Documentation lead to follow at-event notes capture processes per session type
 Documentation process of the most popular session types
@@ Line 19: / Line 19: @@
 * Spectrogram
 ** Documentation lead to collect separately in different lists to be transcribed:
-*** Read statements. And for each of these, take note of the approximate positioning of participants along the Agree-Not Sure-Disagree line and most relevant movements. E.g. "50% Agree, 10% Not Sure, 40 % Disagree; by the end of the debate, 50% Agree and 50% Not Sure".
+*** Read statements. And for each of these, take note of the approximate positioning of participants along the Agree-Not Sure-Disagree line and most relevant movements. E.g. "50% Agree, 10% Not Sure, 40 % Disagree; by the end of the debate, 50% Agree and 50% Not Sure"
 *** Top level statements
 *** Other statements
@@ Line 41: / Line 41: @@
 The Aspiration file-naming convention can have multiple parts:
-* Aspiration, if Aspiration is the organization creating the documentation. Use the full name consistently to avoid sorting errors.
+* Aspiration, if Aspiration is the organization creating the documentation. Use the full name consistently to avoid sorting errors
-* Organizing entity or project. Write it capitalized or as acronym if longer than 10-15 characters.
+* Organizing entity or project. Write it capitalized or as acronym if longer than 10-15 characters
-* Name of the meeting. Write it capitalized.
+* Name of the meeting. Write it capitalized
-* Name of the session. Write it lower case.
+* Name of the session. Write it lower case
-* Content type. Write it capitalized, e.g. "Notes."
+* 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.
+* 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