Workflows & IA

• See also ArchitectureOptions and the SolutionDesign.
• Note, to avoid confusions around text and language, I've used the Drupal convention of t('text'), which means the English word 'text' translated into appropriate [language] for a user's [country]. e.g. t('Search') would be 'Rechercher' in French.

Workflows: TN.org (D6)

Note that 'Normal' initiative viewers and all regular visitors will see no changes.

'National Hub' page viewer (D6)

1. Will see a 'National' page at ​http://www.transitionnetwork.org/world/[localised_country_name] (e.g. in native language like /france, /deutschland, /brasil, but not /germany, /brazil etc).
2. Page will consist of standard D6/English TN.org site structure, menus and blocks, but content area will be the language appropriate for the country.
3. The top part of the content area will consist of some translated welcome/info text. The lower part of the page will hold the "Full page widget" section of "Listings IIRS Widget (D7)", below.
4. Details of the widget part of the page are below.

Workflows: Widgets (D7)

"Full page listings" widget

1. URL TBC but similar to ​http://www.transitionnetwork.org/[langcode]/[localised_country_name]/widget/initiatives/display/full -- though this not be shown to the user usually except when getting the widget code.
2. The widget will have the following display tabs:
   1. t('Latest') - shows users to see the latest [country] initiatives listed,.
   2. t('Map') - shows all the [country] initiatives on a map.
   3. t('Search') - allows searching of initiatives within [country] by criteria.
3. An t('Add your initiative') button opening the Add widget popup -- for details of this, see next section.
4. An t('Initiative details') popup which appears whenever an initiative link is clicked within the widget area. Opens a new popup showing the full D7 node view in [language] for the initiative selected. This popup also allows users to log in and edit the ini if they have permissions.

"Sidebar listings" widget

1. URL TBC but similar to ​http://www.transitionnetwork.org/[langcode]/[localised_country_name]/widget/initiatives/display/sidebar -- though this not be shown to the user usually except when getting the widget code.
2. Simple listings mode only, DECIDED: based on recently posted nation-wide
3. An t('Add your initiative') which opens 'Add Widget' (see below) in popup.

"Button-only" widget

1. Like sidebar but with only the t('Add your initiative') button which opens the "Add" widget display, below.

"Add" widget popup display (D7)

1. User clicks button to t('Add your initiative'), popup opens showing URL TBC but similar to ​http://www.transitionnetwork.org/[langcode]/[localised_country_name]/widget/user/login
2. User logs in or registers -- ?? DECIDED: registration includes social media option ?? QUESTION: IS THIS AUTHENTICATION ONLY??
3. User enters initiative details. (URL TBC but similar to ​http://www.transitionnetwork.org/[langcode]/[localised_country_name]/widget/initiatives/add
4. User gets thanks page. URL TBC but similar to ​http://www.transitionnetwork.org/[langcode]/[localised_country_name]/widget/initiatives/add/ok

"View Detail" widget popup display (D7)

1. Any link to an initiative within the Listings widgets opens a popup in [language] showing the full node view of the initiative. URL TBC but likely ​http://www.transitionnetwork.org/[langcode]/[localised_country_name]/widget/initiative/view/[nid]
2. There will be an option to t('Log in to make changes if the user is the owner'), or register and submit their own initiative.
3. If the user is logged in, the t('Edit') tab will be available to users who have permission (editors, admins and the content author).
4. The page will be fully translated into [language].

Workflows: D7 site (non-widget)

• Some users (admins) will need to oversee things on the D7 site and perform tasks. These admin views are TBC and will not be visible to normal users.
• Since some of the views are public, it's possible some people will come to them. When viewed outside the widget context, such pages should still work on their own.

Information Architecture

User

Mandatory

Standard Drupal user account fields:

1. t('Email') = (built into Drupal)
2. t('Username') = (built into Drupal) --> will be generated from first/middle/last name fields (below) in format "First MM Last" (where M is a single middle name initial). Numbers will be appended if the resultant name is registered in site already.
3. t('Password') = (built into Drupal)

Additional fields:

1. t('First name') = field_user_name_first
2. t('Middle names') = field_user_name_middle
3. t('Last name') = field_user_name_last
4. t('Language') = Provided by core Locale module... This will need to be set automatically by the widget context, and as a fall back should be ​displayed on the registration form)
5. t('Country') OR t'('Address') A custom field, again should be filled from widget context.

Hidden metadata

• UUID = The Universally Unique ID of the user -- system generated, globally shared.
• Uid = The local Drupal user ID -- system generated and not shared outside current site.
• Status = Drupal default 'active/blocked' flag. Allows users to be hidden rather than deleted.

Initiative

Mandatory

1. t('Initiative name')
2. t('Initiative location')

Optional but recommended

1. t('Initiative website')

Hidden metadata

• UUID = The Universally Unique ID of the initiative -- system generated, globally shared.
• Nid = The local Drupal node ID -- system generated and not shared outside current site.
• Status = Drupal default 'published' flag. Allows initiatives to be hidden rather than deleted.

Administration workflows

The National Hub administrator will be able to add/edit/unpublish any Initiative item in their own country. They will be able to see the 'edit' function for all these initiatives as happens on TN.org now.

Useful details from ​PSE workflow?