7. ADAPTING THE EVENTS STANDARD FORMATS
CONTENTS OF THIS CHAPTER
INTRODUCTION
COMPUTER IMPLEMENTATIONS OF THE FORMATS
SHORT FORMATS
NOTE ON USING SEPARATE ROLE FORMATS
DESIGNING THE FORMATS ON PAPER
7.1 INTRODUCTION
In the design of the Standard Formats, HURIDOCS has tried to be as comprehensive as
possible. This explains the multitude of formats and fields. It is quite possible, however, for
organisations to adapt the formats to their own needs, and in many cases only to use a subset
of the whole tool. Certain organisations will use only some of the formats and others will use
only a select number of fields. Likewise it is possible to add fields and assign field tags (field
numbers) for them. For example, an organisation may want to include a field for Motivation in
the Event Format. This is likely to be a field for information used in analysis, so a field tag
from the range 150 to 159, for instance 159 that is not used in the standard version of the
format, could be allocated.
With respect to the Micro-thesauri, individual organisations will sometimes find that the
standard lists do not fit the categories they would like to record, and may therefore wish to
develop their own lists. Some organisations may decide to use just a subset of the categories of
the prescribed Micro-thesauri. For instance, a national organisation would have no need for the
list of all major languages in the world - a list of national languages and dialects would be
more important.
Another major area of adaptation is the use of the formats for monitoring economic, social and
cultural rights. This subject is further discussed in Appendix B: Towards a Typology of
Violations.
If the recorded information is to be shared with other organisations it is important that any
adaptations are fully compatible with the original full formats. For instance an organisation
may decide to omit some fields, but should not change the field tags (field numbers) or field
names. Likewise it is essential for communication that only the established codes are used. If
an organisation wishes to communicate information using for instance a locally developed
Micro-thesaurus, the “code key” needs to be sent to all receiving organisations as well as to
HURIDOCS.
7.2 COMPUTER IMPLEMENTATIONS OF THE FORMATS
76
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents