Daily Work Log

[Meiska12]

10/09/24

• made the group team
• collaborated with each other to get a form of confirmation going.

[Meiska12]

12/10/24

• Discussed more clauses for the contract
• Came up with a plan of action to get the contract together before Saturday and get on a call and share with Dr. Buzard and finalize by Monday evening.

[kbuzard]

@ecn310/development Make sure that someone makes a post for any work you do outside of class over the weekend. Also, going forward, please add some detail.

For instance, today I can see you created the .md file. Say that you created it, and where it's located (providing a link to the file on Github is a good idea). Often, you'll want to reference the commit; you just copy the link that's represented by 6-digit number (the SHA or hash) that's to the right of the commit message, and say something like "We created the .md file for the team contract [here](insert link) with commit https://github.com/ecn310/course-project-development/commit/44b4b3852f81f871151ab9bdc65febd18ae479d5."

Then, you can say that you started to draft it, and that you've saved that work in the .md file itself. You might state which parts are finalized, which still need revision, and which still need to be added.

[Meiska12]

Hello, Prof @kbuzard; please look at our contract's current version. Thank you, and we will be waiting for your feedback.

[kbuzard]

Hello, Prof @kbuzard; please look at our contract's current version. Thank you, and we will be waiting for your feedback.

• First, I LOVE the "Important" advisory and the "Caution" note. I've never seen that before, so you've taught me something new!
• If you want me to enforce "Step 4: If the individual's behavior does not change, the issue will be taken directly to Professor Buzard and a grade change will be determined." you need to specify how a grade would be changed, by how much, etc.
• It's not clear to me what you mean by a group in "The timekeeper keeps track of the time and has to keep track of the time allotted for each group. "
• Do you want to have any kind of enforcement around showing up at meetings, or the communications guidelines? Or only getting work done on time?

For the purposes of the grade, this already meets the standard for full credit; you may want to address my comments above to help improve the functionality of the contract, but that is up to you.

[kbuzard]

Sorry, @ecn310/development -- I forgot to tag you all on my reply to @Meiska12 and I realized I didn't know for sure whether you were all subscribed to notifications for this log. If you aren't already, I suggest that you subscribe by clicking the button in the notifications section on the right so you always know when someone else from the group posts.

[Meiska12]

Today, I added more detail about each group role and protocols to adjust them for the team contract with commit faf8637. I added the grade change description for @lirioslu and a few details to the impasse section regarding the strikes with commit 5babf58.

[filod204]

• Today we worked on: Finalizing our research question to "How has the link between manufacturing employment and economic growth evolved over time and space?", and started reading "Industrialisation as an engine of growth in developing countries, 1950–2005"
• The research question lives in the discussion section of our group.
• Next steps: We are meeting as a team tomorrow to revise the research question once again and present the section that we were supposed to read for Wednesday. Filo is reading Section 1, 4.8, Megha Section 2 and 4.7, Lucia, Section 3 and 4.6, and Sergio section 4 to 4.5, a conclusion shared.

[kbuzard]

Next steps: We are meeting as a team tomorrow to revise the research question once again and present the section that we were supposed to read for Wednesday. Filo is reading Section 1, 4.8, Megha Section 2 and 4.7, Lucia, Section 3 and 4.6, and Sergio section 4 to 4.5, a conclusion shared.

I suggest that you all read the introduction--all of the info that you need for this first, simple version of the summary is likely to be in the introduction.

[kbuzard]

The research question lives in the discussion section of our group.

@ecn310/development Sorry--forgot to tag you all on my previous comment. I also wanted to say that I don't recommend editing the research question in the post I made -- better to leave the original intact and make a reply to say how you're modifying it.

[lirioslu]

09/18/24

• Our group met up on Wednesday night to casually talk about our first article and our research.
• We didn't give anyone roles just yet, because our meeting was short and just to introduce and discuss our first article.
• We didn't fully revise the research question but came to the agreement that time and space are variables that we will change. We want to be more specific in regard to the country/countries that we will focus on, but we want to make sure that there is enough data on the country.
• We decided that for our literature review we will all write a short summary of our sections in a shared google document to have an insight on the entire paper.

