Statista as a data source...

Note, I generally do not approve of the use of Statista as a data source. Statista is a data aggregator, not a primary source. It may be useful for identifying useful original sources but I do not regard it as an original source. 

To check if UCD has campus access (Campus License International).
Click on Login and select Campus Access, you then select "University College Dublin" from the box <Select your University>. Statista then logs you in automatically.

<from Statista's website>

On Campus
When you are on campus, and within the university network, https://www.statista.com/ will be available through an automated IP-activation which requires no further logging in.
Off Campus
If you want to have access to Statista off campus, from home, or a cafe, you can use Shibboleth Access or EZ Proxy. 

https://www.statista.com/login/campus/

Use the dropdown box to check if your campus has Shibboleth Access:

DataCamp Projects

Complete the following learning goal "Introduction to DataCamp Projects".

This short introduction to DataCamp projects introduces you to Jupyter Notebooks. Notebooks are widely used and are a really handy way of playing with data, for organising and presenting research.

If you cannot find this activity, navigate via "Learn" > Projects > Introduction to DataCamp Projects (screenshot below).

Navigate to "Introduction to DataCamp Projects"

Group podcast activity

Sign-up to the "Peer Group Code of Conduct" (copies distributed in-class). You can also use this to record participation as needed.

The basics

To host a 20-40 minute podcast you will need to:

1. Identify a guest to interview for the pod.
2. Agree the scope: 6 questions.
3. Arrange a date and time for the recording.
4. Host and capture the recording.
5. Edit and finish for the pod.
6. Custom cover art, show notes (description), and announcement text.
7. Polish the finished product and publish.

Note: Cover art requirement: "Podcast feeds contain artwork that is a minimum size of 1400 x 1400 pixels and a maximum size of 3000 x 3000 pixels, 72 dpi, in JPEG or PNG format with appropriate file extensions (.jpg, .png), and in the RGB colorspace. Aim not to exceed ~300KB size file."

In this example of a podcast cover-art file I deliberately included the dotted line as part of the art.

The live podcast format

Develop your own running order / show notes. The order of questions (and indicated responses) are merely a starting point. Include links to other material you might have referenced in the show or to point to additional content. Don't forget that the show notes will include acknowledgement for the music, images, clip art etc. (creator name url copyright/license).

The show notes / running order is merely a guide rather than a tight script and the show itself always takes its own course. Avoid reading word-for-word scripted responses - unless you have amazing voice acting skills it is nearly impossible to not to sound wooden. However the activity of preparing primes and enables you to engage nimbly with the flow of a discussion.

Your show-notes can be used to share links to online versions of visual elements, references to other material etc. For the final edited podcast, assume your audience is only able to listen to the audio file.

More tips:

What does the finished product look like?

Find inspiration in some of our other episodes on the Design Talk (dot IE) podcast.

https://shows.acast.com/design-talk/episodes

Prep and activities:

Read, amend and sign the "Peer Group Code of Conduct" when your group is formed.

You should identify a guest to invite (let me know if you have ideas) but if you can't find a guest I'll help you to source one.

Arrange and coordinate the date/time and venue.

Up to two co-hosts assigned for the interview (review previous episodes to get a sense of the format).

Everyone to keep track of time, to prompt and track engagement during the conversation and to highlight comments or themes that arise on the group chat.

Each member to create their own edit, to edit the mp3 file down to a compact lively podcast with intro/outro etc. using Audacity.

Each member to create a podcast cover art version for the episode.

This class is supported by DataCamp

datacamp: clear as data

We think DataCamp is the best platform for self-paced learning for data science skills development.

DataCamp is the most intuitive learning platform for data science and analytics. Learn any time, anywhere and become an expert in R, Python, SQL, and more. DataCamp’s learn-by-doing methodology combines short expert videos and hands-on-the-keyboard exercises to help learners retain knowledge. DataCamp offers 350+ courses by expert instructors on topics such as importing data, data visualization, and machine learning. They’re constantly expanding their curriculum to keep up with the latest technology trends and to provide the best learning experience for all skill levels. Join over 6 million learners around the world and close your skills gap.

