Show new navigation
On
Columbia Basin Fish and Wildlife Program Columbia Basin Fish and Wildlife Program
View Work Elements Available in FY:

Summary

<<
<
>
>>
Work Element 183: Produce Journal Article - Published
WE Name:
183. Produce Journal Article (Prod Scientific Rep)
Work Category:
RM & E and Data Management
WE Agreement Type:
Contracted
Status:
Active
Owner:
Definition:
The "general title/subject" of an individual manuscript should be named in the WE title. This work element should only be used when either the study is complete, or when a very significant stage of the data collection and analyses are done, and the subject matter is well defined. Separate work elements should be used for each document. If you do not have a proposed title (or subject), you may not be far enough along in the data analysis to be using this work element. This work element applies only to manuscripts being submitted for possible peer-reviewed publication. Other technical analyses should be included as part of a project progress report 132. Produce Progress (Annual) Report.
WSE Description Template:
Effective Dates:
FY2005 to <no end date>
Work Phase:
monitoring/evaluation
Sort Sequence:
12.03
Focal Species Required:
Yes
RM&E Metadata Required:
No
Finite or Recurring:
Finite
Is BPA Internal:
No
Is Contracted:
Yes
Is Cost Share:
No
Is Construction:
No


Deliverable Status:
Required
Default Deliverable Desc:
Report
Potential Deliverables:
  • (Note: Deliverables should be uploaded under attachment "Type" of Other.)
  • Manuscript
  • Journal Abstract
  • Journal Article
  • Technical Report
  • Programmatic Review

  • Rule 1 : Manuscripts submitted for peer review to a scientific journal. Use this as the deliverable as long as the writer is still in the process of seeking journal publication.

    When uploading a manuscript:

    TITLE: "Manuscript:" (then insert an abbreviated title). Example: "Manuscript: Use of scales to identify fish."

    DESCRIPTION (on the upload window): In this section, place the full title as it would appear if it was cited in the Transactions of the American Fisheries Society. For example: Manuscript: Smith, R. 1980. Use of scales to differentiate hatchery from naturally-produced, river type salmon in the Columbia River.

    VIEW PERMISSION: If you are not ready to have this manuscript visible to the public, select "Contacts only." If you want to allow public view, select "Public." Note: A manuscript a can be uploaded with permission as "Contact Only." Once the author has withdrawn the manuscript for consideration for publication, the view permission should be changed to "Public" by the author.


  • Rule 2 : Journal Abstract Used more frequently than Journal Article. Insert a publically-accessible link to the on-line abstract ,as well as the citation of the article in Word document, document (as for the Journal Article above).

    When uploading a journal abstract:

    TITLE: "Abstract:" (then insert an abbreviated title). Example "Abstract: Use of scales to identify fish."

    DESCRIPTION (on the upload window): "Abstract:" plus the citation. In this section, place the citation of the document as it would appear if it was cited in the Transactions of the American Fisheries Society. For example: Abstract: Smith, R. 1980. Use of scales to differentiate hatchery from naturally-produced, river type salmon in the Columbia River. Transactions of the American Fisheries Society 118: 112-123.

    VIEW PERMISSION: Select "Public."


  • Rule 3 : Journal Article Used infrequently because of copyright restrictions. Printed, peer-reviewed, article in a scientific journal. Use this only if an article has been accepted for publication AND you have received permission from the copyright owner to post reprints of the article. Deliverable date is the date the journal article is expected to be available to the public in the journal. Often the reprint is a PDF document distributed to the author(s) instead of hard copies.

    When uploading a journal article:

    TITLE: "Article:" (then insert an abbreviated title). Example "Article: Use of scales to identify fish."

    DESCRIPTION (on the upload window): "Article:" plus the citation. In this section, place the citation of the document as it would appear if it was cited in the Transactions of the American Fisheries Society. For example: Article: Smith, R. 1980. Use of scales to differentiate hatchery from naturally-produced, river type salmon in the Columbia River. Transactions of the American Fisheries Society 118: 112-123.

    VIEW PERMISSION: Select "Public."

    BPA encourages submission of significant scientific findings to peer-reviewed journals. However, it is recognized that not all scientists have the time or inclination to seek publication in peer-reviewed journals.


  • Rule 4 : Technical Report Report may or may not have received technical review. Technical review may be internal and/or external. A technical report may be part (chapter/section) of a larger report, including an annual or progress report. If this is the case, use 132. Produce Progress (Annual) Report.

    If the findings are based on a fairly large experiment, preparation of a technical report as a separate document is greatly encouraged to provide ease of location and citation for the public wishing to read the final results. The stand-alone nature of the final findings of an experiment may be better served as a separate document, rather than buried as part of an Annual Progress Report. BPA's preference is generally for a separate document for more significant efforts.

    When uploading a technical report:

    TITLE: "Technical Report:" (then insert an abbreviated title). Example "Technical Report: Use of scales to identify fish."

    DESCRIPTION (on the upload window): "Technical Report:" plus the citation. In this section, place the citation of the document as it would appear if it was cited in the Transactions of the American Fisheries Society. For example: Technical Report: Smith, R. 1980. Use of scales to differentiate hatchery from naturally-produced, river type salmon in the Columbia River. Transactions of the American Fisheries Society 118: 112-123.

    VIEW PERMISSION: Select "Public."

    If the findings are based on a fairly large experiment, preparation of a technical report as a separate document is greatly encouraged to provide ease of location and citation for the public wishing to read the final results. The stand-alone nature of the final findings of an experiment may be better served as a separate document, rather than buried as part of an Annual Progress Report. BPA's preference is generally for a separate document for more significant efforts.

    Example: A 3-year experiment comparing the physiological response to loading into transport trucks of fish reared in low density versus high density raceways is part of an overall larger experiment to determine differences between different densities at several stages of the life history. Although the "umbrella experiment" is not finished until the adult returns are complete, the juvenile physiology experiment has been completed. All 3 years of juvenile physiology data should be analyzed as a separate, distinct, stand-alone "report" describing the full 3 years of methods, data collection, analyses, and conclusions. A stand alone report is most desirable.

  • Rule 5 : Programmatic Review Generally provides a high-level review of goals, objectives and accomplishments of a large program over a long number of years. Intent is generally to provide scientifically-based management recommendations to aid in adaptive management. (e.g., Programmatic assessment of spring Chinook salmon hatchery production in the Hood River from 1988 to 1997).

    When uploading a programmatic review:

    TITLE: "Programmatic Review:" (then insert an abbreviated title). Example "Programmatic assessment of spring Chinook salmon hatchery production in the Hood River from 1988 to 1997."

    DESCRIPTION (on the upload window): "Programmatic Review:" plus the citation. In this section, place the citation of the document as it would appear if it was cited in the Transactions of the American Fisheries Society. For example: Programmatic Review: Smith, R. 1980. Programmatic assessment of spring Chinook salmon hatchery production in the Hood River from 1988 to 1997.

    VIEW PERMISSION: Select "Public."



