Relationships between input/ output centres
A Meeting-related Information Exchange Facility (Part #8)
[Parts: First | Prev | Next | Last | All] [Links: To-K | From-K | From-Kx | Refs ]
Some users (identified as Level 2 and 3 above) have, and will have, the collection and dissemination of particular kinds of information as a programme objective. In other words such users do not just make use of the system to inform or be informed. They allocate resources to improving the pool of information and ensuring that it is made as widely available as the economic constraints permit. A good example is provided by those concerned with information on future conferences.
At the present time such bodies independently collect, process, index and print overlapping portions of the same pool of information. This is then distributed, freely or at a price, to a constituency within which these bodies compete, to some extent, for greater distribution of their respective products. Some of these bodies consider that their programme should generate revenue, whether or not the bodies themselves are non-profit-making. In the proposed environment, the relationship between these bodies becomes much more intimate. Instead of obtaining and checking each others printed products at regular intervals, in order to update their own files, each would contribute to a common pool (It is of course possible to envisage a situation in which each maintained separate files and users would choose between them.). Clearly this process would have to be established most carefully to avoid the possibility of one or more such bodies obtaining any unfair advantage.
Fortunately in a computer environment a multitude of bookkeeping operations can be automated. One possibility is therefore that each date element in an information file, on meetings for example, would bear a code identifying the body which had inserted it. Now a principal characteristic of such information is the changes made to it as the date/location of the meeting is finally fixed. For example, different portions of the meeting entry might end up being contributed by 3 bodies
- 1 Date Body A
- 2 Place Body B
- 3 Organization Body E
- 4 Theme Body A
- 5 Organizer Body C
So at this stage, if any of four bodias were to usethat information to produce independent meeting directories, then some corresponding accounting units mould have to transferred in a suitable bookkeeping system for the following :
| Payments | ||||||
| . | Royalty payment by : . | |||||
| . | . | A . | B . | C . | D . | E . |
| Royalty payment to . | A . | D . | 1,4 . | 1,4 . | 1,4 . | - . |
| to: B . | 2 . | 0 . | 2 . | 2 . | - . | |
| C . | 5 . | 5 . | 0 . | 5 . | - . | |
| 0 . | - . | - . | - . | D . | - . | |
| E . | 3 . | 3 . | 3 . | 3 . | 0 . | |
In the above example, Body D contributed nothing to establishing the entry so that its account would be debited in favour of all the others. On the other hand, Body E makes' no use of that entry for its own purposes. In fact Body E might have been a primary user (Level 1).
Clearly there are many possibilities for handling this kind of system to compensate each according to his contribution if in fact such compensation is required. Many primary users might be quite satisfied to be credited in a manner which reduces royalty payments which they have to make for extracting information. The relationship between users at Level 2 or 3 is more delicate.
The question would quickly arise as to how to prevent the appearance of abuse under such situations as :
- replacement of a valid date by the same date or a less valid date in order to obtain "copyright" advantage
- sincere replacement of the valid place by an invalid place as a result of erroneous information from a misinformed source (possibly even with responsibility for the meeting)
- altering valid text information to bring it into some standard and presentable format without contributing any new information (Namely editorial and translation work ; this could also apply to any indexing)
- taking advantage of work rythms, postal delays, etc. to insert or change information when another body could only do it a day later.
Each would at some time have the advantage in the last case. The first can bo reduced by maintaining a record, periodically listed, of who "bumped" whose data clement by what, possibly with an agreed (if not automatic, in the case of a date, for example) penalty in units of account. The second is more difficult since it is a question of interpretation. Possibly a source code could be used as a guide (e.g. 1 newspaper, 5 = own periodical, 9 = personal letter). In the case of conflicting items with the same authority code, both could be kept. The third could be treated as on independent operation (and subcontracted) so that such changes did not alter the royalty question.
An even more delicate question would be whether a new well-funded body could regularly (or once only) "drain off" major portions of the file for reproduction for its own market. Possibly the royalty payment system could be weighted in terms of the number of elements taken in any one period by such "wild-cat" users. On the other hand care must be taken not to build up an information cartel.
[Parts: First | Prev | Next | Last | All] [Links: To-K | From-K | From-Kx | Refs ]
Subjects: Friendship · Production