Contributors

[philipbaileynar]

Concept

So far we have taken a fairly light touch regarding contributors. We have used "Designers" and "Observers" textboxes on the DCE forms. We would like to elevate the sophistication a bit. This should allow us to reuse this information in reports etc.

My vision is that there is a central list of contributors in a QRiS project (visible on project properties) that can be associated with one or more DCEs.

Task

Create a reusable widget that lists contributors, with "Add New", "Add Existing" and "Remove" buttons. Then use this in the following places:

• Project Properties
• DCEs (where the tab is called "Contributors")
• Design DCEs (where the tab is called "Designers")
• As-Built DCEs (where the tab is called "Observers")

Here's a design for the properties form:

Let's try and keep this simple and generic so that it has widespread applicability...

• Name is the only required field.
• "URL" is deliberately generic and not "Riverscapes Community Profile URL".
• Data Exchange GUID could be super helpful later if people go to the trouble to use it.
• "Roles" - Reuse the list of roles from PBR Explorer. Let's be careful here! Collapse these as a list of strings in the database (not a separate table with intersect). Ideally we would source this list of roles from a simple JSON file maybe in Riverscapes.xml or next to the project etc But this is getting a bit scope creepy. Just make damn sure that the list of checkboxes can tolerate whatever is in the project (i.e. if we remove "Funder", but it still occurs in a project then it should still appear in the list. i.e. the list is a superset).

Database

FYI @Jdgilby @joewheaton

[philipbaileynar]

Some clarifications after talking with @joewheaton

Screenshot below of the "Contributor list" widget for use on the project and DCE properties. The "Search" button authenticates on the data exchange and then pops up search box for finding Data Exchange users. If the user picks a user then the contributor properties form is pre-populated with these details when it returns.

This is similar to adding users to an organization in the Data Exchange: