Changes between Version 18 and Version 19 of IIRS/WorkflowsProcesses
- Timestamp:
- 12/11/13 20:41:34 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IIRS/WorkflowsProcesses
v18 v19 53 53 54 54 === 1. Installing the National Hub installation using the Aegir system === 55 1. Jim is going to fill this in here 56 1. Jim is going to fill this in here 57 1. Jim is going to fill this in here 58 1. Jim is going to fill this in here 55 1. [Techie] builds Latest Transition National Hub distro/platform using the [https://github.com/transitionnetwork/transitionnetwork_d7/blob/master/build-d7-hub-national-panopoly.make build-d7-hub-national-panopoly.make makefile] OR the current one is used if already present on the target server. 56 2. [Techie/Admin] The site is installed using the Transition Network National Hub (Panopoly) profile for the chosen domain name. If using Aegir then the profile is simply chosen, otherwise a user will need to choose this when running the installer. 57 3. [Administrator] Simple instructions are followed to enable the language of their choice, and give the site a name, set any other country-specific things. 58 4. [Administrator] sets up a couple of key user accounts for other staff if necessary. 59 59 60 60 61 === 2. Translating the relevant content === 61 ED QUESTION: is this where the NHA does the translation? He thinks so, so he's adding the translation pieces here :62 ED QUESTION: is this where the NHA does the translation? He thinks so, so he's adding the translation pieces here -- '''JK YES -- process to follow''': 62 63 1. NHA needs to be able to 63 a. know what they need to translate64 a. site options65 a. email confirmations66 a. about and thank you text67 a. other?68 a. have a simple process to translate these pieces69 * Ed is not sure what this is for now 64 a. know what they need to translate 65 a. site options 66 a. email confirmations 67 a. about and thank you text 68 a. other? 69 a. have a simple process to translate these pieces 70 * Ed is not sure what this is for now -- JK process to follow... 70 71 71 === 3. Configuring the widget using the widgetiser ===72 === 3. Configuring the widget using the Widgetizer === 72 73 73 The National Hub administrator will be able to set up a widget and then 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.74 The National Hub administrator, and any editor added to the site, will be able to set up a widget and then 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. 74 75 75 76 Useful details from [https://wiki.transitionnetwork.org/Sharing_Engine/Technical_workflow_%26_business_logic#Entry_widget:_Register.2Flogin_.26_submission_entry_workflow PSE workflow]? 76 77 77 1. Go to widgetiser build page78 1. Choose widget type 79 1. Add 'view pane path' 80 1. Add modal popup path' 81 1. Add modal button text 82 1. Preview widget 83 1. Copy widget code 84 1. Embed into full page of National Hub website 78 1. Go to Widgetizer build page (/widgetizer/build). 79 1. Choose widget type. 80 1. Add 'view pane path' (if widget type includes it) -- presently this is [language code]/tn-widgets/national/initiatives/[country code] -- e.g. ''pt-pt//tn-widgets/national/initiatives/pt'' 81 1. Add modal popup path' -- presently this is [language code]/tn-widgets/national/user-submit-thanks/[country code]/[content type] -- e.g. ''pt-pt/tn-widgets/national/user-submit-thanks/pt/initiative'' 82 1. Add modal button text -- e.g. t('Add your inititative') 83 1. Preview widget. 84 1. Copy widget code. 85 1. Embed into full page of National Hub website -- ensure the correct text format/filter is set if using a content management system that filters input, should be equivalent to 'Full HTML' or 'Raw' etc. 85 86 86 87 === 4. Administering TI submissions === 87 1. user submits a TI via the widget. They may have set up a new account (will have for the alpha). The submission is POST-moderated - i.e. it goes into the system as PUBLISHED88 1. User submits a TI via the widget. They may have set up a new account (will have for the alpha). The submission is POST-moderated - i.e. it goes into the system as PUBLISHED. 88 89 1. Each TI submission triggers an email alert to the NHA including URL to user account and TI profile 89 1. NHA can see the user account and TI profiles without logging into their service site 90 1. NHA can see the user account and TI profiles without logging into their service site -- ''JK question''' -- see TIs ''and user accounts'' without logging in? Why wouldn't thye log in? Why expose user accounts to public? Or is this going into the email sent to the admins? 90 91 1. NHA can log into their service site - when logged in, the NHA can: 91 92 1. See a list of all the TI submissions in a view showing TI name, URL, PPOC link, status ((not)published) … … 127 128 === Mandatory === 128 129 1. t('Initiative name') 129 1. t('Initiative location') 130 1. t('Initiative location') -- Address Field widget, international standardised address formats but with the 'street' address made non-mandatory. 130 131 131 132 === Optional but recommended === 132 133 1. t('Initiative website') 134 1. t('Summary') - 255 character simple, punchy 'about this ini' text field 133 135 134 === Available in CT but not in widget (yet) === 135 1. t('Summary') - 255 character simple, punchy 'about this ini' text field 136 1. t('Further details') - Free text HTML/WYSIWYG field to hold anything else needed: ED 11/12/13: we will not do this for now 136 === Available in CT but not in widget === 137 1. t('Further details') - Free text HTML/WYSIWYG field to hold anything else needed: ED 11/12/13: we will not do this for now -- JK 11/12/13 - it's already done! However, it's hidden from widget users. It's a required 'base' field and will be used by many content types. Leaving in for now as taking it out will only incur pain another time... ok Ed? 137 138 138 139 === Hidden metadata === … … 142 143 * Status = Drupal default 'published' flag. Allows initiatives to be hidden rather than deleted. 143 144 * Coordinates = the 'Location' (address) field will be geocoded to provide coordinates so the ini can be placed on the map. 144 145 146 147 == Archived stuff we're not doing which was in the page ==148 149 === "Sidebar listings" widget ===150 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.151 1. Simple listings mode only, ''' DECIDED: based on recently posted nation-wide '''152 1. An t(''''Add your initiative'''') which opens 'Add Widget' (see below) in popup.