Thursday, February 23, 2017

JRN 300: Some Updates

First, from me: in using Spartan Newsroom instead of individual news sites, we do NOT need to put bylines on top of our stories. They are automatically generated by our Wordpress account.

Next, this is from JRN 300 section coordinator Joe Grimm:


Have your students do these 5 things to make their posts work right:

1. Have them go to bio and select the proper name so we don't get anymore stories by 
​5. Please do NOT have them add tags or ​"top terms" which generate overlines and other kinds of odd things.

Wednesday, February 22, 2017

JRN 300: Examples of Final Projects

Per your request, here are some examples of final projects from past classes of mine. The topics are trend and issue stories like the ones you are doing, but generally these were the best, most ambitious topics likeliest to have the most interest and audience reach.

One big difference between a weekly story and a final project is the depth of reporting. Please note these stories have no fewer than six people quoted and/or paraphrased, along with lots of data and multiple neutral experts. 

Really, a final project is just a weekly story on steroids. An ambitious topic; lots and lots of reporting; and a deep dive into the subject matter.

For a peek, click on the links below.

Lansing's South Side struggling, but improving

Plans for express bus service in Meridian Township

"Schools of choice" in Meridian Township

Thursday, February 9, 2017

JRN 300: Patient But Persistent

Recently I received this email from one of youze:

Hey Omar,

So I have e-mailed my contacts multiple times and tried calling them, however none have picked up or responded. Should I just keep trying or wait for them to respond because I don't want to annoy them or feel like they have to give me a bs answer.

This was my response:

This is a common frustration for journalists. You should both keep trying to reach them, and at the same time start looking for backup sources to contact. The worst thing that happens in that situation is too many people get back to you, which is a good problem. It's not their job to get back to us, but it is our job to have something usable by deadline. So be polite but persistent, and seek backups immediately.

Best, Omar

That's the reality of the business. As professional journalists we aren't paid to write or shoot video or do stand-ups; that's the easy stuff. What we are paid for is solving the problem of finding relevant people to talk to and then actually getting them to talk to us before deadline.  That's the skill we need to refine here.

Is there a magic approach to get people to call you back and talk to you? No. It's very case by case, just like a first date approach with one person doesn't work with another, and it can be hard to predict what will work.

So, what we need to do is be polite but persistent with primary sources: don't just email; call them. Don't just call them; stop by their office. Don't just wait on a return call; make a follow-up call.

Then, immediately after we put out our first round of calls to primary sources; immediately identify and reach out to secondary sources. Don't wait for your primary sources to first blow you off; again, the worst thing that happens is too many people call you back before deadline, and you have a huge amount of material to choose from for your story.

It beats the hack out of the alternative: nobody calls you back, and you're staring at the clock minutes before deal dine with nothing to write.

  

Thursday, February 2, 2017

JRN 300: Examples Of Trend And Issue Stories

These are from a past JRN 300 class of mine that covered Meridian Township (which includes Okemos and Haslett in the Lansing area). Please note these stories aren't fixed on an event; rather, they are on an ongoing trend or issue that may use an event as an example or a starting point, but then delve more deeply into the issue itself.

Also please notice the range of sources, including people who are leading the issue, affected by the issue, acting upon the issue, and neutral experts who help contextualize the issue. These sorts of stories are the ones we're aiming to do off of our beats.

Examples include:
Please note these stories are not just words; they include pictures and charts and fact boxes and can also include video clips, hyperlinks to resources and such. As indicated in the syllabus, your stories are expected to include two other mediums in addition to writing (and MUSY have a photo!). So do take pictures (with people in 'em!) and look to break out a key statistic or two into a chart or graphic, for which you can use free online graphic-making tools.

The difference between a weekly story and a final project is that we report much more broadly and thoroughly on a topic we really think is the biggest trend or issue we come across. Some examples from the Meridian team include:

Please do carefully look over all these previous stories and see if it gives you a better sense of what we're aiming to do here. As always, if you have any questions or concerns please get a hold of me ASAP. It's hard for me to give you workable advice the day before something is due, since most solutions involve having to do more reporting. So don't wait until the last minute to start working on your stories! 

"I couldn't get a hold of a source" will never be an acceptable excuse, just like in the real world. That's because if there's a big story people want to know about now, we need to find sources now. The audience won't care anymore tomorrow.

Really, what journalists are paid for isn't to write or shoot or edit stories; it's to problem-solve all the things that go into having stories to put together: finding sources or backup sources, getting info in a timely manner and on deadline, etc. Those are the skills we will be practicing here.

Plus, journalists are paid to find stories that people either don't already know (and can't Google for on their own) and to answer the whys and hows about things they do notice. If all we needed to do was who-what-when-where and to restate things already easily knowable, then there would be no need for reporters: people could Google on their own for everything they need, and editors wouldn't need reporters to go out and find things if everything could be found online.

Again, these are the skills we're working on this semester. If you're not perfect the first or second time out, that's fine. Just make sure we are learning to be resourceful, hard-working, problem-solving reporters, and that we take any lessons we learn from one exercise and apply them in future exercises so we can do better the next time.

The time for us to refine these skills is now. If you wait until your first job or even your first internship, it's too late.


JRN 300: Our Publication Schedule For Tuesday/Thursday Classes

So we're about to start our out-of-class story cycles, where you will have about 7-9 days per story to go from approved idea to draft form to final version. (Keep in mind, in the real world you'd usually have 7-9 hours, max, to do the same. So this schedule does already take into consideration that you have other things going on.)

