Skip to content
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

NRP front page #502

Open
TiberiusB opened this issue May 17, 2016 · 8 comments
Open

NRP front page #502

TiberiusB opened this issue May 17, 2016 · 8 comments

Comments

@TiberiusB
Copy link

On the front page there are a few fields "Work being done...", "Current needs. Get involved!", "Value being created"
It is better to arrange those according to date, from most recent to further away in time. On SENSOPRICA's NRP front page, http://nrp.sensorica.co/ , the "Work being done..." is very long. It is more interesting to see what people are doing now, and cut this list to 6 months or so.

@TiberiusB
Copy link
Author

I would also add most active projects. This helps sensoricans navigate to their projects faster, from the first page, by clicking on them, and find processes where they can log work. But it also shows other people development/work contexts that are busy.

@fosterlynn
Copy link

Good ideas.

cillian added a commit to cillian/valuenetwork that referenced this issue Jun 24, 2016
cillian added a commit to cillian/valuenetwork that referenced this issue Jun 24, 2016
cillian added a commit to cillian/valuenetwork that referenced this issue Jun 24, 2016
bhaugen added a commit that referenced this issue Jul 1, 2016
Show most active projects on the homepage. #502
@bhaugen
Copy link

bhaugen commented Jul 13, 2016

Most active projects feature deployed, and I think the other improvements requested above were completed, too. Closing issue. Re-open if I missed something.

@bhaugen bhaugen closed this as completed Jul 13, 2016
@TiberiusB TiberiusB reopened this Jul 16, 2016
@TiberiusB
Copy link
Author

Need to discuss the criteria used for this list?
Is is last logs, frequency of logs, the amount of time, a combination of those and more?
It`s a good start, but we need to tweak it.

I don`t think the Piezo pump should show in there
http://nrp.sensorica.co/accounting/contributions/236/
It has one contribution in 2016 and the next one is in 2014

Same with the not defined project.
http://nrp.sensorica.co/accounting/contributions/197/

Renovation lab should be pretty high in the list.
http://nrp.sensorica.co/accounting/agent/406/
206 contributions and almost all in 2016

@TiberiusB
Copy link
Author

The "Work being done..." section is not very useful. It is too long and too granular... I think these types of work from processes are meaningless if not presented in context. The Process has more context.
It is rare that we add descriptions to these types of work when we create them in processes. That would be a lot of work and realistically, now one will systematically do it. The names are self-descriptive. So we cannot rely on the description of types of work.
One possibility is to cluster types of works and provide links to different processes, so one can chose to do something knowing more about the impact/purpose of this work.

@TiberiusB
Copy link
Author

The "Value being created" section presents data that is not relevant to current activities. Does the filter only act on material assets? If so, I think we need to enlarge that to digital assets too.

@sqykly
Copy link

sqykly commented Mar 14, 2018

@TiberiusB
It looks like there was an attempt to fix the "Purpose: " bit, since a {% if %} was added to see if there is a process associated, but the text still comes from the item itself. Do you want the item's description to override the process's if it has a description?

Tentatively I'm just switching it over to use the process's timeline_description, which is the process notes or the process type's description if there are no process notes.

@sqykly
Copy link

sqykly commented Mar 14, 2018

It looks like the "Value being created" section is now including documents and such, so that is fixed?

sqykly added a commit to sqykly/valuenetwork that referenced this issue Mar 14, 2018
addresses valnet#502 by using the Process's description instead of the Work item's for the purpose, which is more likely to be filled than the work item's.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants