User:Tash/Special Issue 06 - Revision history

Tash: /* Research and contribution to XPPL */

2018-06-15T06:27:38Z

Research and contribution to XPPL

← Older revision		Revision as of 08:27, 15 June 2018
Line 244:		Line 244:
	* Using Flask to render an HTML page, SQLalchemy to track requests in the database, and Weasyprint to write it to PDF		* Using Flask to render an HTML page, SQLalchemy to track requests in the database, and Weasyprint to write it to PDF
	[[File:Xppl-potential.png\|700px\|thumbnail\|center]]		[[File:Xppl-potential.png\|700px\|thumbnail\|center]]

			==Things to work on ==
			* expand the search form to reflect and play with metadata
			* connect search form more closely with annotations and stacks
			* uploading only by stacks?
			* categorization
			* database --> how to make it stable enough to spread??
			* installation --> how to make it more user friendly?

Tash: /* Research and contribution to XPPL */

2018-06-15T06:16:12Z

Research and contribution to XPPL

← Older revision		Revision as of 08:16, 15 June 2018
Line 16:		Line 16:
	HOW can you GET data that's MISSING ?! E.G. from LibGen: where is the UPLOAD DATA? what could we do with it?		HOW can you GET data that's MISSING ?! E.G. from LibGen: where is the UPLOAD DATA? what could we do with it?

	Simple test to highlight absent information:		Simple test to highlight absent information: <br>
	In LibGen's catalogue CSV there are rows without titles.		In LibGen's catalogue CSV there are rows without titles.
	How to search for blanks?		How to search for blanks?

Tash at 06:15, 15 June 2018

2018-06-15T06:15:25Z

← Older revision		Revision as of 08:15, 15 June 2018
Line 1:		Line 1:
	=Research and contribution to XPPL=		=Research and contribution to XPPL=
	=== Research questions ===		=== Research questions ===
			[[File:Xppl-potential2.png\|600px\|frameless\|right]]
	on interface:		on interface:
	* How do you engage with UNSTABLE libraries? Can we design reading / searching interfaces that are able to represent uncertainty, locate outsides, explore provenances?		* How do you engage with UNSTABLE libraries? Can we design reading / searching interfaces that are able to represent uncertainty, locate outsides, explore provenances?
Line 16:		Line 16:
	HOW can you GET data that's MISSING ?! E.G. from LibGen: where is the UPLOAD DATA? what could we do with it?		HOW can you GET data that's MISSING ?! E.G. from LibGen: where is the UPLOAD DATA? what could we do with it?

	Simple test to highlight absent information: in LibGen's catalogue CSV there are ~~row~~ without titles		Simple test to highlight absent information:
			In LibGen's catalogue CSV there are rows without titles.
	How to search for blanks?		How to search for blanks?

Tash at 06:09, 15 June 2018

2018-06-15T06:09:59Z

← Older revision		Revision as of 08:09, 15 June 2018
Line 228:		Line 228:
	* Getting metadata which makes explicit the cultural act of uploading and downloading		* Getting metadata which makes explicit the cultural act of uploading and downloading
	* Giving form to the current collection		* Giving form to the current collection
	[[File:Screen Shot 2018-06-15 at 07.43.38.png\|~~580px~~\|thumbnail\|left]][[File:Xppl-upload1.png\|~~580px~~\|thumbnail\|right]]		[[File:Screen Shot 2018-06-15 at 07.43.38.png\|550px\|thumbnail\|left]][[File:Xppl-upload1.png\|550px\|thumbnail\|right]]

	<br clear=all>		<br clear=all>
Line 234:		Line 234:
	* Connecting the search form to the chat form		* Connecting the search form to the chat form
	* Add opportunities for contact between pirates, which works together with the annotations layer		* Add opportunities for contact between pirates, which works together with the annotations layer
	[[File:Xppl-search2.png\|~~580px~~\|thumbnail\|left]]		[[File:Xppl-search2.png\|550px\|thumbnail\|left]]
	[[File:Screen Shot 2018-06-15 at 07.47.10.png\|~~580px~~\|thumbnail\|right]]		[[File:Screen Shot 2018-06-15 at 07.47.10.png\|550px\|thumbnail\|right]]

	<br clear=all>		<br clear=all>

Tash at 06:09, 15 June 2018

2018-06-15T06:09:00Z

← Older revision		Revision as of 08:09, 15 June 2018
Line 228:		Line 228:
	* Getting metadata which makes explicit the cultural act of uploading and downloading		* Getting metadata which makes explicit the cultural act of uploading and downloading
	* Giving form to the current collection		* Giving form to the current collection
	[[File:Screen Shot 2018-06-15 at 07.43.38.png\|~~600px~~\|thumbnail\|left]][[File:Xppl-upload1.png\|~~600px~~\|thumbnail\|right]]		[[File:Screen Shot 2018-06-15 at 07.43.38.png\|580px\|thumbnail\|left]][[File:Xppl-upload1.png\|580px\|thumbnail\|right]]

	<br clear=all>		<br clear=all>
Line 234:		Line 234:
	* Connecting the search form to the chat form		* Connecting the search form to the chat form
	* Add opportunities for contact between pirates, which works together with the annotations layer		* Add opportunities for contact between pirates, which works together with the annotations layer
	[[File:Xppl-search2.png\|~~600px~~\|thumbnail\|left]]		[[File:Xppl-search2.png\|580px\|thumbnail\|left]]
	[[File:Screen Shot 2018-06-15 at 07.47.10.png\|~~600px~~\|thumbnail\|right]]		[[File:Screen Shot 2018-06-15 at 07.47.10.png\|580px\|thumbnail\|right]]

			<br clear=all>
			== The 'Potential PDF' ==
			* Traces of the 'gaps' in the collection
			* Producing a new item which can be fed back into the collection
			* Using Flask to render an HTML page, SQLalchemy to track requests in the database, and Weasyprint to write it to PDF
			[[File:Xppl-potential.png\|700px\|thumbnail\|center]]

Tash at 06:05, 15 June 2018

2018-06-15T06:05:58Z

← Older revision		Revision as of 08:05, 15 June 2018
Line 228:		Line 228:
	* Getting metadata which makes explicit the cultural act of uploading and downloading		* Getting metadata which makes explicit the cultural act of uploading and downloading
	* Giving form to the current collection		* Giving form to the current collection
	[[File:Screen Shot 2018-06-15 at 07.43.38.png\|~~500px~~\|thumbnail\|left]][[File:Xppl-upload1.png\|~~500px~~\|thumbnail\|right]]		[[File:Screen Shot 2018-06-15 at 07.43.38.png\|600px\|thumbnail\|left]][[File:Xppl-upload1.png\|600px\|thumbnail\|right]]

	<br clear=all>		<br clear=all>
	== Sociality of the interface ==		== Sociality of the interface ==
	[[File:Xppl-search2.png\|~~500px~~\|thumbnail\|left]]		* Connecting the search form to the chat form
	[[File:Screen Shot 2018-06-15 at 07.47.10\|~~400px~~\|thumbnail\|right]]		* Add opportunities for contact between pirates, which works together with the annotations layer
			[[File:Xppl-search2.png\|600px\|thumbnail\|left]]
			[[File:Screen Shot 2018-06-15 at 07.47.10.png\|600px\|thumbnail\|right]]

Tash at 06:04, 15 June 2018

2018-06-15T06:04:18Z

@@ Line 222: / Line 222: @@
 <br>
