Participating-org prototype development

[anjesh]

The module should follow the flow given below - the grayed-block is the organisation-module which is handled in different issue #5

---

This slide is for historical purpose, and there are changes in the initial concept, which are documented/presented in mockups below.

[anjesh]

PO (participating-org) interface will be changed in AidStream.

When you are adding a new PO, then you will get a list of organisation names that you have maintained in your org-data module (ie. your partners list).

You may select your partner from your existing partner list. You may also suggest changes to some of those information. If your partner organisation is already a valid IATI Publisher, your suggestion will go through the approval process before it gets updated in API - that's why you will "Suggest edit".

Once you select your partner organisation, organisation-type and identifier are auto-selected. You won't be able to make edits to these information, you may only suggest changes. If it's valid IATI publisher, you will get option for "activity-identifier" to link with your partner's published activity.

However if your organisation you are looking for isn't present in the API list, then you may either "Contact the organisation" for their identifier or "Use Organisation Finder" process using org-id.guide.

Once you select type and country, you will get list of registration agencies for that particular country.

You will have to manually find for that organisation in the portal listed in org-id.guide and enter the organisation-identifier in the interface.

[timgdavies]

This is looking good.

For the org-id.guide workflow, I would suggest using the language of "Find an identifier source from org-id.guide" rather than "Add from org-id.guide"

I'd be happy to review other copy when in final version to make sure we communicate clearly that org-id.guide is helping people discover lists, where they can then discover organisation identifiers.

[reidmporter]

Possible to make explicit location of the list (if available) at source part of a) the research process for new lists added to Org-ID.guide, b) a flag (available/unavailable) to essentially act as a "dead end" or "not a dead end" sign, c) pull that list into the AidStream UI so that (for the lists that aren't dead ends) the user never has to leave the comfort of AidStream to add an identifier? (I'm guessing C is a hard no, and A and B are really more relevant to Org-ID @timgdavies.