The Creation of Alaska Native Corporations

/in /by

This is the topic I have chosen, I just did not complete parts 3 & 4. Please see attachments for 3 & 4. The second case study in Theme: Thinking About History examines the creation of Alaska Native corporations and their impact on the economic development of Alaska’s Native population.

In 1968, oil was discovered at Prudhoe Bay on Alaska’s Arctic coast. To move this oil down to markets in the Lower 48* states, a consortium of oil companies proposed building the Trans-Alaska Pipeline System, which would carry the oil from Prudhoe Bay to the port of Valdez.

The pipeline would need to traverse land whose ownership was in dispute: Native land claims, many of them dating back to Alaska’s purchase in 1867, had to be settled before any pipe could be laid. That urgent economic necessity triggered one of the most innovative economic development efforts in American history.

To ensure that the pipeline would be built, Congress in 1971 passed the Alaska Native Claims Settlement Act (ANCSA), which granted Natives $963 million and up to 44 million acres of federal land, in return for ending their claims on the land where the pipeline was to be built. To administer these grants, the law set up 12 regional corporations (a 13th was added later) and more than 200 local corporations, which would develop their land and run their own businesses for the benefit of their Native shareholders.

The express goal of the corporations was to improve the economic well-being of Alaska Natives, whose living conditions were arguably the worst of any Native group in the country. To date, the corporations’ record has been mixed: some of the corporations have been highly successful, while others have performed poorly. But the use of corporations to foster Native economic development remains one of the nation’s most innovative attempts to improve the lot of Native peoples.

Draft 1 Technical Report

/in /by

### question 

Include an updated version of your outline at the beginning of the document and begin the draft of the report on a new page.  I do not expect you to turn in a 10 page paper at this point.  Approach writing the paper as suggested in the YouTube video you should view (a link to the video and an outline of this video written by someone is included above).  I am expecting to see that you made substantial progress in the body of the paper.  At this point it is not critical that you remove all grammatical errors in what you have written.  Submit a Word file.

File Name:  LastName_FirstName_Draft1.docx or .doc

Must be submitted on time to receive credit for this assignment.

IMPORTANT NOTICE:  All 4 required drafts must submitted when due.  If all the drafts are not submitted, the completed technical report (30% of semester grade) will not be accepted or graded.  Each successive draft must show substantial improvements from the previous draft. You cannot submit the same draft 4 times.

How to Write a Paper in a Weekend (By Prof. Pete Carr)

Key points:  written by a viewer of this video

1. don’t procrastinate; 

2. review the notes and renew the literature search;

3. determine who your audience is – most likely reviewers, so get their concerns firstly addressed; 

4. create the outline and get the big picture done, i.e., complete the first draft while resisting the temptation to correct and edit as you go; the logical sequence of data/tables/figures may be the outline; while writing the first draft, take notes indicating what references might be needed and would be about, but don’t stop to collect the references; 

5. begin with the easier part of the task – experimental section rather then the introduction; then follows the results and discussion section; 

6. then comes the really hard part – critical editing where you make sure that the English is coherent and the science is correct;

7. write the conclusion in a numbered format; 

8. then comes the abstract and the acknowledgements; 

9. now comes the introduction, the two most important things to address in which are the purpose and relevant background; 

10. then collect the references.

Power Point slides

An Example Template

Technical Report Requirements

You will use the format of the article from Week 1 as a guide for your paper.

Title at the top of the first page (no title page)

Use your name as the author followed by the University information.  Example on the next line

Name, Department of Computer Science and Information Systems, A&M-Commerce

Headings in the paper include the following

Abstract bold font

Keywords bold font

Introduction bold font

Other major headings as needed bold font

Subheadings as needed NO bold font

Conclusions bold font

References bold font

Other requirements

Minimum of 10 pages single spaced not including tables or figures

Times New Roman – 12 point

Standard margins 1 inch top, bottom, left and right

In text citations and reference list at the end must be in APA format

Tables must be identified as a Table with a number and title (example – Table 1 List of Parts)

Figures must be identified as a Figure with a number and title

If you did not create the table or figure you must include an in text citation so the reader can identify the source of the figure or table.

References at end must be in alphabetic order see article from Week 1 for indentation format for the complete reference.

The URLs below contain information about citing references in the text of your document, in text citation, and creating the reference list at the end of the document. Use APA format in the report for references at the end of the paper and the in text citations.  This format was used in the article in Week 1.

Read the PDF document in the DocSharing module about plagiarism, how-not-to-plagiarize developed by the University of Toronto.

Week 4 Discussion Post

/in /by

Answer W4D1 and W4D2 Separately using the text provided and article

Zeelenberg, M., & van Putten, M. (2005). The dark side of discounts: An inaction inertia perspective on the post-promotion dip. Psychology & Marketing, 22(8), 611-622. Retrieved from the ProQuest database.

Apocalypse

/in /by

 Read the attached Quantum Crypto file.  What risks does this scenario pose?  How would you address this risk?  What areas of an organization and potentially affected by a cryptographic apocalypse? What about technical concerns and so on?