Milestone Title
Type
Deliverable?
Description

Manuscript: Prepare draft
Recommended
No
[DELETE ALL MANUSCRIPT MILESTONES IF THE DOCUMENT IS NOT A MILESTONE. IF THIS MILESTONE IS RETAINED, DELETE THESE BRACKETS, AND ALL TEXT WITHIN THEM.] Draft preparation of the manuscript before significant intra-contractor technical review. Please select other standard milestones in CBFish that apply to where you are in the Manuscript process. Each separate review stage that takes a significant amount of time (a month or more) should be a milestone.
Manuscript: Internal technical review
Recommended
No
Distribute manuscript for in-house, internal technical review.
Manuscript: External technical review
Recommended
No
Review manuscript externally before sending to the journal: It may include submission to interagency cooperators, a request for technical review by posting on the BPA website, sending the manuscript to the COR for review or other such requests for technical review before submission to a peer-reviewed journal. It may also include policy review and obtaining internal or cooperator signatures internally required by the contractor. BPA does not require these signatures.
Manuscript: Request for copyright release.
Recommended
No
As part of the manuscript submission to the journal, BPA requests that all authors sign a request that would allow BPA to post the full, published article (instead of just the link to the Abstract), should the manuscript be publishable. Most journals require all authors to sign this request.
Manuscript: Submit to a journal for peer review
Recommended
No
Submit manuscript to [INSERT JOURNAL NAME HERE IF KNOW AT THE TIME OF SOW DEVELOPMENT. IF NOT KNOWN, DELETE THESE BRACKETS, AND ALL TEXT WITHIN THEM.].
Manuscript: Revise after peer review
Suggested
No
Revise manuscript after return for major revision or has not been accepted by the journal for publication. Use this until the manuscript has been formally rejected or accepted.
Manuscript: Finalize peer-reviewed article
Suggested
No
Polish manuscript: Accepted for publication with or without revisions. Includes review of gallery proofs, etc., until actual publication.
Technical Rpt: Prepare draft of Technical Report/Programmatic Review
Recommended
No
[DELETE ALL TECHNICAL REPORT MILESTONES IF NOT A TECHNICAL REPORT. DELETE THESE BRACKETS, AND ALL TEXT WITHIN THEM IF MILESTONE IS RETAINED] First draft of technical document. Please select other standard milestones that apply to where you are in the Technical Reporting process.
Tech Rpt: Submit internal technical report for review/revision
Suggested
No
Distribute technical report for contractor internal technical review by [INSERT REVIEWER NAMES HERE. DELETE THESE BRACKETS].
Tech Rpt: Solicit external review/revise report
Suggested
No
Review technical report externally by [INSERT REVIEWER NAMES HERE. DELETE THESE BRACKETS] : interagency cooperators, and/or post on the BPA website, for others to see. Signature by the cooperators' policy personnel may be required for co-authors that for multiple entities.
Tech Rpt: Revise after External Review
Suggested
No
Typically 2 months.
Tech Rpt: BPA Review
Recommended
No
Typically 1 month.
Tech Rpt: Revise after BPA review
Suggested
No
Typically 1 month.
Tech Rpt: Solicit policy review and signature by the contractor's organization
Suggested
No
Internal review by [INSERT REVIEWER NAME HERE. DELETE THESE BRACKETS]. Typically 3 months.
Tech Rpt: Upload final version of the report to CBFish
Recommended
No
Upload MS Word copy of document to CBFish. Contractor may link from their website to BPA's posting of document or post their own version on their website, but BPA must have the full document attached in CBFish (i.e., do not attach a single page with a link to contractor's website). BPA, as a public entity, does not restrict public access or invoke exclusive copyright.
Other Rpt: Prepare draft
Recommended
No
[DELETE THIS MILESTONE IF THE "OTHER REPORT" TYPE IS A MANUSCRIPT] Draft [INSERT 'OTHER' REPORT NAME HERE]. Please select other standard milestones that apply to the creation and review of the "Other Report". [EDIT THE TEXT IN BRACKETS, AND DELETE THESE BRACKETS, AND ALL TEXT WITHIN THEM.]
Other Rpt: Internal technical review of all other report types
Suggested
No
Internal review of [INSERT OTHER REPORT NAME HERE] by [INSERT REVIEWER NAMES HERE, DELETE THESE BRACKETS].
Other Rpt: External review
Suggested
No
Other Rpt: Upload to CBFish.
Recommended
No
Upload copy of [INSERT OTHER REPORT NAME HERE. DELETE THESE BRACKETS, AND ALL UNNECCESSARY TEXT WITHIN THEM] to CBFish.


