jhain
commented
9 years ago It’s hard w/o seeing the application, but basically, what you’re proposing is to not have the whole process on one, intimidatingly long, screen, but instead have it parsed out into sections, correct? Following your proposed sequence of
Location page --> Add Resource button --> Add Resource page Resource page --> Edit button --> Edit Resource page Resource page --> Assess button --> Assess Resource page
Makes sense to me – again, this is w/o actually seeing most of the problems you cite.
J
From: adolski [mailto:notifications@github.com] Sent: Thursday, December 18, 2014 11:18 AM To: PresConsUIUC/PSAP Subject: [PSAP] Separate resource adding/editing and assessing processes (#190)
I have been thinking about this for awhile.
The resource add/edit/assess form is rather long. I think the original idea was that this was unavoidable and that the assessment could be carried out in pieces over time, and that there would be a progress bar that would track completion. We have already ditched the progress bar and made the form appear less complicated by hiding the "advanced info" fields by default. I think the current resource add/edit/assess all-in-one approach has several problems:
1) It's intimidating 2) It discourages batch entry because users may feel like they have to fill out the assessment info immediately even though it's optional 3) Since we aren't tracking completion progress (it's not really feasible), it is hard to go back and find resources that have been incompletely entered 4) I am worried that users will skip over the advanced info because it's hidden by default 5) The overall form length is substantial, especially when advanced info is visible 6) The form is going to be different for collections -- assessment won't be available. This affects the page layout, as the assessment section tabs are displayed in the left column. With collections, there are no assessment section tabs and thus the left column will remain empty, which looks weird 7) Ambiguous terminology throughout the application; currently "adding/editing" and "assessing" a resource are used interchangeably even though they are different tasks. "Resource" is used in many places interchangeably with "assessment," which is confusing.
So, my idea is to separate the assessment process from the adding/editing process. The entry points to the pages would look like:
Location page --> Add Resource button --> Add Resource page Resource page --> Edit button --> Edit Resource page Resource page --> Assess button --> Assess Resource page
I think this would solve most of the above problems.
Feedback welcome.
— Reply to this email directly or view it on GitHubhttps://github.com/PresConsUIUC/PSAP/issues/190.
adolski
I have been thinking about this for awhile.
The resource add/edit/assess form is rather long. I think the original idea was that this was unavoidable and that the assessment could be carried out in pieces over time, and that there would be a progress bar that would track completion. We have already ditched the progress bar and made the form appear less complicated by hiding the "additional info" fields by default. I think the current resource add/edit/assess all-in-one approach has several problems:
1) It's intimidating 2) It discourages batch entry because users may feel like they have to fill out the assessment info immediately even though it's optional 3) Since we aren't tracking completion progress (it's not really feasible), it is hard to go back and find resources that have been incompletely entered 4) I am worried that users will skip over the additional info because it's hidden by default 5) The overall form length is substantial, especially when additional info is visible 6) The form is going to be different for collections -- assessment won't be available. This affects the page layout, as the assessment section tabs are displayed in the left column. With collections, there are no assessment section tabs and thus the left column will remain empty, which looks weird 7) Ambiguous terminology throughout the application; currently "adding/editing" and "assessing" a resource are used interchangeably even though they are different tasks. "Resource" is used in many places interchangeably with "assessment," which is confusing.
So, my idea is to separate the assessment process from the adding/editing process. The entry points to the pages would look like:
Location page --> Add Resource button --> Add Resource page Resource page --> Edit button --> Edit Resource page Resource page --> Assess button --> Assess Resource page
I think this would solve most of the above problems.
Feedback welcome.