[spsotelo]

09/19/24

• We were working on narrowing down specific countries for the research question however decided to leave it as is for time being; All countries
• We revised our google document that will support us with insight on the entire paper
• For next time we meet, we need to individually find a link that has data that will aid our research and corresponds to our topic

[kbuzard]

@ecn310/development Your documentation looks good so far--as it has evolved in the last few posts with the dates and additional detail. Keep up the good work!

[filod204]

09/24/24

• We discussed what could be our potential categorization method for the data in relation to our hypothesis. We will discuss further in our group meeting tomorrow, and work on the second summary, as well as revising the first

[Meiska12]

09/25/24

We got together today to assign roles for the second summary article.

• Sergio: Hypothesis for the Big question
• Megha: Citation and location
• Lucia: Big question
• Filo: Specific question

We fixed the summary of one specific question and tailored it more precisely. Also, I uploaded a summary to GitHub as a .md file.

• Getting more data related to our topic, I hope to have five sources by the end of the week.

[kbuzard]

@ecn310/development Your documentation for early in the week looks solid, but there's nothing after Wednesday. It would also be good to have a detailed log of what you discussed about the data. We're going to work on making the information about your data concrete this coming week; for now, I'd suggest starting a separate issue where you record the details of the data you're looking at, how you access it, what you're thinking about the variables / countries that are in the different datasets.

On the paper summary: we're going to further workshop these summaries on Tuesday, but the big thing to point out is that your causal diagram never made it into the summary. You're going to want to be able to see all your summaries and causal diagrams in the same place without having to flip back and forth between different locations.

[Meiska12]

We will look into rectifying most of the mentioned tasks and make the required changes.

[spsotelo]

10/3/24

• We completed a diagram for one of the summaries
• We also are meeting after today's class to work on the summaries and have a discussion about our work and current position

[kbuzard]

@ecn310/development I'm not sure what's going on here. I'm guessing that you did not meeting later on Thursday since there are no commits after 12:20 on Thursday. In this case, you documentation may be complete, but I'm worried about what I'm going to find when I look at the summaries. I will assume this is true, and someone can let me know if I'm wrong.

[Meiska12]

Added the 2nd causal diagram from the exercises repo to our summary place - ef016c8. There was a misunderstanding in the group, as we thought the person assigned to upload the latest version of our tasks would do so.

[kbuzard]

Added the 2nd causal diagram from the exercises repo to our summary place - ef016c8. There was a misunderstanding in the group, as we thought the person assigned to upload the latest version of our tasks would do so.

I just saw it--thanks! What about the first causal diagram? I still don't see it in the summary.

[Meiska12]

• 6e6f378
• I have changed the specific question, hypothesized, and added the theory in the first summary.
• The second summary slightly changes the diagram and adds the theory.

[Meiska12]

Added the 2nd causal diagram from the exercises repo to our summary place - ef016c8. There was a misunderstanding in the group, as we thought the person assigned to upload the latest version of our tasks would do so.

I just saw it--thanks! What about the first causal diagram? I still don't see it in the summary.

• So, we have a little issue, 2 other group members decided not to work over the weekend and we would like them to take accountability thus we haven't uploaded it yet. It will be updated before the class.
• we will get more articles for the summaries and remove the ones that do not make sense; thanks.

[Meiska12]

I just signed the team contract, b2856d3. I would suggest that the rest of the team do the same. @ecn310/development

• Also, I re-edited the 2nd summary link as the direct link keeps redirecting to a page that is closed and not working, so we need to go a long way to access the pdf - 749248c.

[Meiska12]

Today, I made changes to summary 7, and the only thing left to work on is the Theory section 9748e85.

[spsotelo]

10/8/24

• Today we gained valuable insight on the data we are using for our project
• We did the #6 , giving us something to talk about regarding team improvement and efficiency in the future
• We also coordinated that we would work on the data summary in pairs (Filo & I, Lucia and Megha)
• We evenly distributed both summaries and diagrams from summaries 3-7

[Meiska12]

I changed summary 7 from yesterday to a different link; however, it is still on our Google document. Instead, I worked on Summary 8 56f2f9dd77f9bbddf8448be233f26a363362ed34(it is a PDF, but the link should work); @kbuzard, please look at the link if it is okay, and also the Summary 7 link.

[kbuzard]

@kbuzard, please look at the link if it is okay, and also the Summary 7 link.

The links for both Paper 7 and 8 look good.

[Meiska12]

• f1d4549 - made changes from the given feedback, need help with the theory.
• Also, can you please look at the summary section again @kbuzard? There have been new additions.

[Meiska12]

• As a group we have updated the remaining summary charts and trying to figure out which ones are relevant to our hypothesis.
• We have divided up the data set sections to overview and we will be working on our overleaf document tonight and before Saturday.

[Meiska12]

• We all zoomed in today and discussed the sections that must be worked on for the overleaf writing. -- Lucia: 2.1 and 5 -- Megha: 2 and 6 -- Sergio: 3 and data set 2 -- Filo: 4 and Data set 2
• Summary sections have been assigned to Me (2 and 7 - f4a5460) and Filo (6).
• The whole team needs to look into the data and see what other factors could help decide on the variables and analyze the data better.

[kbuzard]

@ecn310/development I've just completed your documentation check for the week, and it looks pretty good. It would be better to have dates on your posts since Github makes it a pain to figure out when something was posted.

As the work gets more detailed, you'll need to keep making separate issues for specific tasks. I just created one for you for the data documentation. Ideally, you would have started that task when it was assigned, and then kept all the relevant details there, with just a very short summary on this log, something like "We assigned individual roles for the data documentation task on #7 (obviously the link didn't exist at the time--this is just an example.)

[lirioslu]

10/17/24

• We worked on creating an issue for our hypothesis on Github.
• As a group we decided that our research hypothesis would be regenerated with the help of our existing summaries.
• Decided that we are all proposing one working hypothesis by tomorrow.
• We also have to work on our Overleaf feedback, specifically the little errors that we made, and also review our finished summaries.

[kbuzard]

Decided that we are all proposing one working hypothesis by tomorrow.

@ecn310/development I want to point out that I can't see where this happened. It should be on the issue you created for the hypothesis.

This log is great as a summary. What you need to start doing at this point is to link to the issues where you put more details on each individual task

• I created an issue for your work on the data writeup in data.tex.
  • Here you should both record the details of your plan and then each person who works on it should summarize what they've done there.
• Similarly, you should be recording your plan and work on the paper summaries on the specific issue for the paper summaries

[filod204]

10/22/24

• We worked on a hypothesis and theory proposal
• We decided we would rework the theory and make the hypothesis more specific
• We discussed changing our meeting day and/or time but will follow up via text

[lirioslu]

10/24/24

• We worked on specifying our hypothesis.
• Adjusted out theory to the mermaid chart that Sergio did yesterday.
• Presented the work that we completed for today.
• Meeting today at 10pm to discuss the data and the variables that we will use and merge.
• https://github.com/ecn310/exercises/discussions/9#discussioncomment-11019298

[Meiska12]

I created a new issue for our team tasks. Professor Buzard has a new paper that may aid us in our discussion.

[kbuzard]

@ecn310/development For this week's documentation check: Your logs here are fine, but I can't find your do-file for accessing your data.

You need to have a task log (on an issue, probably) for your data work. I checked your data.tex file on Overleaf and didn't see any updates there in the past week. To be clear: you should be talking about who's doing what work on the data on a Github issue, and then consolidating the work product on data.tex.

• This is the key area for me to give you feedback on at this point to make sure you're ready to start testing your hypothesis.
  • You need to nail down your hypothesis before you can do any testing, but I was planning to take a look at your data to make sure it looks like it's going to be able to align with the various possibilities in your hypothesis / theory.

[Meiska12]

Tasks for over the week-end:

1. Everyone link their own issues. - Everyone
2. Making a Do-file with our data - Sergio and Filo
3. work on the feedback given in class - Lucia, Megha and Sergio

[Meiska12]

29th October, 2024

• We have assigned tasks to catch up on the remaining work
  • Sergio: Work on the Overleaf comments
  • Lucia: Work on our theory
  • Filo: Complete the Do-file instructions for accessing data
  • Megha: Add the type of each variable would be in Overleaf

We discussed these tasks for each person in class today and our group dynamics, which need to improve. Furthermore, there have been consequences for the individuals, resulting in a strike for not completing the work on time, thus affecting their grades.

[Meiska12]

Added what time of measures each of the mentioned variables would be in Overleaf- Key Variables Section.

[Meiska12]

31st Oct, 2024.

Here is the Timeline table.

• We worked on drafting deadline dates and summarizing what each section would entail.
• Setting revision dates for the work previously done.

[filod204]

31/10/24

Do file for WDI is completed, the data is reshaped and formatted appropriately for our research purposes

[kbuzard]

@ecn310/development Here's my feedback from the weekly documentation check:

1. I don't see a master documentation file anywhere--do you not have one, or did you forget to write about it and link it here?
   • I found masterdoc.md later, but it is empty.
2. You have a good start on a do file to manipulate your data; see my comments here.
3. You're making good progress on data.tex. I left some comments throughout where you can make improvements and about next steps.
4. You have a bunch of issues, but be careful not to have duplicates (I made a comment about that here). You should probably also have one for the data manipulation at this point, and for writing the master documentation file.
5. This log needs to better link to outputs (like where the theory work is, where the do file is, where the team dynamics check in is). It's missing mention of the master documentation file, which threw me for a loop.

[lirioslu]

5th November, 2024

• We have assigned tasks to each member
  • Sergio: Work on his Overleaf comments and finish Data 2
  • Lucia: Work on draft of Data section
  • Filo: Work on his Overleaf comments and replication package
  • Megha: Data part of replication package.

[filod204]

5/11/24 22:39

I worked on overleaf but need access to stata for the replication package, and will be done by tomorrow, nov. 6th afternoon.

[kbuzard]

5/11/24 22:39

I worked on overleaf but need access to stata for the replication package, and will be done by tomorrow, nov. 6th afternoon.

You can access stata from rds.syr.edu. Stata is also installed in all the public ITS computer labs, list here.

[filod204]

6/11/24 17:06

Exported reshaped dta for WDI data and uploaded it to github in the data folder renamed the Excel file to match do file

[lirioslu]

11/7/2024

• Uploaded the master documentation file https://github.com/ecn310/course-project-development/blob/main/masterdoc.md and added some steps for how to find our data.
• Worked on the descriptive statistics exercise.
• Made sure everyone knew what they had to do for tomorrow and next week https://github.com/ecn310/course-project-development/issues/13

[kbuzard]

@ecn310/development You've made a good start on the master documentation file, but it's not fully developed. Please take a look at the examples.

• For instance, it should give links to the raw data, the do file(s) to transform it, and the analysis data.
• It should link to your data.tex file, to your report file, and to your timeline and other key outputs and process documents (like your paper summaries).

Data.tex

• I've left some comments to improve and update.
• You did not integrate information about your descriptive stats into data.tex.

[lirioslu]

11/12/24

• We worked on the data section of our Overleaf. https://github.com/ecn310/course-project-development/blob/main/data.tex
• Finalized do-file for Data Set 1 https://github.com/ecn310/course-project-development/blob/main/Penn%20World%20Table%20(PWT)%20version%2010.01.do
• Made plan to meet on Wednesday and divided tasks:
• Run the correlation test.
• Write up the results and discussion draft of the paper.
• Sync the Overleaf data to github.
• Make presentation for Thursday.