5 Metrics Associated With Work Element 183: Produce Journal Article

Metric Metric Association Status Last Comment Date Last Comment By Unit Type FY Start FY End Required / Optional Is Activated By Default Included in PI Supports PCSRF/PNSHP (Katz) PNSHP Metric Code PNSHP Metric
1464: Primary R, M, and E Focal Strategy [Population Status, Hydrosystem, Tributary Habitat, Estuary/Ocean, Harvest, Hatchery, Predation, Multiple Strategies] Active RMEFocalAreaList 2022 Required Yes No No
1468: # of draft scientific reports submitted Active number 2005 Required Yes No No
1469: # of draft manuscripts and draft final reports of research findings submitted for publication Active number 2005 Required Yes No No
1495: Secondary R, M, and E Focal Strategy [Population Status, Hydrosystem, Tributary Habitat, Estuary/Ocean, Harvest, Hatchery, Predation, Multiple Strategies] Active RMEFocalAreaList 2022 Required Yes No No
1809: Manuscript Title Active text 2024 Required Yes No No

Location Requirement Type:
No Location

Applicability and status of the following environmental compliance requirements can be found on the Environmental Compliance tab for that work element in your SOW for all 2007 contracts forward. BPA's Environmental staff will update and maintain this information in CBFish in real time, so that you can check the status of environmental compliance on your project at any time.

Note: Many of the fields are set to auto-load in CBFish, but the settings will be reviewed by BPA's Environmental staff prior to the contract being finalized, and may be revised depending on the specific circumstances.

  • National Environmental Policy Act (NEPA)
    NEPA coverage for this work element will be determined by BPA's Environmental staff and could include an Environmental Impact Statement (EIS), Environmental Assessment (EA), Record of Decision to an existing EIS, or Categorical Exclusion.

  • Endangered Species Act (ESA)
    ESA consultation is typically not required for this work element.

  • National Historic Preservation Act (NHPA)
    NHPA Section 106 consultation is typically not required for this work element.

  • Public Involvement
    Public involvement is typically not required for this work element.


Reports that Use this Work Element

This work element and its metrics are used in measures in the following reports. These PDF reports are generated dynamically, always showing you the most up to date information. Most of them also have links to download the underlying data sets to structured text or Excel format.

Stats and Overview

Number of active contracts using Work Element #183 by FY

Top 5 BPA Project Managers using this Work Element:
(by number of current contracts)
Deborah Docherty (Inactive) 72
Tracy Hauser 49
Barbara Shields (Inactive) 37
Virgil Watts III 35
Martin Allen 33
Average Work Element Budget: $24,399
Average Duration: 10 months