NRP-CAS UX and UI - Revision history

TiberiusB at 18:25, 25 September 2026

2026-09-25T18:25:44Z

TiberiusB: /* Patrolling - economic activity and resources */

2026-04-07T18:53:09Z

Patrolling - economic activity and resources

TiberiusB: /* Time */

2025-07-11T17:44:20Z

Time

TiberiusB: /* Navigation and orientation */

2025-07-11T17:26:00Z

Navigation and orientation

TiberiusB: /* Signaling */

2025-07-11T17:10:41Z

Signaling

Sensorica-wiki at 03:44, 20 October 2021

2021-10-20T03:44:53Z

imported>TiberiusB: TiberiusB moved page NRP-VAS UX and UI to NRP-CAS UX and UI: Language has changed

2020-07-30T03:01:58Z

TiberiusB moved page NRP-VAS UX and UI to NRP-CAS UX and UI: Language has changed

New page

This effort concerns the server-based [[NRP-CAS]].

=Important modules to think about=

==Navigation and orientation==
Implement different themes (or viewpoints) for interacting with the [[NRP-CAS]], which maximize some aspects and minimize others, thus reducing noise, increasing efficiency, focusing...

Examples of themes
* project-centric theme, where the [[agent]] explores different [[projects]] for various 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.
* resource-centric theme, where the [[agent]] explores different [[resources]] for various reasons, to find something to use, to find something to offer, to find something to invest in ($, time, ...), to compare with other resources, etc. This is the Inventory view in the current [http://nrp.sensorica.co/accounting/inventory/ Sensorica's NRP-CAS].
* agent-centric theme, where the agent explores other agents for various reasons, to find someone to do something, to see what someone is doing, to see how someone is related to someone else, etc.
* activity type/domain-centric theme, where the agent 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, ... ,
* community-centric view, where the agent explores an entire community, compares it with other communities, sees what projects are embedded in this community context, etc.

Yes another theame structure can take into consideration the level of involvement of an agent, either he/she is in the 1% (core), 9% (contributors) or the 90% (users). See this video [https://www.youtube.com/watch?v=xlXeMScO3F4 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 [[agent]] 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.

==Feedback==
See more on the [[Feedback system]]

==Help==
Best practice for help is to appear in context, to "decorate the environment".

We can also implement a help program that proactively notifies the [[agent]] about something the she/he might not know already - AI support for example. 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.

==Signaling==
Tell [[affiliates]] that something has happened. Some [[events]] are important, others are less important.
This would be pat of a notification system, customizable by [[agents]].

===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]] and other [[affiliates]], validate [[events]], monitor 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 monitor his/her activites. 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 [[projects]]. Modifications of resources can have an impact on the entire OVN. That is because [[resources]] are independent building blocks on the [[NRP-CAS]], they exist across [[processes]] and [[projects]], and even networks. If someone modifies the description, the picture, or anything else about a [[resource]], 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-CAS]] representation in a way that it affects finding the resource in the system later, or understanding what the [[resource]] is;
# add other reasons;

===Getting opportunities===
[[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.

==Search==
The [[NRP-CAS]] doesn't have search functionality. It would be nice to be able to search [[projects]], [[resources]], [[agents]], ...

==Time==
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 if 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]]

=Other UX-UI ideas=

* [https://gitter.im/mfrangos/SensoricaOVN?utm_source=share-link&utm_medium=link&utm_campaign=share-link See discussion on Gitter]
* [https://github.com/valnet/valuenetwork/issues See also issues tagged UX/UI on Github]
* [https://github.com/valnet/valuenetwork/issues/452 github issue by Tibi]

[[category: Infrastructure]]

@@ Line 7: / Line 7: @@
 Examples of themes
-* venture-centric theme, where the [[agent]] explores different [[ventures]] for various 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 [[ventures]].
+* venture-centric theme, where the [[agent]] explores different [[ventures]] for various reasons, to find something to do, to find something to use (get inspired from), to find something to contribute to ($, time, ...), to compare with other [[ventures]].
-* resource-centric theme, where the [[agent]] explores different [[resources]] for various reasons, to find something to use, to find something to offer, to find something to invest in ($, time, ...), to compare with other resources, etc. This is the Inventory view in the current [http://nrp.sensorica.co/accounting/inventory/ Sensorica's NRP-CAS].
+* resource-centric theme, where the [[agent]] explores different [[resources]] for various reasons, to find something to use, to find something to offer, to find something to contribute to ($, time, ...), to compare with other resources, etc. This is the Inventory view in the current [http://nrp.sensorica.co/accounting/inventory/ Sensorica's NRP-CAS].
 * agent-centric theme, where the agent explores other agents for various reasons, to find someone to do something, to see what someone is doing, to see how someone is related to someone else, etc.
 * activity type/domain-centric theme, where the agent explores [[ventures]] 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, ... ,

@@ Line 33: / Line 33: @@
 ===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 [[ventures]], [[processes]] and other [[affiliates]], validate [[events]], monitor domains of activity (which can go across [[ventures]] and [[process]]).
+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 [[ventures]], [[processes]] and other [[affiliates]], validate [[events]], monitor domains of activity (which can go across [[ventures]] 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 monitor his/her activities. Another example, if I am a specialist in x, I want to police everything about x.

@@ Line 51: / Line 51: @@
 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.
+* ''Coordination'' - some activities have time dependencies and must be completed in order, at a given time with respect to others.
-* ''Evaluation'' - Some temporal characteristics of economic activities are important to evaluate [[ventures]]. For example, a [[venture]] is said to be "dormant" is the rate of contributions is low, or nul. A [[venture]] is unstable if economic activity is sporadic. Usually, [[ventures]] that operate below critical mass (not enough affiliates) and/or with insufficient incentives have exhibit fluctuations in their activities. A [[venture]] is alive or stable if the frequency of contributions is high and if [[contributions]] happen with a certain periodicity. [[Ventures]] 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.
+* ''Evaluation'' - Some temporal characteristics of economic activities are important to evaluate [[ventures]]. For example, a [[venture]] is said to be "dormant" if the rate of contributions is low, or null. A [[venture]] is unstable if economic activity is sporadic. Usually, [[ventures]] that operate below critical mass (not enough affiliates) and/or with insufficient incentives have exhibit fluctuations in their activities. A [[venture]] is alive or stable if the frequency of contributions is high and if [[contributions]] happen with a certain periodicity. [[Ventures]] 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 [[ventures]] 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 [[venture]] for a certain duration he/she becomes an inactive [[affiliate]] and might be denied access to some decision making processes.
 * ''add more''...

← Older revision		Revision as of 17:26, 11 July 2025
Line 14:		Line 14:


−	~~Yes~~ another ~~theame~~ structure can take into consideration the level of involvement of an agent, either he/she is in the 1% (core), 9% (contributors) or the 90% (users). See this video [https://www.youtube.com/watch?v=xlXeMScO3F4 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 [[agent]] 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.	+	Yet another theme structure can take into consideration the level of involvement of an agent, either he/she is in the 1% (core), 9% (contributors) or the 90% (users). See this video [https://www.youtube.com/watch?v=xlXeMScO3F4 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 [[agent]] 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.

	==Feedback==		==Feedback==

@@ Line 27: / Line 27: @@
 ==Signaling==
 Tell [[affiliates]] that something has happened. Some [[events]] are important, others are less important.
-This would be pat of a notification system, customizable by [[agents]].
+This could be implemented as a notification system, customizable by [[agents]]. Signals must also be placed in context, where the focus of the agent / user is on the UI.
 ===Patrolling - economic activity and resources===
@@ Line 41: / Line 43: @@
 ===Getting opportunities===
 [[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.
 ==Search==

@@ Line 7: / Line 7: @@
 Examples of themes
-* project-centric theme, where the [[agent]] explores different [[projects]] for various 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.
+* venture-centric theme, where the [[agent]] explores different [[ventures]] for various 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 [[ventures]].
 * resource-centric theme, where the [[agent]] explores different [[resources]] for various reasons, to find something to use, to find something to offer, to find something to invest in ($, time, ...), to compare with other resources, etc. This is the Inventory view in the current [http://nrp.sensorica.co/accounting/inventory/ Sensorica's NRP-CAS].
 * agent-centric theme, where the agent explores other agents for various reasons, to find someone to do something, to see what someone is doing, to see how someone is related to someone else, etc.
-* activity type/domain-centric theme, where the agent 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, ... ,
+* activity type/domain-centric theme, where the agent explores [[ventures]] 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, ... ,
-* community-centric view, where the agent explores an entire community, compares it with other communities, sees what projects are embedded in this community context, etc.
+* community-centric view, where the agent explores an entire community, compares it with other communities, sees what [[ventures]] are embedded in this community context, etc.
@@ Line 31: / Line 31: @@
 ===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]] and other [[affiliates]], validate [[events]], monitor domains of activity (which can go across [[projects]] and [[process]]).
+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 [[ventures]], [[processes]] and other [[affiliates]], validate [[events]], monitor domains of activity (which can go across [[ventures]] 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 monitor his/her activites. Another example, if I am a specialist in x, I want to police everything about x.
+[[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 monitor his/her activities. 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 [[projects]]. Modifications of resources can have an impact on the entire OVN. That is because [[resources]] are independent building blocks on the [[NRP-CAS]], they exist across [[processes]] and [[projects]], and even networks. If someone modifies the description, the picture, or anything else about a [[resource]], others must know about it.
+[[Affiliates]] might create, modify and remix [[resources]] in [[processes]], in the context of [[ventures]]. Modifications of resources can have an impact on the entire OVN. That is because [[resources]] are independent building blocks on the [[NRP-CAS]], they exist across [[processes]] and [[ventures]], and even networks. If someone modifies the description, the picture, or anything else about a [[resource]], others must know about it.
 Knowing that a [[resource]] has been modified is important for many reasons
 # see if someone has improved it;
@@ Line 44: / Line 44: @@
 ==Search==
-The [[NRP-CAS]] doesn't have search functionality. It would be nice to be able to search [[projects]], [[resources]], [[agents]], ...
+The [[NRP-CAS]] doesn't have search functionality. It would be nice to be able to search [[ventures]], [[resources]], [[agents]], ...
 ==Time==
@@ Line 50: / Line 50: @@
 * ''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 if 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.
+* ''Evaluation'' - Some temporal characteristics of economic activities are important to evaluate [[ventures]]. For example, a [[venture]] is said to be "dormant" is the rate of contributions is low, or nul. A [[venture]] is unstable if economic activity is sporadic. Usually, [[ventures]] that operate below critical mass (not enough affiliates) and/or with insufficient incentives have exhibit fluctuations in their activities. A [[venture]] is alive or stable if the frequency of contributions is high and if [[contributions]] happen with a certain periodicity. [[Ventures]] 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.
+* ''Governance'' - Access to [[decision making]] is related to the type of [[affiliation]]. Most [[ventures]] 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 [[venture]] for a certain duration he/she becomes an inactive [[affiliate]] and might be denied access to some decision making processes.
 * ''add more''...