User:Sabine/Affiliations

MPDL

Please note that this page is work in progress!

Introduction
The following entry is a guideline on how to encode affiliation information using the new element in TEI P5. According to the TEI Guidelines for P5 (link!) the element is defined as containing "an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor". This means that an affiliation represents a connection between one ore more parties, e.g. a person and an organization. The affiliation information is not a statical information but may change over time and one person might be connected to more than one affiliation at the same time. In the context of the TEI the element might be applied when describing characteristics of a person or an author.

How to generate a schema with Roma
A schema or a DTD for encoding affiliation information can be generated by using Roma. Roma is an application used for generating P5 compatible schemas and documentations. The online version of Roma can be found at http://tei.oucs.ox.ac.uk/Roma/.

In order to create a schema, an ODD specification has to be transformed into a DTD or a schema in the desired target language (RELAX NG or W3C Schema). For that purpose, access the Roma online version, select Open existing customization, load the corresponding ODD document and press the submit button. Now the specification can be either modified (for example by adding or removing single elements) or can be directly transformed into a schema or DTD. Select Schema in order to choose the required format and to create the schema.

Roma also provides the possibility to generate a schema or DTD directly by choosing Build schema. In a next step, select Modules in order to combine the different TEI modules at will and to add or remove single elements as required. For the encoding of affiliation information, accept the default list of modules and add the module namesdates. Finally, again select Schema, choose the format and create the schema.

The element "contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor" (Def. TEI Guidelines).

Possible core encoding:

  

... the organization name?
The name of an organization should be encoded with the element .

Max Planck Digital Library

The acronym of the organization should be encoded with the  element, adding an @type attribute with the value "acronym"

MPDL

... the postal address?
The postal address of an organization should be encoded with the element.

possible (sub)elements are:
 * street:
 * city:
 * place: 
 * postal code: 
 * postal box or post office box: 
 * country:

Example:

Invalidenstr. 35     10115 Berlin Deutschland

... the email address?
The electronic mail address should be encoded with the element.

xxx@yyy

... the homepage?
The homepage of an organization should be encoded with the element. Additionally the @type attribute should be used with the value "url".

http://www.mpdl.mpg.de

Open Issues

 * To specify the type of an organization we would like to use the element and the @role attribute. A fixed list of attribute values like laboratory, team and project has to be defined (attribute values should not be freely definable). In this context one has to make sure that the predefined value list is compatible with the affiliation attributes for eSciDoc.
 * The element is not allowed within the element. It would be good to have it allowed (a discussion concerning this has already been started with Lou).
 * The element is not allowed within the element. We discussed this already with Lou.
 * To encode the phone or fax number we would like to have a new generic element called  which can than be typed with "phone" or "fax". This has been already suggested to Lou.
 * The element is not allowed within the element nor within the element. We suggested that this should be changed already to Lou.
 * How to encode relations between different organizations? Suggestion: extend the  and the element for encoding personal relationships (see TEI Guidelines for P5, chapter 16.3.2.4) to encode also relationships of organizations.
 * How to point to an organization? Suggestion: use the element and a @xml:id attribute. Problem: element is not allowed within.
 * How to encode alternative names of an organization? Suggestion: use  elements and add a @type attributes, value "alternativeName".
 * How to encode the abbreviation of an organization? Suggestion: use the  element and add a @type attribute, value "abbreviation".
 * How to encode the period a person has been/is assigned to an affiliation? Suggestion: use the element and add the @notBefore, @notAfter, @from, @to attributes.
 * How to encode the former and later name of an organization?

Sample encodings
The sample encodings are not valid TEI encodings but should demonstrate the envisioned encoding possibilities in the domain of affiliation information.

Laurent Romary Max Planck Digital Library</orgName> Invalidenstr. 35          10115</postCode> Berlin Deutschland <addrPart type="phone">+49-(0)30-...</addrPart> <addrPart type="fax"">+49-(0)30-...</addrPart>        ...@...

<persName> Peter Meyer </persName> Max-Planck-Gesellschaft</orgName> ...       ...</postCode> ...       ...       Max-Planck-Institut für ...</orgName> ...        ...</postCode> ...        ...       Department für ...</orgName> ...       ...</postCode> ...        ...

Do not forget

 * Put a note on the CoLab page on TEI Bibliographic Information stating that the whole issue concerning affiliation is handled and documented on a special page called TEI Affiliation and link to this page.
 * Add appropriate categories (TEI, How To, Best Practice, etc.)
 * To make this page publicly accessible, please proceed as follows:
 * delete the access control
 * create a new page called TEI_Affiliation (Do not move/rename this page because history should not be visible to everybody!!!)
 * copy the content of this page to the newly created page
 * delete this page (deletion has to be done by a sysop)

Links

 * TEI Homepage