Purpose

1. Represent the global range of TIs
2. Make local TI registration easier than at present
3. Make National hub registration easier than at present

Key Audience

1. TI representatives (local-level) Internationally
2. National hub representatives
3. 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

1. technical time by developers
2. lead tech
3. international consultant tech
4. design

• Not in this budget: Transition Network staff

1. Ben Brangwyn
2. Filipa Pimental
3. Ed Mitchell

• Not in this budget: other international works

1. translation of key pages on TN.org into many languages
2. website design work to represent the above
3. 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

1. embeddable maps and listings for national hubs websites
2. embeddable widget (sidebar/full page) for TIs’ websites
3. 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)

1. will need agreement on support - how they support their countries in their languages
2. 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

1. e.g. TUS wanting the US Ini data for their engagement work
2. 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?

1. 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)

1. UK
2. US
3. Australia
4. Germany
5. Canada
6. Portugal
7. France
8. Italy
9. Spain
10. Netherlands
11. India
12. Belgium
13. Norway
14. Sweden
15. Ireland