1.0 Title
2.0 Purpose: To collect the results from a specific inquiry about a subject in an ad hoc format.
3.0 Usage: This format (or lack thereof) is used if no other more useful formats (such as Topic Maps or Semantic web) are being applied.
note: some of the more reliable bits can be transferred to SIG Topics but only if the SIG memebers approve of the contenst. For non-SIG members this provides a way to collect the good, the bad and the ugly and not have to worry as much about dis-information or error - or even spam.
4.0 Frequency
5.0 References
6.0 Responsibility: There are several "actors" in this use case including;
Task Leader: the person who posed the question and needs and uses the answers.
Archive Owner: the peron who is responsible for keeping the site active once its immediate use is past, most often the Task Leader - but not always.
Contributor: any person who has assisted or provided information to the search
Reader: Any perosn who has read only access to te archive.
7.0 Ownership:
The Task Leader who posed the original question and the Archive Owner who is responsible for keeping the site alive are the "woners" of the information unless expressly transferred to others.
8.0 Effort
9.0 Risks
> 80%Wasted effort:
One can spend a lot of time copying and pasting information that nobody ever uses or can use again becasue it si inaccesible or a complete mess.
>50% Mis-information:
Since most people don't have the expertise or time to challenge or even read all of the links and results from a query a lot of the information may be just plain wrong. Even more will be out of date.
>50% Confusing and unhelpful
10.0 Contents
10.1 The Question:
A re-statement of the original question and its context should be posted in the archive.
10.2 The Work Order
At least - a unique reference tag for the archive so that it can be identified form dozens of other queries.
also a good idea - a time budget/limit for the partcipants - especially if you've promised to pay.
For formal queries a pm4 Task Decsription/Work Order should be created.
10.3 The Participants
For general queries to large group of people, only those hwo responded or showed interest need be included in the acess to the archive. Others may be added later if the task leader deems fit.
10.4 The list of contents
Yes - it would be nice to have a list of contents - make sure you do that.
10.5 the dump.
The contents of a general topical inquiry vary greatly but often include:
- email threads
- search engine queries and results
- article links and reprints (beware of copyright violations)
- vendors of interest
- equipment data sheets or drawings of interest
- and more..... (like - how much more??)
10.6 the Index
- yeah sure - whatever.....
10.7 Topic Map
- hah! if you wanted a Topic Map you should have used km201
11.0 MetaData
12.0 File Handling Policy