The value of using DataCamp

The DataCamp skills self-paced training is directly relevant to digital and business in general. Employers recognise and highly value even basic python, R, Excel or general data science skills. Everyone's paths will be different and DataCamp supports different learning needs, offering support and challenges suited to both beginner and experienced learners. More importantly the data analytical tools are directly relevant to your term paper project, whether you use python, R or Excel, ultimately the DataCamp courses will help. Some projects in DataCamp may align well with your own research projects.

An introductory pathway for new starters and programming rebooters.

• The Excel Fundamentals track
• The R Programming Fundamentals track
• and many others.

Consider following one of the many guided or unguided DataCamp projects by browsing through the catalogue. For example:

• https://learn.datacamp.com/projects

A relevant example (using R) is "Visualizing Inequalities in Life Expectancy"&nbsp;

• https://learn.datacamp.com/projects/166

Some thoughts on learning using DataCamp

Taking the DataCamp learning tracks early and taking them seriously is important. The knowledge and learning you will gain will stand to you in your career, although you may never end up coding for work you will have acquired a deep appreciation for the work itself and an understanding of the concerns of the people who do and who you will interact with or manage.

"You will inevitably encounter specific learning challenges in different tracks. The programming courses (like computer programming in general) will pose challenges of syntax, logic, even spelling. Yes, coding can be extremely frustrating for us all, regardless of experience. That is why we also offer in-person tutorials. We believe that self-directed learning still needs an element of interaction with others to succeed, to help problem solve, to overcome roadblocks. We have all encountered education models where information is presented pre-configured, where the answers are provided in plain view, merely requiring extraction and mapping to solve problems, or regurgitating at the right moment of a multiple choice question. But if you find yourself stuck on a problem and unable to make progress based on the instructions. What then? The educators in DataCamp, while providing lots of scaffolding and spoon-fed problems, actually encourage, and in many cases require, the learner to go off and explore other related content and solve problems using external resources. Using "search", drawing upon and participating in online communities such as StackExchange and other sources is both appropriate and commended. Not for copy-and-paste-code, but for phrasing the problem, following dialogue, engaging in conversation. Over time you will find yourself emboldened to take an active part in these communities, supporting others as they struggle problems like those you eventually overcame."

Case Based Learning CRIB Sheet

A process view for organising case based learning (aka problem based learning); to formulate self-defined and self-directed learning goals.  Cases can be analysed at progressively deeper levels, from simple to more complex and/or subtle analysis as you become adept at this approach to learning.

With respect to the cases, you will get out as much as you put in. Consider using the following process and prompts.

• Case analysis process guide:
• Read the case
• Identify what you already know about a topic. 
• Develop a list of potential problems evident in the case.
• State learning gaps then resolve them by finding and reading-up relevant material.
• Summarise your findings and ideas.
• Generate a synthesis.
• Present a single page capturing the above (homework).
• Retrospective (reflect on the process).
• Case analysis self-question prompts:
• Are there topics/objects in the case you need to know more about?
• Do you have applicable prior learning and experience you can bring in?
• Did the case raise questions for you? How did you answer the questions?
• Is information presented that you do not understand? Avoid highlighting non-specific generalised experience/skill gaps that you cannot address through independent research and learning.
• How did you resolve your personal knowledge gap(s)?
• Our intention is for you to show that you started to address the knowledge gap here. So, what did you learn?  
• Any general benefit? Is the case applicable to inform future practice?
• Are your recommendations, prescriptions, statements or claims justifiable?

Writing a precis

The commentary or précis of a reading/article conveys what you learnt and how you might employ the knowledge. In addition you can employ a critical or analytical interpretation, i.e. what is the intention of the authors, who is the audience, how valid are the claims?

Patterns for a basic précis:

