OSBW RequirementsUseCases - Revision history

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

2009-02-22T16:01:03Z

Replacing page with 'This page can be deleted'

Ch at 13:15, 6 February 2009

2009-02-06T13:15:29Z

Johnmiedema at 14:08, 12 January 2009

2009-01-12T14:08:04Z

Johnmiedema at 14:07, 12 January 2009

2009-01-12T14:07:09Z

Johnmiedema at 14:06, 12 January 2009

2009-01-12T14:06:28Z

Johnmiedema at 12:59, 12 January 2009

2009-01-12T12:59:07Z

Johnmiedema at 00:41, 8 January 2009

2009-01-08T00:41:46Z

Johnmiedema: New page: I thought it might be handier at the start to combine requirements and use cases into this single page. This is a statement of actors/users and the functions that open source book widgets...

2009-01-08T00:40:43Z

New page: I thought it might be handier at the start to combine requirements and use cases into this single page. This is a statement of actors/users and the functions that open source book widgets...

New page

I thought it might be handier at the start to combine requirements and use cases into this single page.

This is a statement of actors/users and the functions that open source book widgets should perform.

@@ Line 1: / Line 1: @@
-[[Open_Source_Book_Widgets|OSBW Main Page]]
+This page can be deleted
-−
-This is a statement of actors/users and the functions that open source book widgets should perform. This discussion is non-technical in nature. It answers the question: what do you want book widgets to do for you?
-−
-== Actors/Users ==
-−
-Who uses book widgets? Two general categories: book widget authors interested in sharing book information, and book widget users interested in using book information. That said, there are many kinds of authors and users. It may be useful to distinguish librarians and library users as a distinct group.
-−
-== Functions ==
-−
-'''As a widget author:'''
-* Provide book covers and other bibliographic data for readers of my blog.
-* Easily select from different data sources, using various identifiers (not just ISBN), be able to select from multiple versions of given title, set options for linking, etc.
-* Access data sources for independent writers, publishers, etc. If these records are not in the data source, I would like to be able to add them.
-* Credit contributors to a book: artists, illustrators, translators, editors, etc. Credit can take the form of being named, but also through a link to the contributors website, if available.
-* Respect copyright on book cover images. (My research on this indicates that thumbnails are fair use for book covers of copyrighted materials. If it can be determined that a book cover is public domain, copying full covers is legal. --[[User:Johnmiedema|Johnmiedema]] 06:06, 12 January 2009 (PST)).
-−
-'''As a widget author who manages a library website:'''
-* I am targeting patrons of my own library. I would like to be able to configure the widget to show items in my specific library.
-−
-'''As a widget user:'''
-* Link to detailed book data.
-* View books online where available.
-* Read reviews and recommended titles.
-* Connect to social data about books.
-* See availability of an item in my libraries and bookstores. Libraries should include those that are not OCLC members. Bookstores should include independent bookstores. (Of course, this requirement is a significant design issue -- see Technical Design for more discussion).
-* Add virtual books to my personal "shelf".
-−
-'''As a third-party developer:'''
-* I would like book widgets to be designed for auto-detection by other applications. E.g. COinS or unAPI for detection by Zotero and other applications.
-* Consume book data that is XHTML compliant.
-−
-[[Category:Open Source Book Widgets]]

← Older revision		Revision as of 13:15, 6 February 2009
Line 30:		Line 30:
	* I would like book widgets to be designed for auto-detection by other applications. E.g. COinS or unAPI for detection by Zotero and other applications.		* I would like book widgets to be designed for auto-detection by other applications. E.g. COinS or unAPI for detection by Zotero and other applications.
	* Consume book data that is XHTML compliant.		* Consume book data that is XHTML compliant.
		+
		+	[[Category:Open Source Book Widgets]]

@@ Line 1: / Line 1: @@
 [[Open_Source_Book_Widgets|OSBW Main Page]]
-I thought it might be handier at the start to combine requirements and use cases into this single page.
+This is a statement of actors/users and the functions that open source book widgets should perform. This discussion is non-technical in nature. It answers the question: what do you want book widgets to do for you?
-−
-This is a statement of actors/users and the functions that open source book widgets should perform. Non-technical in nature.
 == Actors/Users ==

@@ Line 11: / Line 11: @@
 == Functions ==
-As a widget author:
+'''As a widget author:'''
 * Provide book covers and other bibliographic data for readers of my blog.
 * Easily select from different data sources, using various identifiers (not just ISBN), be able to select from multiple versions of given title, set options for linking, etc.
@@ Line 18: / Line 18: @@
 * Respect copyright on book cover images. (My research on this indicates that thumbnails are fair use for book covers of copyrighted materials. If it can be determined that a book cover is public domain, copying full covers is legal. --[[User:Johnmiedema|Johnmiedema]] 06:06, 12 January 2009 (PST)).
-As a widget author who manages a library website:
+'''As a widget author who manages a library website:'''
 * I am targeting patrons of my own library. I would like to be able to configure the widget to show items in my specific library.
-As a widget user:
+'''As a widget user:'''
 * Link to detailed book data.
 * View books online where available.
@@ Line 29: / Line 29: @@
 * Add virtual books to my personal "shelf".
-As a third-party developer:
+'''As a third-party developer:'''
 * I would like book widgets to be designed for auto-detection by other applications. E.g. COinS or unAPI for detection by Zotero and other applications.
 * Consume book data that is XHTML compliant.

← Older revision		Revision as of 14:06, 12 January 2009
Line 4:		Line 4:

	This is a statement of actors/users and the functions that open source book widgets should perform. Non-technical in nature.		This is a statement of actors/users and the functions that open source book widgets should perform. Non-technical in nature.
		+
		+	== Actors/Users ==
		+
		+	Who uses book widgets? Two general categories: book widget authors interested in sharing book information, and book widget users interested in using book information. That said, there are many kinds of authors and users. It may be useful to distinguish librarians and library users as a distinct group.
		+
		+	== Functions ==
		+
		+	As a widget author:
		+	* Provide book covers and other bibliographic data for readers of my blog.
		+	* Easily select from different data sources, using various identifiers (not just ISBN), be able to select from multiple versions of given title, set options for linking, etc.
		+	* Access data sources for independent writers, publishers, etc. If these records are not in the data source, I would like to be able to add them.
		+	* Credit contributors to a book: artists, illustrators, translators, editors, etc. Credit can take the form of being named, but also through a link to the contributors website, if available.
		+	* Respect copyright on book cover images. (My research on this indicates that thumbnails are fair use for book covers of copyrighted materials. If it can be determined that a book cover is public domain, copying full covers is legal. --[[User:Johnmiedema\|Johnmiedema]] 06:06, 12 January 2009 (PST)).
		+
		+	As a widget author who manages a library website:
		+	* I am targeting patrons of my own library. I would like to be able to configure the widget to show items in my specific library.
		+
		+	As a widget user:
		+	* Link to detailed book data.
		+	* View books online where available.
		+	* Read reviews and recommended titles.
		+	* Connect to social data about books.
		+	* See availability of an item in my libraries and bookstores. Libraries should include those that are not OCLC members. Bookstores should include independent bookstores. (Of course, this requirement is a significant design issue -- see Technical Design for more discussion).
		+	* Add virtual books to my personal "shelf".
		+
		+	As a third-party developer:
		+	* I would like book widgets to be designed for auto-detection by other applications. E.g. COinS or unAPI for detection by Zotero and other applications.
		+	* Consume book data that is XHTML compliant.

← Older revision		Revision as of 12:59, 12 January 2009
Line 1:		Line 1:
		+	[[Open_Source_Book_Widgets\|OSBW Main Page]]
		+
	I thought it might be handier at the start to combine requirements and use cases into this single page.		I thought it might be handier at the start to combine requirements and use cases into this single page.

	This is a statement of actors/users and the functions that open source book widgets should perform. Non-technical in nature.		This is a statement of actors/users and the functions that open source book widgets should perform. Non-technical in nature.

← Older revision		Revision as of 00:41, 8 January 2009
Line 1:		Line 1:
	I thought it might be handier at the start to combine requirements and use cases into this single page.		I thought it might be handier at the start to combine requirements and use cases into this single page.

−	This is a statement of actors/users and the functions that open source book widgets should perform.	+	This is a statement of actors/users and the functions that open source book widgets should perform. Non-technical in nature.