Wiki Workshop Bloomington

Take 5 min for your individual tour through this wiki

Access the wiki at http://decodingthediscplines.de (NB: 1) http not https, 2) .de not .org)

To access this page use QR-code to the right.

Reasons why we need a wiki

• People learning about Decoding (or threshold concepts, misconceptions etc.) regularly ask for a list of bottlenecks in their discipline.
• Such a list could be the entry point to more information about Decoding and by the Decoding community.
• Make your own work more visible.
• Sharing data (e.g. interview recording/transcripts, teaching materials etc.) - nonpublicly if needed. For instance, most of you will currently not be allowed to access the transcriptes featured under "Available Resources" on the page Limits.
• Wiki as a community platform.

Quoting David Pace:

We could, for example, share lists of bottlenecks that are worth special attention in particular kinds of courses. Segments of interviews could be presented in an abbreviated form that would give teachers insights into what their students need to be able to do in order to succeed. And we could make available examples of strategies used to model, give practice on, and assess key mental operations or responses to specific emotional bottlenecks.

Create an user account

Go to http://decodingthediscplines.de, press "Log in" on the upper right corner, and go down the page to "create user account."

Suggestions for tiny tasks to get your hands dirty

1. Edit Decoding Conference and make the Bloomington meeting a past event (rather than a future one).
2. Add comma between "Bloomington Indiana" on Events page.
3. Add a publication about Decoding. Use any page in Category:PublishedWork as an example.
4. Describe a bottleneck. Use any page in Category:Bottleneck as an example.
5. Improve any page you found incomplete during your 5 min tour through this wiki.

Commitment

It is unlikely that we spend our precious time on generating content.

→ Regular "edit-a-thons" during formal Decoding meetings (such as this conference or virtual meetings)

Are we willing to reserve meeting time for edit-a-thons?

See also

• Poster at the Aachen Conference