-
Notifications
You must be signed in to change notification settings - Fork 0
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
Clearer labelling and/or auto-population of reporting-org/@narrative #1406
Comments
Approach
Issue/ concern/ question
|
@praweshsth - the approach above sounds good for new sign ups; that's what I was focusing on. I don't think we need to retrospectively apply it to existing organisations' data. In Support, we've already contacted a few publishers to ask them to correct their |
Added estimation. |
This has been deployed to staging. |
Looks great! |
We're seeing many users mistakenly complete the
reporting-org/@narrative
field in Organisation Data with an organisation description, when it should be their organisation name. The long text strings that they're entering are causing problems for other IATI tools, so we want to make it clearer to users what this field is and, ideally, populate it for them.In cases where the organisation has signed up as a primary reporter (almost all cases),
reporting-org/@narrative
should equaliati-organisation/name
For example, in my test account below, I've registered with publisher name "Emma's test publisher v.2" and as a primary reporter (
reporting-org/@secondary-reporter
= false)My
iati-organisation/name
has been auto-populated, whereas thereporting-org/@narrative
is left blank.To make things clearer to users:
reporting-org/@secondary-reporter
= false). If missing default language is the problem, we can consider collecting this at point of registration.The text was updated successfully, but these errors were encountered: