It is tgmorais1. Ok ok!

Great! What's your GitHub usr? I'll add you. Please update the overview file too (see readme in repo)

Hi all, I already finished the correspondence between v3 and v2 of exiobase, but I’m not authorize to upload in the github. Thus, I attached the file year. Meanwhile, I will also start to

Hi Michele, Like Tiago, I also opted for this group to offer my help. I added my name to the readme on github and created a pull request. I will start to work on point 2 from Chris' list.

I will start working on the point 1. -- Tiago G. Morais Instituto Superior Técnico - Universidade de Lisboa/University of Lisbon MARETEC/LARSYS Área Científica de Ambiente e Energia/Environment

1. See if there are any differences in the elementary flows lists of exiobase version 2 and 3 (even a single character difference is enough to need a mapping). 2. Map ecoinvent elementary flow list

Hi Michele, I selected to work in this group. How can I help now? I am also available to have a call Monday. -- Tiago G. Morais Instituto Superior Técnico - Universidade de Lisboa/University of

Working group self-assignment is here: https://bonsai.groups.io/g/hackathon2019/responses?pollid=4642 -- ############################ Chris Mutel Technology Assessment Group, LEA Paul Scherrer

@Chris Done. Is there anyone that subscribed to this group that is not listed as a group member right now? @All, I am working on collecting under our group repo all the info/material/guidelines we

Dear all- The call tomorrow is cancelled so that people (including me) can join the climate strike. You are welcome to send any pressing questions to me directly via email.

Dear all- It is clear that we need to update the agenda, as we have split into working groups with different competencies, and I expect these groups to stick more or less together in Barcelona. I am

Dear Brandon, Stefano, and Tomas: As I did not see much movement from your working group, I have done the following: Filled out the python library skeleton. You can see what needs to be completed

We have a good start! I added a checklist for pre-hackathon release, and added that to the hackathon planning board. Michele, please add a short working group description to the hackathon README.

I agree with Massimo; let me add a few thoughts. 1. There is no perfect schema, or at least we won't find one in the next weeks. So I think at some point it is better to have something with holes than

Thanks Brandon for setting things up so nicely - I very much recommend reading the repo readme that Brandon wrote if you haven't aready done this. We will adapt the scope of this working group as we

Great minutes, thanks for sending them and I look really much forward to next meeting. I’ll try to answer the question below: >>>GitHub repos- BEP 0003 and Deliverables:If we plan to have

After some reflection, Brandon's approach is much more sensible than mine. We would then need to either generate a preliminary vocabulary ourselves, or get one from the #ontology folks. Do we know

Thank you Miguel for starting this hashtag and thanks Chris and Brandon for the inputs. This discussion seems the right place to kick start the Group on Correspondence tables. I have just created a

Hi everyone Please find the meeting minutes in the attached document. A follow- up meeting is planned on Friday 22nd March, 9:00 AM