Dataset page: displaying contacts

10732
Reporter: kbraak
Assignee: mdoering
Type: Task
Summary: Dataset page: displaying contacts
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-02-01 17:15:04.257
Updated: 2013-08-29 14:45:08.972
Resolved: 2012-10-26 17:22:52.252
        
Description: Contacts have two sources:

Registry
-primary contacts
-other contacts

EML
-contact, creator, metadata provider (=primary contacts)
-associated personnel, project personnel (=other contacts)

The contacts are combined from their two sources and then displayed like so:

-The primary contacts are displayed in summary block
-The other contacts are displayed in project block (with only the specific project personnel being added in the main project block).

I need to ensure that the EML contacts do not override the contacts coming from the Registry, or that there is duplication.

I will attach some screenshots as soon as I can to this issue, and then hopefully we can decide if the layout requires any change or not.
]]>
    

Author: kbraak@gbif.org
Created: 2012-10-26 17:22:52.285
Updated: 2012-10-26 17:22:52.285
        
It's not the Portal's job to avoid duplicating contacts, just to display them.

The Registry will be the authoritative source for contacts.

Currently, the registry-metadata-service augments a dataset with metadata coming from an eml.xml file, but there is nothing downloading these files yet-see http://dev.gbif.org/issues/browse/CRAWLER-19

The registry metadata synchronizer and registry-metadata-service will have to be coordinated. For example, the synchronizer populates the registry with any metadata from the DwC-A, but will never do external datasets. And, the registry-metadata-service will only augment external datasets.

Marking as won't fix.