|
|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
|
<html>
|
|
|
|
|
|
<head>
|
|
|
|
|
|
<meta charset="utf-8">
|
|
|
|
|
|
<title>Tasks of the Contingent Librarian</title>
|
|
|
|
|
|
<link rel="stylesheet" type="text/css" href="tasks.css">
|
|
|
|
|
|
<script src="tasks.js"></script>
|
|
|
|
|
|
</head>
|
|
|
|
|
|
<body>
|
|
|
|
|
|
|
|
|
|
|
|
<div class="cardback"><DOCUMENT_FRAGMENT><div class="mw-parser-output"><div class="thumb tright"><div class="thumbinner" style="width:152px;"><a class="image" href="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d2/Woven_papyrus_sheet.jpeg/960px-Woven_papyrus_sheet.jpeg"><img alt="" class="thumbimage" decoding="async" src="https://pzwiki.wdka.nl/mw-mediadesign/images/thumb/d/d2/Woven_papyrus_sheet.jpeg/320px-Woven_papyrus_sheet.jpeg"></a> <div class="thumbcaption"><div class="magnify"><a class="internal" href="File:Woven_papyrus_sheet.jpeg.html" title="Enlarge"></a></div>Papyrus, an early writing surface made from woven reeds</div></div></div>
|
|
|
|
|
|
<h2><span class="mw-headline" id="22.05.19_Outlining_content_of_workshops:_annotation">22.05.19 Outlining content of workshops: annotation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/mw-mediadesign/index.php?title=User:Simon/Reading,Writing_%26_Research_Methodologies_SI9/Outlining_content_of_workshops_22.05.19&action=edit&section=T-1" title="Edit section: ">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
|
|
|
|
|
|
<p>a) what purpose does annotation serve (in your case)?
|
|
|
|
|
|
</p><p>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
|
|
|
|
|
|
</p><p>b) what does it do for the reader (in your case)?
|
|
|
|
|
|
</p><p>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.
|
|
|
|
|
|
</p><p>c) what does it do for the annotators (in your case)?
|
|
|
|
|
|
</p><p>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).
|
|
|
|
|
|
</p><p>YOUR PROJECT<br>
|
|
|
|
|
|
<b>look at your project descriptions and use them as a basis to make a plan</b>
|
|
|
|
|
|
</p>
|
|
|
|
|
|
<ol><li>define your aim [see above]</li>
|
|
|
|
|
|
<li>what needs to be done?</li>
|
|
|
|
|
|
<li>make a timetable</li>
|
|
|
|
|
|
<li>what needs to be developed further?</li>
|
|
|
|
|
|
<li>who can help you? and how?</li>
|
|
|
|
|
|
<li>consider how you can organise your upcoming methods sessions (5 & 19 June) so they can help you realise your aim.</li></ol>
|
|
|
|
|
|
<p>General question: what is the interface to your part the project. OR How do you invite people in to your project?
|
|
|
|
|
|
</p>
|
|
|
|
|
|
<!--
|
|
|
|
|
|
NewPP limit report
|
|
|
|
|
|
Cached time: 20200620141728
|
|
|
|
|
|
Cache expiry: 86400
|
|
|
|
|
|
Dynamic content: false
|
|
|
|
|
|
CPU time usage: 0.007 seconds
|
|
|
|
|
|
Real time usage: 0.011 seconds
|
|
|
|
|
|
Preprocessor visited node count: 4/1000000
|
|
|
|
|
|
Preprocessor generated node count: 16/1000000
|
|
|
|
|
|
Post‐expand include size: 2102/2097152 bytes
|
|
|
|
|
|
Template argument size: 0/2097152 bytes
|
|
|
|
|
|
Highest expansion depth: 2/40
|
|
|
|
|
|
Expensive parser function count: 0/100
|
|
|
|
|
|
Unstrip recursion depth: 0/20
|
|
|
|
|
|
Unstrip post‐expand size: 0/5000000 bytes
|
|
|
|
|
|
-->
|
|
|
|
|
|
<!--
|
|
|
|
|
|
Transclusion expansion time report (%,ms,calls,template)
|
|
|
|
|
|
100.00% 1.151 1 User:Simon/Reading,Writing_&amp;_Research_Methodologies_SI9/Outlining_content_of_workshops_22.05.19
|
|
|
|
|
|
100.00% 1.151 1 -total
|
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Saved in parser cache with key wdka_mw_mediadesign-mw_:pcache:idhash:31706-0!canonical and timestamp 20200620141728 and revision id 175203
|
|
|
|
|
|
-->
|
|
|
|
|
|
</div></DOCUMENT_FRAGMENT></div>
|
|
|
|
|
|
|
|
|
|
|
|
</body>
|
|
|
|
|
|
</html>
|
