Hello implementers, I have some more user experience-related questions for you. All record pages (e.g. Acquisition) have "Save" and "Cancel" buttons. Save button saves the changes you've made and keeps you on the record page (you'll see a time stamp for the Save action at the top of the page e.g. Saved at 15:07). Cancel button cancels the changes you've made, and brings you back to the page you were on previously (e.g. Search Results). My questions are about the Cancel button: What are some of the use cases/situations you can think of where you might want to use the Cancel button? Is the interaction described above a desired behaviour for the Cancel button? Would you want the Cancel button to bring up a confirmation dialog (i.e. "Are you sure you want to cancel all your changes?") or is it undesirable? Thank you! :) Erin

Hi Erin, For data entry systems, it seems like the behavior I usually see is that if you hit the cancel button in order to "not save" the data you just entered or modified, you do get a dialog window asking you if you are sure. Because the save and cancel buttons are close together, I think it's important to have this confirmation. I think returning to the page you were on previously is a good way to go. Thanks, Chris On May 12, 2010, at 2:45 PM, Erin Yu wrote: > Hello implementers, > I have some more user experience-related questions for you. > > All record pages (e.g. Acquisition) have "Save" and "Cancel" buttons. > Save button saves the changes you've made and keeps you on the record page (you'll see a time stamp for the Save action at the top of the page e.g. Saved at 15:07). > Cancel button cancels the changes you've made, and brings you back to the page you were on previously (e.g. Search Results). > > My questions are about the Cancel button: > What are some of the use cases/situations you can think of where you might want to use the Cancel button? > Is the interaction described above a desired behaviour for the Cancel button? > Would you want the Cancel button to bring up a confirmation dialog (i.e. "Are you sure you want to cancel all your changes?") or is it undesirable? > > Thank you! :) > Erin > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

ditto to what Chris said - and to clarify, cancel returns you to the same page in the state it was in when you landed on it. I often cancel if I discover just as I hit save that I've made a mistake or that there's some new information coming that I want to wait for as it might make a difference to my entries and I don't want the interim information to potentially be seen and/or archived and cause confustion Marlita Kahn Project Manager Information Services & Technology Data Services 2195 Hearst Avenue Berkeley, CA 94720-4876 510-250-2488 marlita@berkeley.edu On May 12, 2010, at 2:56 PM, Chris Hoffman wrote: > Hi Erin, > > For data entry systems, it seems like the behavior I usually see is that if you hit the cancel button in order to "not save" the data you just entered or modified, you do get a dialog window asking you if you are sure. Because the save and cancel buttons are close together, I think it's important to have this confirmation. > > I think returning to the page you were on previously is a good way to go. > > Thanks, > Chris > > On May 12, 2010, at 2:45 PM, Erin Yu wrote: > >> Hello implementers, >> I have some more user experience-related questions for you. >> >> All record pages (e.g. Acquisition) have "Save" and "Cancel" buttons. >> Save button saves the changes you've made and keeps you on the record page (you'll see a time stamp for the Save action at the top of the page e.g. Saved at 15:07). >> Cancel button cancels the changes you've made, and brings you back to the page you were on previously (e.g. Search Results). >> >> My questions are about the Cancel button: >> What are some of the use cases/situations you can think of where you might want to use the Cancel button? >> Is the interaction described above a desired behaviour for the Cancel button? >> Would you want the Cancel button to bring up a confirmation dialog (i.e. "Are you sure you want to cancel all your changes?") or is it undesirable? >> >> Thank you! :) >> Erin >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

