-
Notifications
You must be signed in to change notification settings - Fork 92
Collaboration Call: September 21, 2018
Pre-call technical catch-up - see below
UK team
- Christopher Norris, first time on this call and will be helping out with this work. Not a developer, but an extremely gifted statistical officer.
- Will be helping to incorporate the interactive maps on the site and helping to incorporate multilingual capacity to the site.
- Brock, Chris and Ann had a meeting this morning to explore options for the technical details moving forward.
- Talked through the changes with the proof of concept, Jekyll theme, and multilingual.
- Mapping tool
- Guidance for architecture diagrams and hosting
- Talking through suggestions to change the reporting status
- UK scheduled to do their VNR and next year and will be working on that soon.
- Ann put out an advertisement for a developer for the site
US team
- Kali asked about the update on the translation
- Brock sent out a list with the french translation spreadsheet page to help with the translation.
- Kali will take some time to review the links.
- What will be translated?
- Not the UN pages
- Mostly the indicators
- Need a logo for the new site. The one on the upper left hand corner.
- Don’t need the lingo in the old logo
- Brock- creating a contrast version would be good to make as well so that we can use it for the next site
- Will pull the logo for the different language from the UN website with the logos
- Translation should be pretty simple and shouldn’t need much instruction. But Phil will work on a few lines for instructions and descriptions for the translator position
- Kali - What are the outstanding issues that need to be worked on for the merge? Wants to announce it along with the data call soon.
- Brock and Phil will get together this afternoon and can provide more of an update after that.
- Data providers have changed so we may need to change part of the site to mention that.
CODE team
- Wrapping up documentation and blog post on wide versus tidy
- Working on a blog post for training on how to setup the site through Amazon web services.
- Also started working on a proof of concept for a local reporting platform. Brock will be speaking at a conference in NYC next Friday and will be demonstrating this platform.
- UT translation project
- Caleb has been working with UT students to translate the site into the UN-supported languages. Has translators for Russian, Arabic, Chinese, Farsi, and Spanish
- Will follow up with them to find a French Translator.
Country/subnational interest in cloning the NRP
- Ann - working with Ghana and Rwanda and they are planning on soft launching in October. Omar will be in the WDF panel so it will be good to have him there.
- 80% chance that Phil will get his approval to travel to the WDF
- Ann - still having conversations with Germany about the platform
- Brock looked through the Australian site and it seems like it was maybe inspired by the platform, but probably not using it. Ann will follow up to see how they decided to use it and why.
- Chris - a couple of members on his team have been using APIs to pull data from different sources. Has there been any work on this?
- Brock has worked on it before and had done a proof-of-concept to pull data from CKAN. Chris will follow up with them on it on the next technical call.
- Brock will be in NYC next week on the local reporting platforms. SNSN Data Day at Columbia University
- IODC is coming up next week with a pre-event on SDG reporting and open data and interoperability and an conference event on SDG reporting
- More technical calls in the mornings before these calls
- Brock will work with Chris to test out the multilingual and Jekyl portions of the site
- Angela will review the French translation sheet
1. The multilingual proposal
https://github.com/brockfanning/sdg-translations
US platform has English and Spanish and will soon have French. Jekyll plug-in pulls in all these files as data. Countries can overwrite and store a local version if don’t want to use the central version. Could consider inheritance – eg English largely the same but may be some US and UK differences. Need to consider how the permissions would work and how versions would be controlled – use open standard versioning?
Have changed templates within Jekyll to avoid hard coded reference to the various elements.
Role required for how keep this updated from central UNSD re any changes to naming etc. Could store global metadata in this repository?
Current UK repository stores stuff locally so would change to point to something central.
2. The Jekyll theme proposal
Will be easier long term to get changes delivered to countries or for countries to customise. Without using themes, if through customisations the original and forked versions diverge, then harder to pull down code and changes in future (github conflicts!) but this way means a shared resource regardless of version or customisations.
Uses Jekyll ‘remote theme’ – a plug-in. Brock sees only potential downside is if would cause any issues with other plug-ins – aim for community support if this occurs.
To note US uses CircleCI not TravisCI
Action: Brock to find out why GSA using CircleCI, so we’re aware in case other countries ask re CircleCI vs TravisCI
3. Next steps for testing (and timescales to suit international partners)
UK to create copy of repository and Brock could do pull request to put the code in.
Action: Chris to liaise with Brock re repository link for code to be added to.
4. Mapping tool
Brock – aim to have as little code as possible in the local versions so avoid putting in local repo. Briefly discussed option for putting in a shared space – similar to multilingual options. To be discussed further. UK looking to pull in contractor resource to develop the mapping template eg so usesdata format in platform.
5. Architecture diagram
We’ll share Doug’s diagram.
6. Guidance re hosting
Brock working on guidance re hosting on amazon web services. Future version could be how to host on other cloud services.
7. How the builds work
Need to force build to push through metadata changes, any issues that sdg-indicators automatically build every 24 hours.
Brock previously explored getting something to force a build of sdg-indicators when sdg-data updated but has not implemented. Chris will be exploring how the automated builds are controlled.
8. Changes to reporting status and RAG progress display
UK are exploring removing the current RAG colours from the reporting status page. This would then reserve these colours for assessment of progress towards the goals/targets/indicators. Rwanda also specifically requested removing the currently used RAG colours.
9. Future meetings
Agreed helpful to have these longer additional discussions about technical issues. Will trial having fortnightly catchups on a Friday, in advance of the wider fortnightly US/Uk catchup. Action: Ann to set up further meetings