NRP-VAS UX and UI
This effort concerns the server-based NRP-VAS.
Important modules to think about
Implement different themes for interacting with the NRP-VAS, which maximize some aspects and minimize others, thus reducing noise, increasing efficiency, focusing...
One example is a project-centric theme, where the user explores different projects for different reasons, to find something to do, to find something to use (get inspired from), to find something to invest in ($, time, ...), to compare with other projects. Another example is a people-centric theme, where the user explores other users for different reasons, to find someone to do something, to see what someone is doing, to see how someone is related to someone else, etc.
Another example is an activity type/domain-centric theme, where the user explores projects in a certain domain of activity, where to apply his skills, what domains are covered by the entire ecosystem and how different domains relate to each others, how active or popular certain domains are, ... ,
Another example is a resource-centric theme, where the user is looking for find some equipment or tool, to understand the total assets accessible to the entire ecosystem, how certain resources are used and where, why some resources are not used, if there is a need for a certain resource, ...
Another theam structure takes into consideration the level of involvement of the OVN affiliate, either he/she is in the 1% (core), 9% (contributors) or the 90% (users). See this video Samer Hassan on Online Tools to Increase Participation in Collaborative Communities for more. An affiliate's view, the UI, can jump automatically from one to the other, as the affiliate migrates from user, to contributor and core, or vice versa. These 3 groups have different interests and different needs. Moreover, we want to insure mobility between these ranks, so these views need to provide every group with the ability to efficiently and effectively interact with the other groups.
See more on the Feedback system
Help features must appear in context. Help must decorate the environment.
We can also implement a help program that proactively notified the user about something the user might not know already. This can be done dynamically by monitoring the User's activity, or simply static help programs can be implemented for new affiliates, feeding them with suggestions as they use the system.
Help search feature needed as well.
Tell affiliates that something has happened. Some events are important, others are less important.
Patrolling - economic activity and resources
Networks rely on peer review to establish truth about bringing something positive to a process. In other words, OVNs need input from humans for "proof of work". Affiliates need to be able to monitor projects, processes, other affiliates, domains of activity (which can go across projects and process). Affiliates must have the choice to customize how the system notifies them about economic activities. For example, if I don't trust an affiliate, I can subscribe to all his/her activity and police him. Another example, if I am a specialist in x, I want to police everything about x.
Affiliates might create, modify and remix resources in processes, in the context of projets. Modifications of resources can have an impact on the entire OVN. That is because resources are independent building blocks on the NRP-VAS, they exist across processes and projects, and even networks. If someone modifies the description, the picture, or anything else about a resources, others must know about it. Knowing that a resource has been modified is important for many reasons
- see if someone has improved it;
- see if someone has changed the description or the NRP-VAS representation in a way that it affects finding the resource in the system later, or understanding what the resource is;
- add other reasons;
Affiliates create processes and types of work or tasks. The system notifies other affiliates who might have the potential to execute them. The system can learn from activity who is doing what and send a notification to those who have already logged something in relation to the new task, or type of work. But affiliates might want to subscribe to notifications for other types of tasks.
The NRP-VAS doesn't have search functionality. It would be nice to be able to search projects, resources, agents, ...
Time is a very important parameter for economic activities.
- Coordination - some activities have time dependencies and must be completed in order, at a given time with respect with others.
- Evaluation - Some temporal characteristics of economic activities are important to evaluate projects. For example, a project is said to be "dormant" is the rate of contributions is low, or nul. A project is unstable is economic activity is sporadic. Usually, projects that operate below critical mass (not enough affiliates) and/or with insufficient incentives have exhibit fluctuations in their activities. A project is alive or stable if the frequency of contributions is high and if contributions happen with a certain periodicity. Projects can also be in expanding mode or in decay. A decrease in periodicity and/or frequency of contributions can be a symptom to a problem.
- Governance - Access to decision making is related to the type of affiliation. Most projects in SENSORICA use different types of affiliation that can be algorithmically (automatically) set by a governance equation. For example, if an affiliate hasn't contributed to a project for a certain duration he/she becomes an inactive affiliate and might be denied access to some decision making processes.
- add more...
See also Timeline