You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
@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.
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.
The text was updated successfully, but these errors were encountered: