Development Objectives for 0.80
-------------------------------

1)	Database changes

I am planning to make several database structural changes in
0.70.  In order to lessen the impact I am going to make as 
many of the forseeable changes in this release even if the
functionality to use them is not developed until later.

Tables to be updated:
	user
		* Include more user details, such as 'phone number',
		'address details', etc.

		I am also considering adding a new 's_location'
		table for the location field.

		The patch would perform a: 
			SELECT distinct LOWER(location)
			FROM user

		... to populate the s_location table.  From then on
		the location input field would be a SELECT object.

		I think that there should be a tighter control
		on this field, so it can be used for more things than
		it is now.

		For instance we could generate lists of users at the
		same location; and graph item distribution per location,
		etc.

	s_location
		* New table, with columns:
			location_cd (FK to user.location)
			description
			perhaps an address?

	borrowed_item
		* Borrower ratings
			Add columns:
				rating
				comment

			The rating would be something similiar to the review table.
			A new s_attribute_type of 'S_B_RATING' would provide the
			options for the rating.

			The comment would allow the Lender to include comments
			about any issues encountered with the borrower.  For 
			example the disc was scratched!

		* Addition of a 'transaction_log' field.  This field would be
		something like VARCHAR(2000).  It would be populated with
		all details of the borrow transaction including:

			Emails sent regarding the borrowed_item activity.
			When an item is changed from 'reserved' to 'checked-out' 
			The date this happened. 
			
			I am not sure what the format of the log will be, but 
			perhaps an XML structure might be useful.

			<entry date="10/10/2002 23:11:23" type="status_change">
				<status old_value="R" new_value="B">
				<email>
				<![CDATA[
					Contents of email message.
				]!>
				</email>
			</entry>

			Or just plain text:

			# ----------------- START ENTRY -------------------------
			Date: 10/10/2002 23:11:23
			Status: Old: R; New: B

			Contents of email message.
			# ------------------ END ENTRY --------------------------

			Or if we wanted a fully normalised solution (Which I think
			would be overkill), we could add a new table.






			
									