Basically, every Tuesday you will have a draft due for your latest story and the idea for your next story due before class, and in-class we'll review everyone's previous stories. And every Thursday, you'll have at least some lab time (and at times that lab time will be the whole class) to finish your latest story, which will be due by the end of class.

Here's our out-of-class story schedule for the semester for Tuesday/Thursday classes:

Story 1:
Idea due: Tue. 2/7, 8 AM to omars@msu.edu
Idea OKd: Tue. 2/7 by 6 PM
Draft due: Tue. 2/14, by 8 AM to omars@msu.edu
Draft returned: Tue. 2/14 by 6 PM
Final version due: Thu. 2/16 by end of class to WordPress
Final version posted: Fri. 2/17 by 6 PM
Review as class: Tue. 2/21

Story 2:
Idea due: Tue. 2/7, 8 AM to omars@msu.edu
Idea OKd: Tue. 2/7 by 6 PM
Draft due: Tue. 2/21, by 8 AM to omars@msu.edu
Draft returned: Tue. 2/21 by 6 PM
Final version due: Thu. 2/23 by end of class to WordPress
Final version posted: Fri. 2/24 by 6 PM
Review as class: Tue. 2/28

Story 3:
Idea due: Tue. 2/21, 8 AM to omars@msu.edu
Idea OKd: Tue. 2/21 by 6 PM
Draft due: Tue. 2/28 by 8 AM to omars@msu.edu
Draft returned: Tue. 2/28 by 6 PM
Final version due: Thu. 3/2 by end of class to WordPress
Final version posted: Fri. 3/3 by 6 PM
Review as class: Tue. 3/14

Story 4:
Idea due: Tue. 2/28, 8 AM to omars@msu.edu
Idea OKd: Tue. 2/28 by 6 PM
Draft due: Tue. 3/14 by 8 AM to omars@msu.edu
Draft returned: Tue. 3/14 by 6 PM
Final version due: Thu. 3/16 by end of class to WordPress
Final version posted: Fri. 3/17 by 6 PM
Review as class: Tue. 3/21

Story 5:
Idea due: Tue. 3/14, 8 AM to omars@msu.edu
Idea OKd: Tue. 3/14 by 6 PM
Draft due: Tue. 3/21 by 8 AM to omars@msu.edu
Draft returned: Tue. 3/21 by 6 PM
Final version due: Thu. 3/23 by end of class to WordPress
Final version posted: Fri. 3/24 by 6 PM
Review as class: Tue. 3/28

Story 6:
Idea due: Tue. 3/21, 8 AM to omars@msu.edu
Idea OKd: Tue. 3/21 by 6 PM
Draft due: Tue. 3/28 by 8 AM to omars@msu.edu
Draft returned: Tue. 3/28 by 6 PM
Final version due: Thu. 3/30 by end of class to WordPress
Final version posted: Fri. 3/31 by 6 PM
Review as class: Tue. 4/4

Story 7:
Idea due: Tue. 3/28, 8 AM to omars@msu.edu
Idea OKd: Tue. 3/28 by 6 PM
Draft due: Tue. 4/4 by 8 AM to omars@msu.edu
Draft returned: Tue. 4/4 by 6 PM
Final version due: Thu. 4/6 by end of class to WordPress
Final version posted: Fri. 4/7 by 6 PM
Review as class: Tue. 4/11

We also have our final project story, which should be your most elaborate, ambitious trend-and-issue story of the term. Please note the idea is due in late February, even though the draft isn't due until late March. That's to give you a lot of time to work on this. Please don't wait until the last minute.

Final Project:
Idea due: Tue. 2/28, 8 AM to omars@msu.edu
Idea OKd: Tue. 2/28 by 6 PM
Draft due: Tue. 3/28 by 8 AM to omars@msu.edu
Draft returned: Tue. 3/28 by 6 PM
Final version due: Thu. 4/20 by end of class to WordPress
Final version posted: Fri. 4/21 by 6 PM
Review as class: Tue. 4/25

Questions? Please ask me. And good luck, everyone!


Wednesday, February 1, 2017

JRN 300: Filing Your Story: A Style Sheet

JRN 300 STYLE SHEET

When you enter your content in WordPress, use the TEXT option, NOT the Visual option. The Visual option adds extraneous coding you do not want. You can toggle over to visual for a look (or use preview) but ENTER the content with the TEXT option.

Headlines and subheads are downstyle. Capitalize only the first word in the headline and proper nouns. Numbers should never be spelled out. Subheads are recommended in long stories. Subheads should be downstyle and bold body type.

Bylines:


By Sam Spartan

Place references: Follow AP style

Day references should include the date, as our stories live on, on the web. The day of the week is optional: "The board met at 7:30 p.m. Tuesday, Jan. 3." The year is usually not needed, as stories are time-stamped. In dates, AP style is to not use ordinal numbers such as 3rd.

Paragraphs are not indented. Simply hit return for an extra line between paragraphs.

Put the first photo with your story above the story if it is full width or to the right of the lede for maximum exposure. You’ve gone to the trouble to take a photo – show it!)

Stories continue off the home page after 3-5 paragraphs or a logical break point. Use the –more– button in WordPress. This saves readers from scrolling through long stories and gives us more headlines on the home page.

Hyperlink from names or nouns. Do not simply paste in an email address or hyperlink a phrase like "click here." A link from a noun is called a content link. Google likes them.

Example:
The contest hours are on the Happy Valley website.

Multimedia like a slide show or video needs to have a blurb of at least 150 words to explain it and to give search engines the cues they need to find it. A video posted on YouTube or Vimeo should link to our news website. The blurb goes on both locations.