• Sentence 1:Name of author, genre, and title of work, date in parenthesis; a rhetorically accurate verb (such as "claims," "argues," "asserts," "suggests"); and a THAT clause containing the major assertion or thesis statement in the work. 
• Sentence 2: An explanation of HOW the author develops and supports the thesis, usually in chronological order. 
• Sentence 3: A statement of the author's apparent purpose, followed by an "in order to" phrase. 
• Sentence 4: A significant quote from the paper used in a sentence.

Focus on the article being reviewed, not so much on other readings, books, articles etc.

Please do identify key quotes from the article. These a short statements or at most a sentence or two that distill some essential aspect of the article. A key quote is used: to point to the authors' evidence or claims; to make a justification for your own arguments; to act as a foundation for your own ideas. However, there must be clear delineation between the authors' content and your use of it therefore.

• For quotes: use quotation marks followed by cite.
• For paraphrasing: follow with cite.
• For extracts and transformations like lists and tables: explain source followed by cite.
• When reviewing, do not quote the author's quotes of other authors. Instead, quote an original passage written by the author of the article you are reviewing.

Please use double quotation marks and page number to identify "the quoted text" p. 23. You could apply one of the standard citation methods if you like e.g. Harvard style:

• (Surname et al., Publication Year, p.#)
• (Surname et al., Publication Year, pp.#-range)

Something like "some text" (AuthorSurname et al, 2033, p.7), or similar according to the citation standard required for the document.

Using problem-based cases for self-directed learning

TLDR? Apply the following response structure for case analysis. The 6 points represent the milestones of the skills and developmental process for problem based learning: analytical, self-audit, self-critique, self-plan, synthesis, closure.

Process as follows:

1. Identify up to three (max) challenges/problems evident in this case.
2. State knowledge/skills you currently possess relevant to these challenges/problems.
3. Identify up to three (max) personal knowledge gaps related to any aspect of this case.
4. Provide evidence of key learning sources you identified to address your personal knowledge gaps.
5. Propose strategic/remedial actions that may address the three (max) challenges/problems evident in this case.

Structure for a learning process centred on case studies.

How do you read a case and engage with it as a problem-based learning exercise for self-directed learning?

When a learner asks "why?" Often the last thing they want or need is for the answer to be given to them. What we as teachers should enable, is not to provide answers to questions, but to facilitate learning through personal discovery. So when someone asks "why?", a good answer might be "I don't know, but I think I might know how to start the process of finding an answer".

Let's say you are reading a case study but you aren't sure how to deal with it. On the one hand perhaps the case study presents basic statements as facts, or perhaps the case presents so much rich context that it is difficult to see the underlying challenges. It is confusing. Sometimes the problems are well sign-posted, sometimes not. PBL, problem-based cases and self-directed learning offer a way to personalise your own learning, encouraging you to explore, extrapolate and investigate wider issues under your own initiative, an investigation that addresses your personal knowledge-gaps and enables you to further your own learning objectives.

One of the goals of case based learning is to have readers react, question, go out and research, and eventually recommend some change or solution. But crucially, the reader should be looking at the challenges 'in general', the wider issues affecting similar initiatives in today's environment. Furthermore recommendations will be based on research, readings, applicable theory, and evidence; usually evidence you will have gathered yourself (aka research).

Consider case analysis as a process in which the learner poses or structures the problem, explores and shapes solutions to the problem. A reflective turn on the "case as a process" raises the circumstance where the "problems" that the case raises can be construed as personal knowledge gaps. Problem solving drives the underlying personal process of learning.

In order to put some shape on this as a process consider the following "moves":

• Diagnose: Identify the problems(s)
• Discover: Independently research the problem area(s)
• Develop: Propose a response or responses, recommendations to resolve, improve etc.

Remember that recommendations and resolutions based on abstract rules will not necessarily fit actual situations therefore 'expert', rather than simply proficient, determinations will account for both the general issues and those that are context dependent.


The method: in brief.

1. Quickly 'first read' the case/paper/whatever. You will skip some sentences and words. The goal is to read the whole thing in a single sitting, without taking notes, just to get the first impression.

2. After the 'first read' write a sentence or paragraph from memory. This is your initial impression after first reading. Don't go back to re-read parts or seek clarity yet.

3. 'Second read' is also quick but you now underline/circle or write a list of concepts, jargon, terms, identities that are new or confuse, or are unknown to you. These are your personal knowledge gaps. Some of these you will resolve during homework time.

4. 'Third read' you can focus on sections or impressions; come up with a minimum of at least 3 initial diagnosis (continue during homework time). Encourage a variety of analyses, otherwise everyone focuses on perhaps one big superficial criticism like 'the business strategy is broken for these reasons and needs to change'.

5. Homework, self-directed and self-paced learning; address the personal knowledge gaps, work on diagnosis, work on prescribing more than one potential remedy to the problems.

The following are similar structured processes for reading and case analysis. You will probably have your own approach or adapt and modify the steps to suit the your own style and conditions.

Schwartz et al. (2001) outline a typical sequence of learning-centred activities for case analysis.

• First encounter a problem ‘cold’, without doing any preparatory study in the area of the problem.
• Interact with each other to explore their existing knowledge as it relates to the problem.
• Form and test hypotheses about the underlying mechanisms that might account for the problem (up to their current levels of knowledge).
• Identify further knowledge gaps or learning needs for making progress with the problem.
• Undertake self-study between group meetings group to satisfy identified learning needs.
• Return to the group to integrate the newly gained knowledge and apply it to the problem.
• Repeat steps 3 to 6 as necessary.
• Reflect on the process and on the content that has been learnt.

The Seven Jump or Maastricht process offers a similar template for structuring small-group case learning (Grave et al., 1996).

• Clarify unknown terms or concepts in the problem description.
• Define the problem(s). List the phenomena or events to be explained.
• Analyse the problem(s). Step 1. Brainstorm. Try to produce as many different explanations for the phenomena as you [can] think of. Use prior knowledge and common sense.
• Analyse the problem(s). Step 2. Discuss. Criticize the explanations proposed and try to produce a coherent description of the processes that, according to what you think, underlie the phenomena or events.
• Formulate learning issues for self-directed learning.
• Fill the gaps in your knowledge through self-study.
• Share your findings with your group and try to integrate the knowledge acquired into a comprehensive explanation for the phenomena or events. Check whether you know enough now.

The MacMaster ‘triple jump’ describes three main stages for student-driven problem investigation: initial analysis, independent research, and synthesis. Each stage consists of a series of activities (not necessarily taking place in sequence).

• Initial analysis: identify problems, explore extant knowledge, hypothesise, identify knowledge gaps
• Independent research: research knowledge gaps
• Synthesis: present findings – relating them to the problem(s), integrate learning from others, generate a synthesis, self-assessment of learning process, repeat ‘triple jump’ if needed.

You can also try one or more of the following methods to capture and order your analyses, diagnoses, recommendations etc.

Discover the issues...

• Create an Empathy Map (from a key actor's perspective: the person, what they see, say, do, feel, hear, think)
• Brainstorm
• Anti-problem (state the antithesis to the problem and resolve it)
• Context Map (depict rich context)
• History Map (depict the past)
• Low-Tech Social Network (sketch relationships between actors)
• Storycard the Problem(s)
• Draw the Problem(s) (graphical system depiction or representation)

Having identified problems...

• Stakeholder Analysis
• The 4 Cs or the 4 Ds or the 5 Whys (components, characteristics, challenges, characters; or discover, design, damage, deliver; or ask why 5 times)
• The SQUID (sequential question and insight diagram)
• Root cause analysis (cause-reason fishbone diagram)

References:

• GRAVE, W. S., BOSHUIZEN, H. P. A. & SCHMIDT, H. G. (1996) Problem based learning: Cognitive and metacognitive processes during problem analysis. Instructional Science, 24, 321-341.
• SCHWARTZ, P., MENNIN, S. & WEBB, G. (Eds.) (2001) Problem-Based Learning: Case studies, experience and practice, London, Routledge.