Because the certification statement is in the faculty member’s name, they must be the one who downloads it under federal law.  You can add a delegate position who helps them complete the information but they cannot log in as the PI and certify.  

Certification:

When the individual signs the certification on behalf of themselves, they are certifying that the

information is current, accurate, and complete. This includes, but is not limited to, information related

to domestic and foreign appointments and positions. Misrepresentations and/or omissions may be

subject to prosecution and liability pursuant to, but not limited to, 18 U.S.C. §§ 287, 1001, 1031 and 31

U.S.C. §§ 3729-3733 and 3802.


Certification:

When the individual signs the certification on behalf of themselves, they are certifying that the information is

current, accurate, and complete. This includes, but is not limited to, information related to current, pending, and

other support (both foreign and domestic) as defined in 42 U.S.C. §§ 6605. Misrepresentations and/or

omissions may be subject to prosecution and liability pursuant to, but not limited to, 18 U.S.C. §§ 287, 1001,

1031 and 31 U.S.C. §§ 3729- 3733 and 3802.


 

From: xxxxxx@lists.healthresearch.org <xxxxxx@lists.healthresearch.org> On Behalf Of Steve Wright
Sent: Tuesday, April 23, 2024 12:03 PM
To: Research Administration Discussion List <xxxxxx@lists.healthresearch.org>
Subject: [RESADM-L] Faculty Pushback on SciENcv for NSF Proposal

 

[This email originated from outside of OSU. Use caution with links and attachments.]

Hello everyone,

I'm reaching out for some advice regarding a faculty member's NSF proposal submission. While working with a faculty member on their proposal, I encountered some resistance regarding the use of SciENcv. The faculty member is hesitant to access and utilize the platform and has offered to share their login credentials and password so we can create the necessary documents and populate them on their behalf.

This situation raises some concerns:

  • Security: Sharing login credentials is a security risk, and it's not a practice we want to encourage.
  • Faculty Ownership: Ownership of research accomplishments is crucial. SciENcv allows faculty to control and update their information.

My question:

Has anyone else encountered similar pushback from faculty regarding SciENcv? If so, how did you address the concerns and encourage their use of the platform?

Additionally:

Does your institution have a policy in place regarding the use of SciENcv for grant proposals?

Any insights you can share would be greatly appreciated.

Steve

 

**For a direct link to log into the Cayuse Research Suite, including access to your proposal(s) within Cayuse, please visit https://isu.cayuse424.com/

Steve Wright

Senior Research Administrator-Pre Award | Office of Sponsored Programs and Support

 

Administration Building | Room 121D

921 South 8th Ave., Stop 8046 | Pocatello, ID 83209

(208) 282-2593 | xxxxxx@isu.edul

 

- = - = - = - = - = - = -

This email was sent to xxxxxx@oregonstate.edu via the Research Administrator's mailing list.

To unsubscribe from RESADM-L, go to https://lists.healthresearch.org and enter your subscribed email address into the "My account and unsubscriptions" area at the bottom of the page. This also allows you to switch to Digest Mode or to temporarily suspend emails. You will be emailed a link to change all these settings.

List archives are available at: https://lists.healthresearch.org/resadm-l