Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


Critical questions in bold orange. Recommendations in blue.


Admin SetsCollectionsCollection TypesWorksComments
New
tabsDescription onlyDescription onlyDescription onlyAll tabsI'm ok with the difference in action here because the works UI is significantly different than the others.
save button nameSaveCreate CollectionSaveSave

Which pattern do you want to move towards?

"Save" for all

save goes toeditediteditshow

Seems like Works is a set pattern by itself.  The other 3 should probably be the same.

Agree, the Save button on Work should do what it currently does: redirect to the Admin Show Work page.

The other three should also continue as is, since the first Save results in new tabs being displayed.

cancel button nameCancelCancelCancelCancelThis is truly cancel in all cases.
cancel goes toindexHomeindexDashboardThese seem wrong and should probably be index for all.
Edit
tabsAll tabsAll tabsAll tabsAll tabsThis seems correct in all cases.
save button nameSaveUpdate CollectionSaveSave

Which pattern do you want to move towards?

"Save changes" for all

save goes toeditshoweditshow

Which pattern do you want to move towards?

I think we should remain on the same tab as where the save is being made, since we have no way to know what the user might want to do next (verify their change in another window, edit another tab, etc.).

cancel button nameCancelCancelCancelCancelIf we stay on the edit page, it seems like this should be Done.
cancel goes toindexHomeindexDashboardThese seem wrong and should probably be index for all.
Participants
has save button?noyesyesyesI'm not as concerned about this, but it is an inconsistency.
add happens immediatelyyesyesyesyesThis seems correct in all cases.




  • No labels