-== Extracting images from PDF ==
+[[File:Xppl-search1.png|600px|thumbnail|center]
-Option 1: using
+== Upload form ==
-pdfimages -j magnet_reader_3_processual_publishing_actual_gestures.pdf ./pdfimages
+* Getting metadata which makes explicit the cultural act of uploading and downloading
-Option 2: python script which looks for start bytes and endbytes of jpg files:
+<br clear=all>
-[[File:img_pdfscript.png|400px|thumbnail|right| python script extracts less images, only recognizes complete jpgs]]
+== Sociality of the interface ==
+[[File:Xppl-search2.png|500px|thumbnail|left]]
-<source lang=python>
+[[File:Screen Shot 2018-06-15 at 07.47.10|400px|thumbnail|right]]

Tash: /* Search functionality (Concept) */

2018-06-10T13:44:54Z

Search functionality (Concept)

← Older revision		Revision as of 15:44, 10 June 2018
Line 44:		Line 44:

	Considerations:		Considerations:
	* How to bring forward the distributed and enunciative materiality of the library? This means being more transparent about labour		* How to bring forward the distributed and enunciative materiality of the library? This means being more transparent about labour, traces
	* Interface design which challenges the user-as-consumer model:		* Interface design which challenges the user-as-consumer model:
	** "Sustained interpretative engagement, not efficient completion of tasks, would be the desired outcome." http://www.digitalhumanities.org/dhq/vol/7/1/000143/000143.html		** "Sustained interpretative engagement, not efficient completion of tasks, would be the desired outcome." http://www.digitalhumanities.org/dhq/vol/7/1/000143/000143.html

Tash: /* Search functionality (Concept) */

2018-06-10T13:00:23Z

Search functionality (Concept)

← Older revision		Revision as of 15:00, 10 June 2018
Line 52:		Line 52:
	** "Sameness and difference as guiding principles of classification seem obvious, but are actually fundamental characteristics specifically related to Western culture. [...] Classifications such as the DDC set up pigeonholes for certain samenesses. Dewey himself recognized that dividing all of knowledge into tens is absurd in any theoretical sense, but asserted that because it is efficient in practice – like pigeonholes on a nineteenth-century businessman's desk– it is justifiable."		** "Sameness and difference as guiding principles of classification seem obvious, but are actually fundamental characteristics specifically related to Western culture. [...] Classifications such as the DDC set up pigeonholes for certain samenesses. Dewey himself recognized that dividing all of knowledge into tens is absurd in any theoretical sense, but asserted that because it is efficient in practice – like pigeonholes on a nineteenth-century businessman's desk– it is justifiable."

	[[File:Classification olson.png\|~~900px~~]]		[[File:Classification olson.png\|1000px\|center]]

	* Showing what is included & excluded, remembering feminist methodologies: Interesting project on the politics of the search engine: http://www.feministsearchtool.nl/		* Showing what is included & excluded, remembering feminist methodologies: Interesting project on the politics of the search engine: http://www.feministsearchtool.nl/

Tash: /* Search functionality (Concept) */

2018-06-10T12:59:41Z

Search functionality (Concept)

← Older revision		Revision as of 14:59, 10 June 2018
Line 47:		Line 47:
	* Interface design which challenges the user-as-consumer model:		* Interface design which challenges the user-as-consumer model:
	** "Sustained interpretative engagement, not efficient completion of tasks, would be the desired outcome." http://www.digitalhumanities.org/dhq/vol/7/1/000143/000143.html		** "Sustained interpretative engagement, not efficient completion of tasks, would be the desired outcome." http://www.digitalhumanities.org/dhq/vol/7/1/000143/000143.html
	* Upload form and search form are two sides of the same coin. Classification informs query and vice versa. So how to insert new questions into this process~~? What assumptions can we shake up~~?		* Upload form and search form are two sides of the same coin. Classification informs query and vice versa. So how to insert new questions into this process?
	** "Searching in a collection of [amassed/assembled] [tangible] documents (ie. bookshelf) is different from searching in a systematically structured repository (library) and even more so from searching in a digital repository (digital library). Not that they are mutually exclusive. One can devise structures and algorithms to search through a printed text, or read books in a library one by one. They are rather [models] [embodying] various [processes] associated with the query. These properties of the query might be called [the sequence], the structure and the index. If they are present in the ways of querying documents, and we will return to this issue, are they persistent within the inquiry as such?" https://monoskop.org/Talks/Poetics_of_Research		** "Searching in a collection of [amassed/assembled] [tangible] documents (ie. bookshelf) is different from searching in a systematically structured repository (library) and even more so from searching in a digital repository (digital library). Not that they are mutually exclusive. One can devise structures and algorithms to search through a printed text, or read books in a library one by one. They are rather [models] [embodying] various [processes] associated with the query. These properties of the query might be called [the sequence], the structure and the index. If they are present in the ways of querying documents, and we will return to this issue, are they persistent within the inquiry as such?" https://monoskop.org/Talks/Poetics_of_Research
	* On hierarchical systems of classification and how they rely on cultural assumptions: https://journals.ala.org/index.php/lrts/article/view/4913		* On hierarchical systems of classification and how they rely on cultural assumptions: https://journals.ala.org/index.php/lrts/article/view/4913
Line 54:		Line 54:
	[[File:Classification olson.png\|900px]]		[[File:Classification olson.png\|900px]]

	* Showing what is included & excluded, remembering feminist methodologies: Interesting project on the politics of the search engine: http://www.feministsearchtool.nl/		* Showing what is included & excluded, remembering feminist methodologies: Interesting project on the politics of the search engine: http://www.feministsearchtool.nl/



	== Search functionality (Tech) ==		== Search functionality (Tech) ==