Tnv3/architecture

IIRS Javascript widget:  

• Not good for National Hub innovation
• data is stored on TN.org

• National Hub search doesn't find the TI

• Doesn't integrate with the National Hub user system so they won't be able to login after registration
• Politically 'colonial' in that National Hub doesn't own or control data
• Doesn't require any responsibility for the National Hub Administrator: easy out of the box solution
• Would use Javascript to hook in to and change

• Details on TIs and functions like mapping all works through Javascript widgets from TN

• Website does not know who the user is so cannot provide any *custom* context sensitive content

• 

IIRS PHP native Wordpress plugins and Drupal modules and others as required... paying attention also to version differences / requirements

• good for National Hub innovation

• data is stored on the National Hub site

• TN.org syncs the data to its database

• National Hub search and user authentication all works
• Politically 'correct' in that the National Hubs have complete control over their own data and TN.org requests updates
• Requires National Hub administration to take responsiblity for data
• standard simple PHP plugin, easy to hook in to and change

• Data stored locally, easy to use and innovate around

• framework abstraction layer
• I think thinking about how this data might end up in a TN webapp (ios/android) might be worth considering...
• NOTE: The TN site only allows authenticated sessions via HTTPS. All data transfers to and from the TN server should also be HTTPS only as the transfers will contain things such as email addresses. do we want to authenticate first before adding TIs? (From memory we have discussed having login/authentication as the last step in the past, I don't know how this is best done... ) and as who? it's a publicly accessible system... User: remoteTImanager? -> permission: remoteTImanagement?
  

IIRS National Hub "spin ups"

• one website

• one code base

• one database

• several domains pointing to this single website

• multiple translations of content

• automatic language switching according to domain used to access

• content in one non-English language also that appears only for that domain

• effectively several websites in one website because of content translations

• theme per domain to allow powerful customisation of National Hub

• Functuonality available is fixed and not controlled on a per domain basis

• not necessarily Drupal (To Be Decided)

• 

IIRS Natonal Hub Distributions

• far future