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

Add contact for each WAF #33

Closed
rsignell-usgs opened this issue Mar 27, 2017 · 2 comments
Closed

Add contact for each WAF #33

rsignell-usgs opened this issue Mar 27, 2017 · 2 comments
Assignees

Comments

@rsignell-usgs
Copy link
Member

rsignell-usgs commented Mar 27, 2017

Could we add (or display, if already exists) a field in the database at https://registry.ioos.us/harvests that identifies an email to contact if issues with specific harvests are discovered?

For example, the currently harvest of MARACOOS forecast data from espressso populating this WAF
http://tds.maracoos.org/iso/
has an issue, and I know how to solve it (#31 (comment)) , but don't know who to contact.

@mwengren
Copy link
Member

@ericmbernier Apologies if it's too late, which it may be, but where will the contact info for PR ioos/catalog-harvest-registry#107 show in the UI? In the harvests table?

I thought at first that non-admin users could only see their own harvests, but now I see that is not the case, they just can't edit any harvests not their own. Great!

I guess a related question is can we set up so that if a logged on user creates a new harvest, it defaults the contact info to their own user account email address, but they have the option to overwrite with any email they want? I can file a new issue for this if necessary, just let me know.

We'll also need to assign these contact values to existing harvests somehow.

@ericmbernier
Copy link
Contributor

@mwengren Yes, it will show in the harvests table.

That feature shouldn't be a problem, just submit a new issue for it, as you mentioned.

Existing harvests can either have their contact manually added via the edit harvests page, or I can run a migration, which fills them all in at once, assuming we have this information readily available.

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

4 participants