Versions Compared

Version Old Version 78 New Version 79
Changes made by

Kho SA

Kho SA

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

  • If first name/ last name is filled and structure name is blank → Individual will be created. (1)

  • If structure name is filled and first name + last name is blank → Structure will be created. (2)

  • If structure name and first name/ last name are filled → Structure + will be created and then Relay will be created. (3)

    • Preferred language applies to both structure and relay.

    • Address applies to both structure and relay.

    • Communication mean (Phone/ Email...) information on contact applies to both relay and structure.

    • Authorization only applies to relay.

    • Contact criterion: Depends on contact type. If contact type is Structure, then applies to Structure only. If contact type is Both/ Individual, then applies to Relay only. 
      Comparing 2 records which have the official name filled (can be (2) or (3)), based on structure information (official_name, address_name1, address_name2) + Address information (line1, line2, line3, zipcode, town, town_complement, country) → Decide if the same structure or different structures.
      If relay has different address with structure, create a new data file with the operation "UPDATE" in order to update the address for relay.
      Same ru

...

Field code

Field type

Mandatory

Description

OFFICIAL_NAME

Text 100


Official name of the structure. The name will be truncated if it is too long.

ADDRESS_NAME1

Text 38


Name of the structure for the adresse

If it is empty, it is taken from the official name

 If it is too long, it is truncated.

ADDRESS_NAME2

Text 38


STRUCT_TYPE

Code


The type of the structure. The code must be defined as described in Define type of structure

COMMUNITY_TYPE

Code


The code of the community type. If it is left empty, then the structure isn't member of any community.

ADMIN_NUMBER

CodeValue


Administrative number, for example a SIRET number. Only one number can be given here, but subsequent updates of the contact may help adding several numbers.

  • On the CONFIG row, the user can define the default code.

Example

Field value

Comment

SIRET=404 833 048 00022

The SIRET number is 404 833 048 00022

404 833 048 00022

SIRET must have been defined in a CONFIG row


NB_EMPLOYEES

Number



WEB_SITE

Text 255


URL to the structure's websit

...

Field code

Field type

Mandatory

Description

TELEPHONE

Text 15


Landline phone number.

Following formats will be recognized. These examples assume country FR (country of the address, or by default the country of the institution).

The initial << + >> sign will be recognized as well as 00.

The country prefix can be forced if it entered in parenthesis at the beginning.

All other non digit signs are ignored.

The national prefix (0 for CH, FR, 1 for US, 9 for ES, etc. see COUNTRY table) will be automatically removed in the database if present in the input number.

Examples

Input country

Input number

Stored as

Remark

FR

01 40 15 80 00

33 / 140158000

The leading 0 (national prefix) has been removed for France

FR

1 40 15 80 00

33 / 140158000


FR

0041 21 613 21 11

33 / 041216132111

