Database of resources

The database should be an open structure in which WHICH resources to map (ie. are considered useful) is open.

The point is to not only gather concrete data as to the extent and location of resources, but to find out actually what kind of resources are considered useful to people and worth mapping and sharing.

The database is therefore simultaneously for data gathering, communty building and research, and its an art project about needs, consumption and our real environment.

Allocation of keywords will build up relationships between resources and services in a multilayered way and allow different kinds of searches.  so that the services themselves and an idea of their various subjective and real qualities (eg. are they free? are they corporate? are they volunteer run? are they friendly?)

eg.
easyeverything may be allocated the keywords:

internet access, public, cheap, corporate, crowded


local library may be allocated the keywords:

internet access, public, cheap, local authority, quiet


walking down the thames path may be allocated the keywords:

free, public, non-corporate, outdoors, educational


56A bike workshop may be allocated the keywords:

free, volunteer run, public, transportation, do-it-yourself


Can collaborate with consume who have been buidling their "nodes database" on the visualisation/mapping elements. 


database structure...

table 1

ID number (primary key)
Resource name (not null)
Building name/flat number
street address
street address2
postcode (not null)
contact name
contact number


table 2
keywords


table 3
?map coordinates??



- do you want site members who enter the data? and whose data is assigned to them. so you can make a personal map of anybody?

OR is this too much personal data (probably...)