"roles"
in their email
domain, and the role name in front of email. Example is gbif-dadi@roles.circa.gbif.net
. More details on roles is given below .
"ig"
in their email domain
and in the front the <optional access class>.<ig>.<instance>
names. Example is leader.dadi.gbif@ig.circa.gbif.net
.
"ig"
domain.gbif.net
, whereas services of and for the GBIF Secretariat are available from
gbif.org
. http://circa.gbif.net/gbif/
.
For every interest group there is a corresponding email address that should
be used for communication to the committee mentioned and other people that
have been included as interest group members.
Name
|
Description
with link to mailing list archive |
Availability
|
Email address
|
GB |
Governing Board
|
Members only |
gb.gbif@ig.circa.gbif.net |
EC |
Executive Committee
|
Members only |
ec.gbif@ig.circa.gbif.net |
BC |
Budget Committee
|
Members only |
bc.gbif@ig.circa.gbif.net |
SC |
Science Committee
|
Members only |
sc.gbif@ig.circa.gbif.net |
Archive |
Archive
area of the Secretariat |
Members only |
archive.archive.gbif@ig.circa.gbif.net
|
NODES |
Participant
Node Managers Committee |
Public after registration |
nodes.gbif@ig.circa.gbif.net
|
DADI |
Data standards
and data interoperability |
Public |
dadi.gbif@ig.circa.gbif.net |
DIGIT |
Digitalisation
of biodiversity data |
Public |
digit.gbif@ig.circa.gbif.net
|
ECAT |
Electronic
catalogue of names of known organisms |
Public |
ecat.gbif@ig.circa.gbif.net |
OCB |
Outreach and
capacity building |
Public |
ocb.gbif@ig.circa.gbif.net |
ICT |
IT helpdesk
and documentation |
Public |
bug.ict.gbif@ig.circa.gbif.net
,helpdesk.ict.gbif@ig.circa.gbif.net |
"ig"
domain is recommended."roles"
address. See information about roles below. However, in order
to archive automatically these messages, a special access class with the name
"representative" has been set up for the above interest groups. Hence,
official announcements are sent, for instance, to representative.nodes.gbif@ig.circa.gbif.net
.
Name
|
Description
|
Email address
|
GBIF Secretariat |
Director and the Lead Secretary (for action)
|
gbif@gbif.org
|
GBIF |
All GBIF Secretariat staff (for info)
|
staff@gbif.org
|
GBIF Webmaster |
Webmaster (for action), Network and Database Administrator
(for info), Secretary of IT Department (for info), Liaison Officer for
Public Relations (for info), Deputy Director for Informatics (for info) |
webmaster@gbif.org |
GBIF Hostmaster |
Network and Database Administrator (for action),
Webmaster (for info), Programme Officer for Database Access and Data Interoperability
(for info), Deputy Director for Informatics (for info) |
hostmaster@gbif.org |
Helpdesk |
Assistance in the use of GBIF information and communication
technologies |
helpdesk@gbif.org
|
Network-Function-Topic-Country-RankRoles do not have to be complete to the 5th level. They can be queried using wildcards. Examples:
Emails are spawned to lower levels of the tree hierarchy. So, sending togbif-gb
(GBIF Network - Governing Board)
gbif-gb-vp-fi-1
(GBIF Network - Governing Board - Voting Participant - Finland - Head of
Delegation)
gbif-dadi
(GBIF Network - DADI Subcommittee)
gbif-*-*-fi
(All Finnish occupants of GBIF roles)
gbif-gb-vp-fi
sends to all Finnish members in various rank
positions and to gbif-gb
sends to all categories of members
and countries in the underlying tree. Indeed, gbif@roles.circa.gbif.net
reaches all people that have some role in the GBIF network. In
the current CIRCA release 3.1 wildcards can not be used in email addresses,
but that will be enabled in a future release. helpdesk@gbif.org
.