OSBW Technical Design - Revision history

Johnmiedema: Replacing page with 'This page can be deleted'

2009-02-22T16:09:25Z

Replacing page with 'This page can be deleted'

Ch: /* Availability in Local Libraries */

2009-02-06T13:15:46Z

‎Availability in Local Libraries

Ch at 10:27, 6 February 2009

2009-02-06T10:27:41Z

Tomkeays: /* Sharing Code Modules */

2009-01-12T16:48:51Z

‎Sharing Code Modules

Johnmiedema at 14:31, 12 January 2009

2009-01-12T14:31:14Z

Johnmiedema at 14:30, 12 January 2009

2009-01-12T14:30:33Z

Johnmiedema at 12:59, 12 January 2009

2009-01-12T12:59:23Z

Johnmiedema: New page: Discussion of Technical Issues

2009-01-08T00:44:02Z

New page: Discussion of Technical Issues

New page

Discussion of Technical Issues

@@ Line 1: / Line 1: @@
-[[Open_Source_Book_Widgets|OSBW Main Page]]
+This page can be deleted
-−
-If you are a technical sort, interested in discussing technical issues, this is the place to do it.
-−
-= Availability in Local Libraries =
-−
-OpenBook currently provides a link to the WorldCat record as a way of showing availability in libraries. Thing is, WorldCat only shows availability for member libraries. I think it is possible to do more. If a library has a web-based catalogue, the catalogue is usually designed to be findable and it works in a consistent way. Usually it is a simple search box and button, defaulting to a keyword search, with results wrapped in hyperlink. Again, it is designed to be findable and consistent. Why not take advantage of that and use a little screen-scraping to see if a result exists for a given title? No doubt there are variations between catalogues, but how many library catalogues exist? And surely, a few simple rules per type could make things work.The user will be invited to configure their library using "the fuzzy library adaptor", a wizard that tests the catalogue. If the test fails, WorldCat can still be used. This feature is my current main interest. --[[User:Johnmiedema|Johnmiedema]] 06:30, 12 January 2009 (PST)
-−
-== Existing solutions & examples ==
-There's a web service called SeeAlso[http://www.gbv.de/wikis/cls/SeeAlso_Simple_Specification] that could be useful for availability check.
-−
-'''More information:'''
-* http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso
-−
-= Sharing Code Modules =
-−
-Why reinvent the wheel? My next steps with OpenBook will work toward separating the WordPress code from the generic code. This will begin to create PHP modules available for reuse by others. Are you doing the same?
-−
-One question: I'm writing in PHP. How about others?  --[[User:Johnmiedema|Johnmiedema]] 06:30, 12 January 2009 (PST)
-* PHP mainly (interested in Python, but no real experience) --[[User:Tomkeays|tomkeays]] 08:48, 12 January 2009 (PST)
-−
-= Live vs. Cached Design =
-−
-Currently OpenBook connects to Open Library via a live connection. If Open Library is down, OpenBook uses exception handling to prevent a hang. I have been thinking about the option of a cached design in which a widget can choose to download a cover image locally, and use static HTML for the rest. Once the HTML is written, the page would not ever have to call the datasource again. Thoughts? --[[User:Johnmiedema|Johnmiedema]] 06:30, 12 January 2009 (PST)
-−
-== Cached ==
-'''Pro'''
-* Data still available when a service is down
-* Less traffic for data providers
-* Less traffic for users of book widgets (blogs, etc.)
-* False data is not easily corrected
-−
-== Live ==
-'''Pro'''
-* Much more easy to integrate data in a website
-* No need for a database
-* Always fresh data. Corrections in data source are shown instantly
-−
-= Service Based Design =
-−
-This is just an idea that has been kicking around in my head. There are advantages to having a service based design. Right now, the heavy coding has to be done in WordPress, Drupal, Firefox, etc. How about a widget server that does all the work, returning the HTML. The only work that would have to be done on the client side is the call to the server. Dependence on a central server has its downsides too, e.g., downtime, but it could play an important role in the "book widget ecology". I have been thinking about designing OpenBook with a separate "server" module that encapsulates the functions I would hope to find on a server someday. --[[User:Johnmiedema|Johnmiedema]] 06:31, 12 January 2009 (PST)
-−
-[[Category:Open Source Book Widgets]]

← Older revision		Revision as of 13:15, 6 February 2009
Line 6:		Line 6:

	OpenBook currently provides a link to the WorldCat record as a way of showing availability in libraries. Thing is, WorldCat only shows availability for member libraries. I think it is possible to do more. If a library has a web-based catalogue, the catalogue is usually designed to be findable and it works in a consistent way. Usually it is a simple search box and button, defaulting to a keyword search, with results wrapped in hyperlink. Again, it is designed to be findable and consistent. Why not take advantage of that and use a little screen-scraping to see if a result exists for a given title? No doubt there are variations between catalogues, but how many library catalogues exist? And surely, a few simple rules per type could make things work.The user will be invited to configure their library using "the fuzzy library adaptor", a wizard that tests the catalogue. If the test fails, WorldCat can still be used. This feature is my current main interest. --[[User:Johnmiedema\|Johnmiedema]] 06:30, 12 January 2009 (PST)		OpenBook currently provides a link to the WorldCat record as a way of showing availability in libraries. Thing is, WorldCat only shows availability for member libraries. I think it is possible to do more. If a library has a web-based catalogue, the catalogue is usually designed to be findable and it works in a consistent way. Usually it is a simple search box and button, defaulting to a keyword search, with results wrapped in hyperlink. Again, it is designed to be findable and consistent. Why not take advantage of that and use a little screen-scraping to see if a result exists for a given title? No doubt there are variations between catalogues, but how many library catalogues exist? And surely, a few simple rules per type could make things work.The user will be invited to configure their library using "the fuzzy library adaptor", a wizard that tests the catalogue. If the test fails, WorldCat can still be used. This feature is my current main interest. --[[User:Johnmiedema\|Johnmiedema]] 06:30, 12 January 2009 (PST)
		+
		+	== Existing solutions & examples ==
		+	There's a web service called SeeAlso[http://www.gbv.de/wikis/cls/SeeAlso_Simple_Specification] that could be useful for availability check.
		+
		+	'''More information:'''
		+	* http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso

	= Sharing Code Modules =		= Sharing Code Modules =

@@ Line 3: / Line 3: @@
 If you are a technical sort, interested in discussing technical issues, this is the place to do it.
-=== Availability in Local Libraries ===
+= Availability in Local Libraries =
 OpenBook currently provides a link to the WorldCat record as a way of showing availability in libraries. Thing is, WorldCat only shows availability for member libraries. I think it is possible to do more. If a library has a web-based catalogue, the catalogue is usually designed to be findable and it works in a consistent way. Usually it is a simple search box and button, defaulting to a keyword search, with results wrapped in hyperlink. Again, it is designed to be findable and consistent. Why not take advantage of that and use a little screen-scraping to see if a result exists for a given title? No doubt there are variations between catalogues, but how many library catalogues exist? And surely, a few simple rules per type could make things work.The user will be invited to configure their library using "the fuzzy library adaptor", a wizard that tests the catalogue. If the test fails, WorldCat can still be used. This feature is my current main interest. --[[User:Johnmiedema|Johnmiedema]] 06:30, 12 January 2009 (PST)
-=== Sharing Code Modules ===
+= Sharing Code Modules =
 Why reinvent the wheel? My next steps with OpenBook will work toward separating the WordPress code from the generic code. This will begin to create PHP modules available for reuse by others. Are you doing the same?
@@ Line 14: / Line 14: @@
 * PHP mainly (interested in Python, but no real experience) --[[User:Tomkeays|tomkeays]] 08:48, 12 January 2009 (PST)
-=== Live vs. Cached Design ===
+= Live vs. Cached Design =
 Currently OpenBook connects to Open Library via a live connection. If Open Library is down, OpenBook uses exception handling to prevent a hang. I have been thinking about the option of a cached design in which a widget can choose to download a cover image locally, and use static HTML for the rest. Once the HTML is written, the page would not ever have to call the datasource again. Thoughts? --[[User:Johnmiedema|Johnmiedema]] 06:30, 12 January 2009 (PST)
-=== Service Based Design ===
+== Cached ==
 This is just an idea that has been kicking around in my head. There are advantages to having a service based design. Right now, the heavy coding has to be done in WordPress, Drupal, Firefox, etc. How about a widget server that does all the work, returning the HTML. The only work that would have to be done on the client side is the call to the server. Dependence on a central server has its downsides too, e.g., downtime, but it could play an important role in the "book widget ecology". I have been thinking about designing OpenBook with a separate "server" module that encapsulates the functions I would hope to find on a server someday. --[[User:Johnmiedema|Johnmiedema]] 06:31, 12 January 2009 (PST)

@@ Line 11: / Line 11: @@
 Why reinvent the wheel? My next steps with OpenBook will work toward separating the WordPress code from the generic code. This will begin to create PHP modules available for reuse by others. Are you doing the same?
