Ever since the guys at JoshuaProject rolled out the new look of their spiffy new website (about 2 years ago, I’m guessing? maybe longer), we had lost the ability to physically print (or even generate a simple one-page PDF of) an unreached people group profile. Remember the good ole days when the old website would let us do that? So we finally dropped a note to the helpful staff to ask. Guess what they suggested! Look for the ROG3 country code and the Peo3 people code using the new site, then plug those values into this syntax to use the old legacy site to queue up the page you’re seeking. (You’re saying, WHAT?) Seriously. Suppose you want to print a one-page profile for the Crimean Tatar of Ukraine. First go to …



to find them. Put the name of the UPG in the search box, click the “People Groups” radio button, then hit search. This shows you a list of People Groups containing the search term you entered. Click on the people group. This will take you to a description of the UPG across countries (if the UPG is found in more than one country). The last element of the URL will be the Peo3 people code. Jot that down. In the case of the Crimean Tatar, it’s 11434. Now you need the ROG3 country code. You can find that by scrolling down the page until you see the list of countries in which this UPG is found. Click on the country. This will take you to a description of the UPG in that country (and I bet JoshuaProject someday adds a “click-to-print” button on this page, because this is the page we all grew up printing. : ) The last two letters of this URL are the ROG3 country code. Jot that down. Now use the template:




where XX is the ROG3 code and NNNNN is the Peo3 people code. In our example of the Crimean Tatars, the URL would look like this:




Try it. It’s like magic! : ) The odd thing is, as of today, there’s no direct way to come up with that super-helpful page on the new site. But give them some time. There are few services as responsive as JoshuaProject.net. : ) In the meantime, you can still get the page you were wanting using this work-around. : )