Fields and widgets common to most forms

There are different input forms for each record type in a MICHAEL production module. Each form has its own set of fields filled in using specific widgets, but some fields and widgets are the same for all or most of the forms. We introduce these fields and widgets in this document.

1) Identifier

Whether the identifier is automatically assigned or is typed by the editor depends on your local configuration. In the case you need to provide an identifier (or part of it), it is very important to use a unique identifier in the database , among all records of any kind.

2) Links

Links are used to create relationships between records and to the external world. The form used to create a link looks like:

A link is expressed with three pieces of information.

Target

The target is either a URL when you create a link towards an external resource, or the identifier of record within the same MICHAEL database. See below for help on selecting an identifier. In most of the cases, this field is mandatory, although the form don't enforce it. See below for exceptions.

Role

The role is the type of relation or link you create. This is a very important field and it should always be used for usual links. See below for exceptions. The role is either selected in the drop-down list, or if you select the Other value you can add a new role in the text zone below.

Description

This optional field lets you add information about the link. This is useful if, for instance, the role does not explain completely or exactly why you create such a link.

When you create a link towards another record in the same database, you need to specify the identifier of the target record in the target field. To do so, it is easier to use the ... button on the right of the text zone. This will open a small window like this one:

This window contains a simplified browser of a database. You can browse through the folders, and whenever you select a document its identifier will be inserted in the target text zone.

3) System metadata

System metadata are part of all the input forms – always the last screen. They contain information that you cannot edit, such as the creation and modification date, and the username of the agent having made the last modification.

You can edit other fields that are explained here.

Review date of the record

The review date is an indication to help editors maintaining the data. It can serve as a reminder to know when to verify the accuracy of the information held in the record. Using this field is optional, but when you use it you should always specify a date in the future.

Record editorial status

The editorial status is either Draft or V alid . Only valid records can be published. Please also note that only users member of the validators record can change this field; for others it is always set to Draft .

Language of the record

This is the cataloguing language , not the language of the object described by the record. It defaults to the current user interface language, but it can be changed.

Comments on the record

These are internal comments, for editors, not for the public.