Country prefix (41 but lookin
One leading 0 (national prefix) has been removed for France

CH

0041 21 613 21 11

+41 21 613 21 11

41 / 216132111

Country prefix could be recognized

FR

(41)216132111
(41)0216132111

41 / 216132111

This format allows to force the country code.
This is the preferred format for import, as it lets you choose the country prefix independently from the country of residence.

FR

01 SVP 77 77

017777


IT

(39)0444 651070

39 / 0444 651070

Keep the “0” in telephone numbers for Italy.


FAX

Text 15


Fax number. Same rules as for PHONE.

CELLPHONE

Text 15


Mobile phone. Same rules as for PHONE.

EMAIL1

Text 250


Will be used as username for ticket shop login.

If email does already exist in the database, the email is imported for the contact but can't be used to login.

There no possibility to import a list of passwords. Each new contact will need to request a password change (click on Have you forgotten your password ?)

The email validated by regular expression: ^[0-9a-z+\$_-]+(\.[0-9a-z+\$_-]+)*@[0-9a-z+_-]+(\.[0-9a-z+_-]+)+$

EMAIL2

Text 250


Alternative email address. Cannot be used for login.

EMAIL3

Text 250


Alternative email address. Cannot be used for login.

...

Field code

Field type

Mandatory

Description

CRIT01

CodeValue


The code must be created as described in Define criteria's for the contacts.

  • Several values can be given. They need to be separated by pipes.

  • On the CONFIG row, the user can define the default code.

Examples:

Field value

Comment

PREFCOL=Red

The preferred color is Red only

PREFCOL=Red|Green

The preferred color is Red and Green

Red|Green

PREFCOL must have been defined in a CONFIG row

PREFCOL=Red

PREFCOL=Green

This is equivalent to PREFCOL=Red|Green, but using two CRIT columns.


...



CRIT50

CodeValue



File format for contacts

...

Field code

Field type

Mandatory

Description

OFFICIAL_NAME

Text 100


Official name of the structure. The name will be truncated if it is too long.

ADDRESS_NAME1

Text 38


Name of the structure for the adresse

If it is empty, it is taken from the official name

 If it is too long, it is truncated.

ADDRESS_NAME2

Text 38


STRUCT_TYPE

Code


The type of the structure. The code must be defined as described in Define type of structure

COMMUNITY_TYPE

Code


The code of the community type. If it is left empty, then the structure isn't member of any community.

ADMIN_NUMBER

CodeValue


Administrative number, for example a SIRET number. Only one number can be given here, but subsequent updates of the contact may help adding several numbers.

  • On the CONFIG row, the user can define the default code.

Example

Field value

Comment

SIRET=404 833 048 00022

The SIRET number is 404 833 048 00022

404 833 048 00022

SIRET must have been defined in a CONFIG row


NB_EMPLOYEES

Number



WEB_SITE

Text 255


URL to the structure's website. It must contain the http:// prefix.

...

Field code

Field type

Mandatory

Description

TELEPHONE

Text 15


Landline phone number.

Following formats will be recognized. These examples assume country FR (country of the address, or by default the country of the institution).

The initial << + >> sign will be recognized as well as 00.

The country prefix can be forced if it entered in parenthesis at the beginning.

All other non digit signs are ignored.

The national prefix (0 for CH, FR, 1 for US, 9 for ES, etc. see COUNTRY table) will be automatically removed in the database if present in the input number.

Examples

Input country

Input number

Stored as

Remark

FR

01 40 15 80 00

33 / 140158000

The leading 0 (national prefix) has been removed for France

FR

1 40 15 80 00

33 / 140158000


FR

0041 2

33 / 041216132111

Country prefix (41 but looking for 33) could not be recognized
One leading 0 (national prefix) has been removed for France

CH

0041 21 613 21 11

+41 21 613 21 11

41 / 216132111

Country prefix could be recognized

FR

(41)216132111
(41)0216132111

41 / 216132111

This format allows to force the country code.
This is the preferred format for import, as it lets you choose the country prefix independently from the country of residence.

FR

01 SVP 77 77

017777







FAX

Text 15


Fax number. Same rules as for PHONE.

CELLPHONE

Text 15


Mobile phone. Same rules as for PHONE.

EMAIL1

Text 250


Will be used as username for ticket shop login.

If email does already exist in the database, the email i

There no possibility to import a list of passwords. Each new contact will need to request a password change (click on Have you forgotten your password ?)

The email validated by regular expression: ^[0-9a-z+\$_-]+(\.[0-9a-z+\$_-]+)*@[0-9a-z+_-]+(\.[0-9a-z+_-]+)+$

EMAIL2

Text 250


Alternative email address. Cannot be used for login.

EMAIL3

Text 250


Alternative email address. Cannot be used for login.

...

Field code

Field type

Mandatory

Description

CRIT01

CodeValue


The code must be created as described in Define criteria's for the contacts.

  • Several values can be given. They need to be separated by pipes.

  • On the CONFIG row, the user can define the default code.

Examples:

Field value

Comment

PREFCOL=Red

The preferred color is Red only

PREFCOL=Red|Green

The preferred color is Red and Green

Red|Green

PREFCOL must have been defined in a CONFIG row

PREFCOL=Red

PREFCOL=Green

This is equivalent to PREFCOL=Red|Green, but using two CRIT columns.


...



CRIT50

CodeValue