+1 _____ From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Chris Hoffman Sent: Wednesday, May 12, 2010 2:57 PM To: Erin Yu Cc: talk@lists.collectionspace.org Subject: Re: [Talk] Cancel button on record pages Hi Erin, For data entry systems, it seems like the behavior I usually see is that if you hit the cancel button in order to "not save" the data you just entered or modified, you do get a dialog window asking you if you are sure. Because the save and cancel buttons are close together, I think it's important to have this confirmation. I think returning to the page you were on previously is a good way to go. Thanks, Chris On May 12, 2010, at 2:45 PM, Erin Yu wrote: Hello implementers, I have some more user experience-related questions for you. All record pages (e.g. Acquisition <http://wiki.collectionspace.org/display/collectionspace/Wireframes+-+Acquis ition> ) have "Save" and "Cancel" buttons. Save button saves the changes you've made and keeps you on the record page (you'll see a time stamp for the Save action at the top of the page e.g. Saved at 15:07). Cancel button cancels the changes you've made, and brings you back to the page you were on previously (e.g. Search Results). My questions are about the Cancel button: * What are some of the use cases/situations you can think of where you might want to use the Cancel button? * Is the interaction described above a desired behaviour for the Cancel button? * Would you want the Cancel button to bring up a confirmation dialog (i.e. "Are you sure you want to cancel all your changes?") or is it undesirable? Thank you! :) Erin _______________________________________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace .org

 * What are some of the use cases/situations you can think of where
   you might want to use the Cancel button?
 * Is the interaction described above a desired behaviour for the
   Cancel button? 
 * Would you want the Cancel button to bring up a confirmation
   dialog (i.e. "Are you sure you want to cancel all your
   changes?") or is it undesirable?

If you hit the cancel button after creating an identification Number or after adding a new record to an Authority but before saving the record Would the expected behaviour be that the identification Number and the new record to authority would also be rolled back My personal view is... maybe the Identification Number should be rolled back so it is available for the next record created but probably not the authority as it may have been used by someone else already in their record. I am not sure how worried museums would be to effectively have sequences with missing identification Numbers Chris Erin Yu wrote: > Hello implementers, > I have some more user experience-related questions for you. > > All record pages (e.g. Acquisition > <http://wiki.collectionspace.org/display/collectionspace/Wireframes+-+Acquisition>) > have "Save" and "Cancel" buttons. > *Save* button saves the changes you've made and keeps you on the > record page (you'll see a time stamp for the Save action at the top of > the page e.g. Saved at 15:07). > *Cancel* button cancels the changes you've made, and brings you back > to the page you were on previously (e.g. Search Results). > > My questions are about the Cancel button: > > * What are some of the use cases/situations you can think of where > you might want to use the Cancel button? > * Is the interaction described above a desired behaviour for the > Cancel button? > * Would you want the Cancel button to bring up a confirmation > dialog (i.e. "Are you sure you want to cancel all your > changes?") or is it undesirable? > > > Thank you! :) > Erin > > ------------------------------------------------------------------------ > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

* What are some of the use cases/situations you can think of where
  you might want to use the Cancel button?
* Is the interaction described above a desired behaviour for the
  Cancel button?     * Would you want the Cancel button to bring  

Thanks all for the feedback. I agree, I also thought Cancel definitely needs a confirmation initially, then I remembered our wiki doesn't give any confirmation when you cancel (and I like it as a user). When I click cancel, I do so deliberately to undo what I did and revert to the last save. That said, I do think the confirmation is a good preventative measure and would like to suggest 1) including the confirmation dialogue and 2) adding a "Don't show this again" checkbox in the dialogue. I'd love to hear from the users. CMS users, speak up and have your thoughts heard! :) Erin P.S. Chris (Martin), earlier in the project, I think we decided that as soon as the user selects an ID number, the number gets reserved forever, so even if you cancel out of it, the number is gone (because numbers are cheap). Services team, correct me if I'm wrong... On 13-May-10, at 7:45 AM, Chris Martin wrote: > If you hit the cancel button after creating an identification Number > or after adding a new record to an Authority but before saving the > record > > Would the expected behaviour be that the identification Number and > the new record to authority would also be rolled back > > My personal view is... > > maybe the Identification Number should be rolled back so it is > available for the next record created but probably not the > authority as it may have been used by someone else already in their > record. > > I am not sure how worried museums would be to effectively have > sequences with missing identification Numbers > > Chris > > > Erin Yu wrote: >> Hello implementers, >> I have some more user experience-related questions for you. >> >> All record pages (e.g. Acquisition <http://wiki.collectionspace.org/display/collectionspace/Wireframes+-+Acquisition >> >) have "Save" and "Cancel" buttons. >> *Save* button saves the changes you've made and keeps you on the >> record page (you'll see a time stamp for the Save action at the top >> of the page e.g. Saved at 15:07). >> *Cancel* button cancels the changes you've made, and brings you >> back to the page you were on previously (e.g. Search Results). >> >> My questions are about the Cancel button: >> >> * What are some of the use cases/situations you can think of where >> you might want to use the Cancel button? >> * Is the interaction described above a desired behaviour for the >> Cancel button? * Would you want the Cancel button to bring >> up a confirmation >> dialog (i.e. "Are you sure you want to cancel all your >> changes?") or is it undesirable? >> >> >> Thank you! :) >> Erin >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >

* What are some of the use cases/situations you can think of where
  you might want to use the Cancel button?
* Is the interaction described above a desired behaviour for the
  Cancel button?     * Would you want the Cancel button to 

At 18:32 -0400 2010-05-13, Erin Yu wrote: >P.S. Chris (Martin), earlier in the project, I think we decided that >as soon as the user selects an ID number, the number gets reserved >forever, so even if you cancel out of it, the number is gone >(because numbers are cheap). Services team, correct me if I'm >wrong... That sounds right, from memory - at least from the services standpoint. We eventually want to do much more sophisticated management of IDs, but for now, each new request to retrieve a new ID from a particular ID generator (aka 'ID pattern' or 'number pattern') simply generates a new ID. Aron > > >On 13-May-10, at 7:45 AM, Chris Martin wrote: > >>If you hit the cancel button after creating an identification >>Number or after adding a new record to an Authority but before >>saving the record >> >>Would the expected behaviour be that the identification Number and >>the new record to authority would also be rolled back >> >>My personal view is... >> >>maybe the Identification Number should be rolled back so it is >>available for the next record created but probably not the >>authority as it may have been used by someone else already in their >>record. >> >>I am not sure how worried museums would be to effectively have >>sequences with missing identification Numbers >> >>Chris >> >> >>Erin Yu wrote: >>>Hello implementers, >>>I have some more user experience-related questions for you. >>> >>>All record pages (e.g. Acquisition >>><http://wiki.collectionspace.org/display/collectionspace/Wireframes+-+Acquisition>) >>>have "Save" and "Cancel" buttons. >>>*Save* button saves the changes you've made and keeps you on the >>>record page (you'll see a time stamp for the Save action at the >>>top of the page e.g. Saved at 15:07). >>>*Cancel* button cancels the changes you've made, and brings you >>>back to the page you were on previously (e.g. Search Results). >>> >>>My questions are about the Cancel button: >>> >>> * What are some of the use cases/situations you can think of where >>> you might want to use the Cancel button? >>> * Is the interaction described above a desired behaviour for the >>> Cancel button? * Would you want the Cancel button to >>>bring up a confirmation >>> dialog (i.e. "Are you sure you want to cancel all your >>> changes?") or is it undesirable? >>> >>> >>>Thank you! :) >>>Erin >>>------------------------------------------------------------------------ >>> >>>_______________________________________________ >>>Talk mailing list >>>Talk@lists.collectionspace.org >>>http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> > > >_______________________________________________ >Talk mailing list >Talk@lists.collectionspace.org >http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

* What are some of the use cases/situations you can think of where
  you might want to use the Cancel button?
* Is the interaction described above a desired behaviour for the
  Cancel button?     * Would you want the Cancel button to bring 

Perfect. It would be what I expected but I thought it worth double checking Chris Aron Roberts wrote: > At 18:32 -0400 2010-05-13, Erin Yu wrote: >> P.S. Chris (Martin), earlier in the project, I think we decided that >> as soon as the user selects an ID number, the number gets reserved >> forever, so even if you cancel out of it, the number is gone (because >> numbers are cheap). Services team, correct me if I'm wrong... > > That sounds right, from memory - at least from the services standpoint. > > We eventually want to do much more sophisticated management of IDs, > but for now, each new request to retrieve a new ID from a particular > ID generator (aka 'ID pattern' or 'number pattern') simply generates a > new ID. > > Aron > >> >> >> On 13-May-10, at 7:45 AM, Chris Martin wrote: >> >>> If you hit the cancel button after creating an identification Number >>> or after adding a new record to an Authority but before saving the >>> record >>> >>> Would the expected behaviour be that the identification Number and >>> the new record to authority would also be rolled back >>> >>> My personal view is... >>> >>> maybe the Identification Number should be rolled back so it is >>> available for the next record created but probably not the >>> authority as it may have been used by someone else already in their >>> record. >>> >>> I am not sure how worried museums would be to effectively have >>> sequences with missing identification Numbers >>> >>> Chris >>> >>> >>> Erin Yu wrote: >>>> Hello implementers, >>>> I have some more user experience-related questions for you. >>>> >>>> All record pages (e.g. Acquisition >>>> <http://wiki.collectionspace.org/display/collectionspace/Wireframes+-+Acquisition>) >>>> have "Save" and "Cancel" buttons. >>>> *Save* button saves the changes you've made and keeps you on the >>>> record page (you'll see a time stamp for the Save action at the top >>>> of the page e.g. Saved at 15:07). >>>> *Cancel* button cancels the changes you've made, and brings you >>>> back to the page you were on previously (e.g. Search Results). >>>> >>>> My questions are about the Cancel button: >>>> >>>> * What are some of the use cases/situations you can think of where >>>> you might want to use the Cancel button? >>>> * Is the interaction described above a desired behaviour for the >>>> Cancel button? * Would you want the Cancel button to bring >>>> up a confirmation >>>> dialog (i.e. "Are you sure you want to cancel all your >>>> changes?") or is it undesirable? >>>> >>>> >>>> Thank you! :) >>>> Erin >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>>> >>> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >