Hi, Terry,
This conversation goes in two directions. One is appropriately public. The
other should be off-list.
The public part involves ideas and suggestions for what a respository should
be -- what should it contain? what scope and scale should it archive? what
features would people value? I'm interested, but for the most part, I plan
to read rather than respond.
If people reply to this note and a short header -- Design Research
Repository -- we can follow the thread and aggregate suggestions.
The off-list part has to do with anything specific and managerial --
software, committee members, volunteers, suggested policy proposals, actual
"how-to" ideas.
Chris is going to convene a small session at the Design Research Society
conference in Sheffield for people who want to talk about this. I'll welcome
volunteers who want to help. We'll probably do some advance work so that
those who attend DRS and those who may not are able to communicate before
the meeting.
That said, if anyone on this list has ideas about what a Design Research
Reposioty ought to do and be, please put your ideas forward. This is the
time for the bold ideas and big suggestions from which me will have to make
choices for a workable project.
If you have specific "how-to" thoughts or you want to help, please
communicate off-list with
Chris Rust at <[log in to unmask]>
or with me at <[log in to unmask]>.
Yours,
Ken
Ken Friedman
Professor
Dean, Swinburne Design
Swinburne University of Technology
Melbourne, Australia
|