Issue 11067
Admin console - Is email a mandatory field when filling up a contact of ANY type?
11067
Reporter: jcuadra
Type: Task
Summary: Admin console - Is email a mandatory field when filling up a contact of ANY type?
Priority: Major
Resolution: Invalid
Status: Closed
Created: 2012-05-11 15:45:12.865
Updated: 2013-08-29 15:29:20.231
Resolved: 2013-08-29 15:29:20.115
Description: When creating a new contact through the admin console, an email is mandatory for a TECHNICAL or ADMINISTRATIVE contact. But will it be mandatory to all other contact types?
See all possible contact types for
http://code.google.com/p/gbif-registry/source/browse/trunk/registry-api/src/main/java/org/gbif/registry/api/model/vocabulary/ContactType.java#28
a more human-readable version is here:
http://staging.gbif.org:8080/enum-web/enum?id=org.gbif.registry.api.model.vocabulary.ContactType]]>
Author: ahahn@gbif.org
Created: 2012-05-11 15:59:48.933
Updated: 2012-05-11 15:59:48.933
Admin and technical contacts are used for automated communication (feedback, info on new datasets under publisher, etc), so a) their existence and b) an email are essential. For contacts that are used for display only, we should leave it to them to decide which information they consider relevant.
A point to clarify: to which degee do we synonymyse contact types? Eg., is a "DATA_ADMINISTRATOR" handled as the ADMINISTRATIVE_POINT_OF_CONTACT if that one is not given? Or does the creation of at least one ADMINISTRATIVE_POINT_OF_CONTACT and one TECHNICAL_POINT_OF_CONTACT enforced? Can either of the entries be flagged as "primary", as is the current terminology and praxis in registration?