You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently in the process of analysing your responses to the Pipeline usage survey held earlier this year. Some of the feedback requires some more elaboration or discussion. Below are some responses in the topic "user interface":
One organisation requested a more easy-to-use user interface:
Q: What do you think are the 3 greatest weaknesses of Pipeline?
Lack of windowed or more guided user interface
Q: Please describe any functionality you would like to see in Pipeline in future
A windowed, more easy-to-use user interface
Q: Would you encourage other organizations to consider using Pipeline in their production workflow?
If I could ask for something it would be that there should be I'm not really well positioned to answer this as a participant in the pipeline development with a quite advanced knowledge of how it works. But other colleagues and the former project manager of our production chain stated to me that they found the application to be not really easy to use for non-technical users, or users that usually have application with a windowed user interfaces (like Windows users). It is difficult to push its usage on machine of users' that are don't part of organizations with an IT department.
Another organisation mentioned that they need both version 1 and 2 of Pipeline and that it complicates their workflow:
Q: What do you think are the 3 greatest weaknesses of Pipeline?
We need both versions (1 y 2) for cover our needs
qualities distributed between both versions
[Pipeline 2] does not convert from daisy 3 to 2.02 with full text
Q: Please describe any functionality you would like to see in Pipeline in future
Unify all in one
One organisation mentioned a "simple UI for validation":
Q: Please describe any functionality you would like to see in Pipeline in future
Simple UI for validation
I would like to know:
Does the new GUI meet your needs better? Does it improve the usability? Do you have suggestions for further improving the GUI?
Would a Pipeline 1 back-end for the Pipeline 2 web and Java APIs, that exposes a specific (restricted) set of Pipeline 1 scripts, be a solution for you?
"Simple UI for validation" needs some elaboration please.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are currently in the process of analysing your responses to the Pipeline usage survey held earlier this year. Some of the feedback requires some more elaboration or discussion. Below are some responses in the topic "user interface":
One organisation requested a more easy-to-use user interface:
Another organisation mentioned that they need both version 1 and 2 of Pipeline and that it complicates their workflow:
One organisation mentioned a "simple UI for validation":
I would like to know:
Beta Was this translation helpful? Give feedback.
All reactions