User talk:Simon/Producing texts: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
[[File:woven papyrus sheet.jpeg|150px|thumb|Papyrus, an early writing surface made from woven reeds]] | [[File:woven papyrus sheet.jpeg|150px|thumb|Papyrus, an early writing surface made from woven reeds]] | ||
{{User:Simon/Reading,Writing & Research Methodologies SI9/Outlining content of workshops 22.05.19}} | |||
[[Category: Library Snippets]] | [[Category: Library Snippets]] |
Latest revision as of 15:17, 20 June 2020
22.05.19 Outlining content of workshops: annotation
a) what purpose does annotation serve (in your case)?
Annotations in the form of accumulative traces of reader's interactions with texts underline the sociability of libraries - not just collections of knowledge but discourse around them; [How?] dispels notions of the singular, authority and property in favour of collectivity and plurality and highlights the social construction of knowledge
b) what does it do for the reader (in your case)?
Simon: Annotation affirms the idea that a text is part of a discourse - not in isolation from other texts/writers - and that knowledge is socially constructed. Annotation is a way for a reader to become visible to others and part of this discourse. It avoids authorship, and singular notions of knowledge production.
c) what does it do for the annotators (in your case)?
Simon: In my case, the annotators are the readers. Annotation exists as an action in response to the text, or to existing annotations. It can be idiosyncratic, and readable only to the annotator, therefore revealing (some) elements of how that particular person interprets the text. But, more often there are unspoken conventions to the types of annotations typically used, e.g. underlining, highlighting, circling, asterisks, dots etc. These can be defined by the technical limitations of the technology used, or linguistic (and typographic) conventions. This commonality begins to create a shared vocabulary through which readers read each other's responses to texts (here "read" can mean interpret, or access, like a file).
YOUR PROJECT
look at your project descriptions and use them as a basis to make a plan
- define your aim [see above]
- what needs to be done?
- make a timetable
- what needs to be developed further?
- who can help you? and how?
- consider how you can organise your upcoming methods sessions (5 & 19 June) so they can help you realise your aim.
General question: what is the interface to your part the project. OR How do you invite people in to your project?