Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Guidance on agency dataset contact information #130

Open
adborden opened this issue Feb 4, 2020 · 3 comments
Open

Guidance on agency dataset contact information #130

adborden opened this issue Feb 4, 2020 · 3 comments

Comments

@adborden
Copy link
Contributor

adborden commented Feb 4, 2020

This question came up during today's Open Data meeting:

Are there any privacy concerns with publishing an individual agency employee's contact information?

@adborden
Copy link
Contributor Author

adborden commented Feb 4, 2020

Based on @hkdctol and @rebeccawilliams 's response, the guidance might include:

  • Citation in the law to requiring contact information.
  • Some explanation of why there should be no privacy concerns with publishing an individual agency employee's contact information.
  • Customers (data users) like working with real people so an individual's contact information is preferred. We recommend you use an individual's contact information and keep that information up to date, since this role can change.
  • A listserv or group email may be appropriate if multiple employees share the responsibility of dataset ownership.

adborden pushed a commit that referenced this issue May 29, 2020
…arging-data-validation-service

Automatically generated. Merged on Netlify CMS.
@adborden
Copy link
Contributor Author

adborden commented Oct 6, 2020

Conversation from the monthly r.d.g meeting:

Schema refers to a vcard, which implies first/last name, so what should you do with group email addresses?

If you identify an individual instead of a group, it's clear who is responsible. If it's a group list, it's less clear who's responsibility it is to respond at the agency.

@hkdctol
Copy link
Contributor

hkdctol commented Nov 24, 2020

Not sure there is a current issue for resources.data.gov, but I would keep this and move to whatever we decide to use for tracking issues when we do a metadata schema update.

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

No branches or pull requests

2 participants