rufuspollock / climate-negotiations Goto Github PK
View Code? Open in Web Editor NEWInformation on the UNFCC climate negotiations using the Earth Negotiations Bulletin from the IISD
Home Page: https://rufuspollock.github.io/climate-negotiations/
Information on the UNFCC climate negotiations using the Earth Negotiations Bulletin from the IISD
Home Page: https://rufuspollock.github.io/climate-negotiations/
Turn this repo into a website via the github pages + jekyll
Create a database of events as CSV document in /data/events.csv
Imagine this can come directly from: https://github.com/medialab/climateDebateExplorer/blob/master/ENB-data/metadata_overview/events_metadata.json
Fields:
id: # id - do not mind this being meaningful e.g. durban-2012 or something rather 001 but up to you
title: # e.g. Durban Climate Change Conference - COP17/CMP7
country:
city: # e.g. Durban - question do we need country and city separate - we could combine into place ??
date:
year: # 2012
Note:
Tommaso: I am pretty confident of this manual tagging
Tommaso: not sure that propagation has been done correctly
Tommaso: this has not been done yet, but should be
Data Model
Classifications:
id,title,actors,countries,topics,url,event_id,track,format,date,year,fulltext
Type (negotiation tracks)
Subtypes (reporting formats)
Tommaso: I am pretty confident of this manual tagging
Tommaso: not sure that propagation has been done correctly
Tommaso: This has not been done yet, but should be
As a first pass I'd suggest we store the raw text in a decent form in this repo.
SciPo already have semi-structured raw text based on scrape of ENB (perhaps with some corrections?).
I suggest we do not want to store this SciPO text but transform a bit to nice markdown and then store.
Why?
---
title:
id: # e.g. 1205000e where file was 1205000e.txt
abstract:
date:
url: # source url of ENB from which text came
---
text goes here in markdown form
I suggest we therefore get rid of the odd quasi-html structure (where is this from?) and replace with markdown:
::H1::§ § WORKING GROUP I§
::BODY::§ § Working Group I
/enb/{id}.md/
Where {id}
is the name of the original txt file minus txt.
Question: but does this make things harder later e.g. when we want to extract sections for tagging? Not sure it really does - we can parse markdown to html and then do the sectioning (the current txt structure does not really give us sections anyway ...)
Do text chunking in a sensible way.
Do we want to store chunks, and if so where?
List all ENB documents.
TODO: detail the algorithm.
Will use "annotation" following Textus terminology - http://okfnlabs.org/textus/
By structural mean that it is not about typography but about structure: sections, themes, tracks etc.
How do we want to implement?
Latter is Textus style and preferable IMO but does require us to have a reasonably stable source text. (or some way to update as we change source text).
This important, but difficult to explain - ask me if I am not clear.
Two 'granularities' are relevant when chunking the ENB reports
Generally, ENB writers
While tagging the tracks and formats (more urgent), we should therefore take into consideration only the titles followed by a new line.
When we'll move to the topic tagging (less urgent), we should to take into consideration all titles.
Hope this help
(This is easy)
A tag referring to a country or a negotiating group has been added to all sections that contained any version of the name of the country or negotiating group as present in a dictionary that I will upload in this Gith
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.