User:Alexander Roidl/itl proposal - Revision history

Alexander Roidl at 16:50, 9 June 2018

2018-06-09T16:50:18Z

← Older revision		Revision as of 18:50, 9 June 2018
Line 1:		Line 1:
	= Project Proposal =		= Project Proposal =

	~~https://pzwiki.wdka.nl/mediadesign/X-Lib~~		[[XPPL]]
	[[File:Screen Shot 2018-05-13 at 22.50.36.png\|thumbnail]]		[[File:Screen Shot 2018-05-13 at 22.50.36.png\|thumbnail]]
	[[File:Screen Shot 2018-05-14 at 23.57.30.png\|thumbnail\|local use of bibliotecha]]		[[File:Screen Shot 2018-05-14 at 23.57.30.png\|thumbnail\|local use of bibliotecha]]
	[[File:Screen Shot 2018-05-14 at 23.58.21.png\|thumbnail\|based on JSON structure]]		[[File:Screen Shot 2018-05-14 at 23.58.21.png\|thumbnail\|based on JSON structure]]


	== Interface for Interface ==		== Interface for Interface ==
	=== The infrastructure of the library ===		=== The infrastructure of the library ===

Alexander Roidl at 16:42, 9 June 2018

2018-06-09T16:42:42Z

@@ Line 5: / Line 5: @@
 [[File:Screen Shot 2018-05-14 at 23.57.30.png|thumbnail|local use of bibliotecha]]
 [[File:Screen Shot 2018-05-14 at 23.58.21.png|thumbnail|based on JSON structure]]
@@ Line 46: / Line 38: @@
 * different access points to the library
 ** interested in how the library opens up to the public
 == Ideas & Thoughts ==

Alexander Roidl at 09:25, 1 June 2018

2018-06-01T09:25:12Z

← Older revision		Revision as of 11:25, 1 June 2018
Line 8:		Line 8:

	== From Reading to Seeing ==		== From Reading to Seeing ==
	What is the position of the library?		*What is the position of the library?
	Does the library make books visible or readable?		*Does the library make books visible or readable?
	How can a book be seen in the interface?		*How can a book be seen in the interface?
	'''How can the library be read?''' -> if the books are inside the library as texts		*'''How can the library be read?''' -> if the books are inside the library as texts
	Does the digital library prefer the text over the book?		*Does the digital library prefer the text over the book?

Alexander Roidl at 09:24, 1 June 2018

2018-06-01T09:24:49Z

← Older revision		Revision as of 11:24, 1 June 2018
Line 11:		Line 11:
	Does the library make books visible or readable?		Does the library make books visible or readable?
	How can a book be seen in the interface?		How can a book be seen in the interface?
			'''How can the library be read?''' -> if the books are inside the library as texts
			Does the digital library prefer the text over the book?

Alexander Roidl at 09:23, 1 June 2018

2018-06-01T09:23:16Z

← Older revision		Revision as of 11:23, 1 June 2018
Line 5:		Line 5:
	[[File:Screen Shot 2018-05-14 at 23.57.30.png\|thumbnail\|local use of bibliotecha]]		[[File:Screen Shot 2018-05-14 at 23.57.30.png\|thumbnail\|local use of bibliotecha]]
	[[File:Screen Shot 2018-05-14 at 23.58.21.png\|thumbnail\|based on JSON structure]]		[[File:Screen Shot 2018-05-14 at 23.58.21.png\|thumbnail\|based on JSON structure]]


			== From Reading to Seeing ==
			What is the position of the library?
			Does the library make books visible or readable?
			How can a book be seen in the interface?

Alexander Roidl: /* Interface for Interface */

2018-05-27T18:09:33Z

Interface for Interface

← Older revision		Revision as of 20:09, 27 May 2018
Line 10:		Line 10:
	=== The infrastructure of the library ===		=== The infrastructure of the library ===
	<onlyinclude>		<onlyinclude>
			[[File:Screen Shot 2018-05-27 at 20.06.40.png\|thumbnail]]
	<!--''what? (250)'' -->		<!--''what? (250)'' -->
	For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.		For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.

Alexander Roidl: /* Interface for Interface */

2018-05-27T17:56:53Z

Interface for Interface

← Older revision		Revision as of 19:56, 27 May 2018
Line 9:		Line 9:
	== Interface for Interface ==		== Interface for Interface ==
	=== The infrastructure of the library ===		=== The infrastructure of the library ===
			<onlyinclude>
	<!--''what? (250)'' -->		<!--''what? (250)'' -->
	For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.		For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.
Line 19:		Line 19:
	<!--''why is it necessary? (125)''-->		<!--''why is it necessary? (125)''-->
	The Library needs a profound structure to be maintainable. A dynamic structure and different ways of access provide for a good basis to keep it alive and to also not display the »only truth« of how books can be stored and interfaced. The API offers the opportunity to query the database and use it in a much wider sense than we can think of now.		The Library needs a profound structure to be maintainable. A dynamic structure and different ways of access provide for a good basis to keep it alive and to also not display the »only truth« of how books can be stored and interfaced. The API offers the opportunity to query the database and use it in a much wider sense than we can think of now.
			</onlyinclude>
	<!--''Relation to project as whole (how does it interface with the rest of the PZI library project)''-->		<!--''Relation to project as whole (how does it interface with the rest of the PZI library project)''-->
	The infrastructure of the library provides all the interfaces with the necessary connection to the database. Therefore it connects all the interfaces to it in its database. The library you see is always only a potential interface to it.		The infrastructure of the library provides all the interfaces with the necessary connection to the database. Therefore it connects all the interfaces to it in its database. The library you see is always only a potential interface to it.

Alexander Roidl: /* The infrastructure of the library */

2018-05-27T17:54:15Z

The infrastructure of the library

← Older revision		Revision as of 19:54, 27 May 2018
Line 12:		Line 12:
	<!--''what? (250)'' -->		<!--''what? (250)'' -->
	For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.		For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.
	The structure of the library is built around a database, that can be accessed from several points and in different ways. The infrastructure is built in such a way, that it can be modified easily. The platform itself will be hosted on a PI, that serves the library. The Library can be interfaced in programmatic as well as in graphical ways. The fundamental basis of the library is the database, but it shouldn’t hide within it self. The library should contain the books not only as downloadable pdf/ebook–book files, but also include the actually text in some form. To »convert[s] an image of a book page back into language – searchable, retrievable, scalable, and translatable. In the future most designers will be creating reading experiences not book designs.« (Blauvelt, 2010) This compiled all together ~~ask~~ the question on how the library can be read.		The structure of the library is built around a database, that can be accessed from several points and in different ways. The infrastructure is built in such a way, that it can be modified easily. The platform itself will be hosted on a PI, that serves the library. The Library can be interfaced in programmatic as well as in graphical ways. The fundamental basis of the library is the database, but it shouldn’t hide within it self. The library should contain the books not only as downloadable pdf/ebook–book files, but also include the actually text in some form. To »convert[s] an image of a book page back into language – searchable, retrievable, scalable, and translatable. In the future most designers will be creating reading experiences not book designs.« (Blauvelt, 2010) This compiled all together asks the question on how the library can be read.

	<!--''how will it be made? (125)''-->		<!--''how will it be made? (125)''-->

Alexander Roidl: /* The infrastructure of the library */

2018-05-27T17:53:57Z

The infrastructure of the library

← Older revision		Revision as of 19:53, 27 May 2018
Line 11:		Line 11:

	<!--''what? (250)'' -->		<!--''what? (250)'' -->

	For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.		For the XPPL I am working on the infrastructure of the library and how to make this structures accessible in a useful but also in a playful way.
	The structure of the library is built around a database, that can be accessed from several points and in different ways. The infrastructure is built in such a way, that it can be modified easily. The platform itself will be hosted on a PI, that serves the library. The Library can be interfaced in programmatic as well as in graphical ways. The fundamental basis of the library is the database, but it shouldn’t hide within it self. The library should contain the books not only as downloadable pdf/ebook–book files, but also include the actually text in some form. To »convert[s] an image of a book page back into language – searchable, retrievable, scalable, and translatable. In the future most designers will be creating reading experiences not book designs.« (Blauvelt, 2010) This compiled all together ask the question on how the library can be read.		The structure of the library is built around a database, that can be accessed from several points and in different ways. The infrastructure is built in such a way, that it can be modified easily. The platform itself will be hosted on a PI, that serves the library. The Library can be interfaced in programmatic as well as in graphical ways. The fundamental basis of the library is the database, but it shouldn’t hide within it self. The library should contain the books not only as downloadable pdf/ebook–book files, but also include the actually text in some form. To »convert[s] an image of a book page back into language – searchable, retrievable, scalable, and translatable. In the future most designers will be creating reading experiences not book designs.« (Blauvelt, 2010) This compiled all together ask the question on how the library can be read.

	<!--''how will it be made? (125)''-->		<!--''how will it be made? (125)''-->

	The library will provide a framework and API to be accessible. It is a self-programmed environment written in python and freely accessible and forkable for anybody. Therefore it integrates the matters of the Experimental Publishing Course perfectly. »Users« (= non registered visitors within the network) are able to contribute to the library. Whereas »Visitors« can only view the catalogue and its structure.		The library will provide a framework and API to be accessible. It is a self-programmed environment written in python and freely accessible and forkable for anybody. Therefore it integrates the matters of the Experimental Publishing Course perfectly. »Users« (= non registered visitors within the network) are able to contribute to the library. Whereas »Visitors« can only view the catalogue and its structure.

	<!--''why is it necessary? (125)''-->		<!--''why is it necessary? (125)''-->

	The Library needs a profound structure to be maintainable. A dynamic structure and different ways of access provide for a good basis to keep it alive and to also not display the »only truth« of how books can be stored and interfaced. The API offers the opportunity to query the database and use it in a much wider sense than we can think of now.		The Library needs a profound structure to be maintainable. A dynamic structure and different ways of access provide for a good basis to keep it alive and to also not display the »only truth« of how books can be stored and interfaced. The API offers the opportunity to query the database and use it in a much wider sense than we can think of now.

	<!--''Relation to project as whole (how does it interface with the rest of the PZI library project)''-->		<!--''Relation to project as whole (how does it interface with the rest of the PZI library project)''-->

	The infrastructure of the library provides all the interfaces with the necessary connection to the database. Therefore it connects all the interfaces to it in its database. The library you see is always only a potential interface to it.		The infrastructure of the library provides all the interfaces with the necessary connection to the database. Therefore it connects all the interfaces to it in its database. The library you see is always only a potential interface to it.

	<!--''Relation to your self-directed research (how does it interface with previous work or abiding interests? what new interests are you following?)''-->		<!--''Relation to your self-directed research (how does it interface with previous work or abiding interests? what new interests are you following?)''-->

	This projects connects to my previous interests in databases and how different programming approaches interface differently with the latter. Different ways of reading the database means different interfaces. I want to explore the structure of database driven projects and how these structures can transform.		This projects connects to my previous interests in databases and how different programming approaches interface differently with the latter. Different ways of reading the database means different interfaces. I want to explore the structure of database driven projects and how these structures can transform.

Alexander Roidl: /* The infrastructure of the library */

2018-05-27T17:53:38Z

The infrastructure of the library