Example Departmental Administrator Session Workflow

Based on SFU's experience with distributed access the legacy registry web interface, the attached workflow is first draft of how we see an everyday user moving through the interface. People who use the interface on a regular basis do so repetitively and extensively. The goal of the workflow and UI design is to minimize the required steps to perform any given action.

• Main Page
  • Simple layout, two obvious options, Find an existing person or Add a new person.
• Find Person
  • Several operations begin by finding an existing person. Updates, deletes, Moving SoR Person objects or generating activation keys all happen from this point.
• Add Person
  • If adding a person, the person object should be generated with minimal information. User should be able to leave the workflow once all required information is provided. If a Role is not required for an entity in the registry, then that should be optional to complete. So once the bare minimum fields are provided, the flow rejoins as though the newly created person was just found via search.

More complicated workflows will be required for users with greater administrative access, but this flow starts with the most common users in the most common situations.