-One question: I'm writing in PHP. How about others? --[[User:Johnmiedema|Johnmiedema]] 06:30, 12 January 2009 (PST)
+One question: I'm writing in PHP. How about others?  --[[User:Johnmiedema|Johnmiedema]] 06:30, 12 January 2009 (PST)
 === Live vs. Cached Design ===

← Older revision		Revision as of 14:31, 12 January 2009
Line 19:		Line 19:
	=== Service Based Design ===		=== Service Based Design ===

−	This is just an idea that has been kicking around in my head. There are advantages to having a service based design. Right now, the heavy coding has to be done in WordPress, Drupal, Firefox, etc. How about a widget server that does all the work, returning the HTML. The only work that would have to be done on the client side is the call to the server. Dependence on a central server has its downsides too, e.g., downtime, but it could play an important role in the "book widget ecology". I have been thinking about designing OpenBook with a separate "server" module that encapsulates the functions I would hope to find on a server someday. --~~	+	This is just an idea that has been kicking around in my head. There are advantages to having a service based design. Right now, the heavy coding has to be done in WordPress, Drupal, Firefox, etc. How about a widget server that does all the work, returning the HTML. The only work that would have to be done on the client side is the call to the server. Dependence on a central server has its downsides too, e.g., downtime, but it could play an important role in the "book widget ecology". I have been thinking about designing OpenBook with a separate "server" module that encapsulates the functions I would hope to find on a server someday. --[[User:Johnmiedema\|Johnmiedema]] 06:31, 12 January 2009 (PST)

← Older revision		Revision as of 14:30, 12 January 2009
Line 1:		Line 1:
	[[Open_Source_Book_Widgets\|OSBW Main Page]]		[[Open_Source_Book_Widgets\|OSBW Main Page]]

−	~~Discussion~~ of ~~Technical Issues~~	+	If you are a technical sort, interested in discussing technical issues, this is the place to do it.
		+
		+	=== Availability in Local Libraries ===
		+
		+	OpenBook currently provides a link to the WorldCat record as a way of showing availability in libraries. Thing is, WorldCat only shows availability for member libraries. I think it is possible to do more. If a library has a web-based catalogue, the catalogue is usually designed to be findable and it works in a consistent way. Usually it is a simple search box and button, defaulting to a keyword search, with results wrapped in hyperlink. Again, it is designed to be findable and consistent. Why not take advantage of that and use a little screen-scraping to see if a result exists for a given title? No doubt there are variations between catalogues, but how many library catalogues exist? And surely, a few simple rules per type could make things work.The user will be invited to configure their library using "the fuzzy library adaptor", a wizard that tests the catalogue. If the test fails, WorldCat can still be used. This feature is my current main interest. --[[User:Johnmiedema\|Johnmiedema]] 06:30, 12 January 2009 (PST)
		+
		+	=== Sharing Code Modules ===
		+
		+	Why reinvent the wheel? My next steps with OpenBook will work toward separating the WordPress code from the generic code. This will begin to create PHP modules available for reuse by others. Are you doing the same?
		+
		+	One question: I'm writing in PHP. How about others? --[[User:Johnmiedema\|Johnmiedema]] 06:30, 12 January 2009 (PST)
		+
		+	=== Live vs. Cached Design ===
		+
		+	Currently OpenBook connects to Open Library via a live connection. If Open Library is down, OpenBook uses exception handling to prevent a hang. I have been thinking about the option of a cached design in which a widget can choose to download a cover image locally, and use static HTML for the rest. Once the HTML is written, the page would not ever have to call the datasource again. Thoughts? --[[User:Johnmiedema\|Johnmiedema]] 06:30, 12 January 2009 (PST)
		+
		+	=== Service Based Design ===
		+
		+	This is just an idea that has been kicking around in my head. There are advantages to having a service based design. Right now, the heavy coding has to be done in WordPress, Drupal, Firefox, etc. How about a widget server that does all the work, returning the HTML. The only work that would have to be done on the client side is the call to the server. Dependence on a central server has its downsides too, e.g., downtime, but it could play an important role in the "book widget ecology". I have been thinking about designing OpenBook with a separate "server" module that encapsulates the functions I would hope to find on a server someday. --~~

← Older revision		Revision as of 12:59, 12 January 2009
Line 1:		Line 1:
		+	[[Open_Source_Book_Widgets\|OSBW Main Page]]
		+
	Discussion of Technical Issues		Discussion of Technical Issues