| Version 1 (modified by ed, 3 years ago) (diff) |
|---|
Purpose
- Represent the global range of TIs
- Make local TI registration easier than at present
- Make National hub registration easier than at present
Key Audience
- TI representatives (local-level) Internationally
- National hub representatives
- Sponsors of Transition Network and around
Staff and roles
- Technical project manager: Ed
- Hubs engagement: Ben at first, then Ed? Filipa?
Budget
- 7,000 GBP
- technical time by developers
- lead tech
- international consultant tech
- design
- Not in this budget: Transition Network staff
- Ben Brangwyn
- Filipa Pimental
- Ed Mitchell
- Not in this budget: other international works
- translation of key pages on TN.org into many languages
- website design work to represent the above
- website tech work to enable the above
Timeline
NB: our developer is booked for this work!
- May/June? 2013: Project initiation document
- June 2013: workflow established
- July 2013: need some feedback from some national hubs
- July 2013: first developer briefing workshop
- August 2013: developer booked in for work
- September 2013: beta product built and ready for the national hubs meeting
Process
Widget-style approach as per the PSE widget:
- ‘distribute the interface’ (data hosted on TN.org servers) for easy embed and re-use on sites around the world
- embeddable maps and listings for national hubs websites
- embeddable widget (sidebar/full page) for TIs’ websites
- add a TI listing in modal pop-up launched from widget
Data
There will be a ‘slimline’ TI data type:
- TI name
- TI website
- TI location
- TI Primary Point of Contact (must be a TN.org registered user)
Support
- Transition Network need to take into account what level of support it can/not offer for this service - in what language
- Budget for ongoing support?
Business offer to International Hubs
Transition Network offers this as a product and service to National Hubs with the following options. There is nothing in the MoU at the time of writing.
- Use the system as stands (use embeddable iFrames into own site)
- will need agreement on support - how they support their countries in their languages
- support includes handy guides
- Provide machine readable data (with agreed data structures)
- Don’t use the system at all
- We will need some form of data agreement with national hubs
- e.g. TUS wanting the US Ini data for their engagement work
- e.g. Germany building their own hub (ed nb: Michael Bakonyi email exchange)
What is included in this budget
- Support pages for Initiatives Hub
What is not included in this budget
- Key pages for translation from TN.org?
- Including language/country-based pointers on TN.org to country pages?
- what is a country page?
Languages
- Ed not sure about how easy/hard it is to do drupal multilingual works
- Suggest not trying to do everything at once
- possibly focus on key languages (is there a standard for this?)
- take a lead from our visitor logs?
- English is the lingua franca for the national hubs group
Visitor reports by country (May 2013)
- UK
- US
- Australia
- Germany
- Canada
- Portugal
- France
- Italy
- Spain
- Netherlands
- India
- Belgium
- Norway
- Sweden
- Ireland
