Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

1_CampaignSummary: Contact #14

Closed
emilyarobles opened this issue Sep 27, 2023 · 1 comment
Closed

1_CampaignSummary: Contact #14

emilyarobles opened this issue Sep 27, 2023 · 1 comment

Comments

@emilyarobles
Copy link
Contributor

@regnans
Could you clarify which individual should be listed as the contact? Is this the person who is filling out the dataset and submitting it, or the PI of the project, etc?

The location reporting format also has a contact field (Submission_Contact_Name) and who exactly should be listed has caused some confusion in the past. Also, the location RF separates the contact name from the contact email. I would suggest something similar in this case, since First and Last name, Organization, Email, and ORCID could make this field quite lengthy. Additionally, it is unclear whether all of this information is required? Or just name and email? You could have a Name; Email field and an optional/recommended Organization; ORCID?

@regnans
Copy link
Collaborator

regnans commented Sep 27, 2023

The Contact field here is the same as the ESS-DIVE package metadata. It is included in Campaign Summary to make the reporting format usable outside of ESS-DIVE, but within ESS-DIVE I expect that the Contact information will be taken from the Package Metadata, not the UAS metadata.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants