{dojo-tabs:theme=tundra}
{dojo-tab:title=Brief|selected=true}
| Title: | Scientific and Technical Publications Requirements |
| Publication date: | 5/7/2012 |
| Effective date: | 3/7/2011 |
h2. BRIEF
h3. Policy Summary
This policy describes Berkeley Lab requirements for the publication of scientific and technical information (STI).
h3. Who Should Read This Policy
Employees and affiliates involved in scientific or technical research
h3. To Read the Full Policy, Go To:
The POLICY tab on this wiki page
h3. Contact Information
Information Technology Policy Manager
Information Technology Division
[[email protected]|mailto:[email protected]]
{dojo-tab}
{dojo-tab:title=Policy}
| Title: | Scientific and Technical Publication Requirements |
| Publication date: | 5/7/2012 \\ |
| Effective date: | 3/7/2011 |
[D. Policy Statement|#_D._Policy_Statement]
[D.1 Publication Submission Requirement|#_D.1_Publication_Submission]
[D.2 Credit Line, Author Affiliations, Copyright Notice, and Disclaimer Requirements|#_D.2_Credit_Line,]
h2. POLICY
h3. A. Purpose
This policy establishes requirements that help to ensure:
* Open access to research conducted at Lawrence Berkeley National Laboratory (Berkeley Lab) and to encourage wide dissemination of research results
* Adherence to copyright obligations in the publication of research results
* The appropriate assignment of intellectual property rights
h3. B. Persons Affected
This policy applies to employees and affiliates involved in the creation of scientific and technical information.
h3. C. Exceptions
The scope of this policy is scientific and technical information (STI) created in the course of research. It does not include all other Laboratory Information.
{anchor:_D._Policy_Statement}
h3. D. Policy Statement
{anchor:_D.1_Publication_Submission}
h4. D.1 Publication Submission Requirement
# *Purpose.* The purpose of the publication submission requirement is to:
## Ensure that STI funded by the U.S. government or conducted at facilities funded by the U.S. government is made available for public access
## Review STI to ensure that copyright obligations are met
## Review STI for potential patents or other intellectual property
# *Requirement.* Authors must submit STI to the [Report Coordination Office|https://commons.lbl.gov/display/rst/Report+Coordination].
{anchor: Card |
---|
| Title: | Scientific and Technical Publication Requirements | Publication date: | 8/9/2024 | Effective date: | 3/7/2011 |
POLICYA. PurposeThis policy establishes requirements that help to ensure: - Open access to research conducted at Lawrence Berkeley National Laboratory (Berkeley Lab) and to encourage wide dissemination of research results
- Adherence to copyright obligations in the publication of research results
- The appropriate assignment of intellectual property rights
B. Persons AffectedThis policy applies to employees and affiliates involved in the creation of scientific and technical information. C. ExceptionsThe scope of this policy is scientific and technical information (STI) created in the course of research. It does not include all other Laboratory Information. Anchor |
---|
| _D._Policy_Statement |
---|
| _D._Policy_Statement |
---|
|
D. Policy Statement Anchor |
---|
| _D.1_Publication_Submission |
---|
| _D.1_Publication_Submission |
---|
|
D.1 Publication Submission Requirement- Purpose. The purpose of the publication submission requirement is to:
- Ensure that STI funded by the U.S. government or conducted at facilities funded by the U.S. government is made available for public access
- Review STI to ensure that copyright obligations are met
- Review STI for potential patents or other intellectual property
- Requirement. Authors must submit STI to the Publications Office.
| }
h4.
#
# * *
##
##
# * *
# **
##
# * *
##
h3.
h3.
| *Term* | *Definition* |
| Scientific and Technical Information (STI) | Information products deemed by the originator to be useful beyond the originating site Term | Definition | Scientific and Technical Information (STI) | Information products deemed by the originator to be useful beyond the originating site (i.e., |
| \\ |
h3.
None
h3.
None
h3.
[|mailto:[email protected]]
h3.
| *Date* | *Revision* | *By whom* | *Revision Description* | *Date | Revision | By whom | Revision Description | Section(s) |
| * | * Type* |
| Type | 8/9/2024 | 1 | A. Sultan | Periodic review: no changes | All | Editorial | 6/15/2021 | 1 | A. Sultan | Periodic review. Minor formatting. No changes. | All | Editorial | 12/17/2020 | 1 | D. Soustin | Updated Contract 31 I clause numbers as per mod 1105 | Source Requirement Documents | Editorial | 5/7/2012 |
| | 1 | | | All | Minor Change |
| | 0 | | | All | Minor Change |
{dojo-tab}
{dojo-tab:title=Document Information}
h2. DOCUMENT INFORMATION
| Title: | Scientific and Technical Publications Requirements |
| Document number | Card |
---|
label | Document Information |
---|
| Title: | Scientific and Technical Publications Requirements | Document number | 10.02.001.000 |
| |
| | 1 |
| Publication date: | 5/7/2012 |
| Effective date: | | 1 | Publication date: | 8/9/2024 | Effective date: | 3/7/2011 |
| |
| | 3/7/2015 |
| Policy Area: | Scientific and Technical Publications |
| RPM Section (home) | Information Management |
| RPM Section | 8/8/2027 | Policy Area: | Scientific and Technical Publications | RPM Section (home) | Information Management | RPM Section (cross-reference) |
| | |
| | |
| | |
h3. Source Requirements Documents
* DOE O Source Requirements Documents | _ {_}t
* Contract 91 - DEAR 970. _ _ (Deviation JUL 2006) Section d.2.
** Requires copyright notice
* {color:#222222}Berkeley Lab Senior Management requirement{color}\*\* Requires disclaimer
h3. Implementing Documents
None
{dojo-tab}
{builder-show:group=rpm2-admins}
{dojo-tab:title=Additional Information}
h2.ADDITIONAL INFORMATION
|Title: |Scientific and Technical Publications Requirements|
|Document number|Implementing DocumentsNone |
Show If |
---|
| Card |
---|
label | Additional Information |
---|
| Title: | Scientific and Technical Publications Requirements | Document number | 10.02.001.000 |
|
| |
| ||
| |5/7/2012|
|Effective date: | | 8/9/2024 | Effective date: | 3/7/2011 |
|
| |
| |37/2015|
|Policy | |
| | |
| | |
| | |
| | Bonaguro|
| | |
|Revision 0 publication date|Bonaguro |
|
| Revision 0 publication date | 3/7/2011 |
|
| |
| ||
| | |
| | |
|Inputs from more than one Functional Area?|No|
|List additional Functional Areas & contacts| |
| | |
|Inputs from more than one Policy Area?|No|
|List additional Policy Areas & contacts| |
| | |
|30-day notification needed?|No|
|30-day start date|n/a|
|30-day end date|n/a|
| | |
|LDAP protected?|No|
| | |
|Need TABL reminders?|No|
|Frequency|n/a|
|Brief reminder text:|n/a|
| | |
|Approval Sheet for this revision received (date) \\
\[Note: author is responsible\}| |
h3.Key labels/tags:
* Scientific and Technical Publications, Information Management
h3.New terms that need to be added to Glossary/Acronym list:***
* Policy Area: Information Technology
h3.Implementing Documents restricted to department/functional use
(optional – these will be used for tracing between requirements and associated documents)
|Document number|Title|
| | |
| | |
\\
\\
*Side bars:*
Side bar 1 location (cite by Policy Section # - for example: Section D.2.a)
Sidebar 1 text:
\\
Sidebar 2 location
Sidebar 2 text:
\\
Sidebar 3 location
Sidebar 3 text:
{dojo-tab}
{builder-show}
{dojo-tabs} |
|
| Inputs from more than one Functional Area? | No | List additional Functional Areas & contacts |
|
|
| Inputs from more than one Policy Area? | No | List additional Policy Areas & contacts |
|
|
| 30-day notification needed? | No | 30-day start date | n/a | 30-day end date | n/a |
|
| LDAP protected? | No |
|
| Need TABL reminders? | No | Frequency | n/a | Brief reminder text: | n/a |
|
| Approval Sheet for this revision received (date) [Note: author is responsible} |
|
- Scientific and Technical Publications, Information Management
New terms that need to be added to Glossary/Acronym list:***- Policy Area: Information Technology
Implementing Documents restricted to department/functional use(optional – these will be used for tracing between requirements and associated documents)
Side bars: Side bar 1 location (cite by Policy Section # - for example: Section D.2.a) Sidebar 1 text: Sidebar 2 location Sidebar 2 text: Sidebar 3 location Sidebar 3 text:
|
|
|