Below are changes to make to the webpage. I've typed it out as requested so you can copy and paste.
Change the suggested gray text in the Investigators boxes from “Dr. Sally Shares” to “Sally Shares”. Please do this for all of the pages, so: Project Investigator(s), Dataset Contributor(s), Code Contributor(s), Codebook Author(s), Document Author(s)).
Project Investigator(s)
Enter the first and last names of the investigators who should get credit for this project and be part of the citation. Do not add titles or degrees to the names. Investigators may or may not include named personnel on funded grants, but likely include those who contributed significantly to the project. Add investigators in the order appropriate for citing this project.
(might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Note: None of the investigators listed here will be given administrative rights [have the words “administrative rights” link to FAQs and auto scroll to “Can I allow others..”), open in a separate window so they do not lose their project creation] to this project. Giving administrative rights, which allows others to manage this project’s metadata and data, is a separate step that happens after the project is saved. (this might be changed after 11/2/24 meeting with dev team)
Dataset Contributor(s)
Enter the first and last names of the people who should get credit for this dataset and be part of the citation. Do not add titles or degrees to the names. Contributors may or may not include named personnel on funded grants, but likely include those who contributed significantly to the dataset. Dataset contributors can be different from Project Investigators. Add contributors in the order appropriate for citing this dataset.
(might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Code Contributor(s)
Enter the first and last names of the people who should get credit for this code and be part of the citation. Do not add titles or degrees to the names. Contributors may or may not include named personnel on funded grants, but likely include those who put the code together. Code contributors can be different from project investigators and dataset contributors. Add contributors in the order appropriate for citing this code.
(might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Codebook Author(s)
Enter the first and last names of the people who should get credit for this codebook and be part of the citation. Do not add titles or degrees to the names. Authors may or may not include named personnel on funded grants, but likely include those who put the codebook together. Add authors in the order appropriate for citing this codebook.
(might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Document Author(s)
Enter the first and last names of the people who should get credit for these materials and be part of the citation. Do not add titles or degrees to the names. Authors may or may not include named personnel on funded grants, but likely include those who put the materials together. Add authors in the order appropriate for citing this material.
(might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
FAQ page
Can I allow others to manage my data?
Yes! In fact, it is a best practice to allow more than one person to manage your LDbase data. Use the “Manage Members” button on your main Project page to assign registered LDbase users to your project management team. We have two roles available: a Project Administrator and a Project Editor. You can assign as many people as you’d like to each role. These assignments are per project. If you have multiple projects in LDbase, your project administrators and project editors will not be able to alter your other projects.
What is a Project Administrator?
You become the project administrator when you create a Project in LDbase. Additional project administrators can be added by any current project administrator via your "Edit Project" page. It is a best practice to add more than one Project Administrator to a project, so that project management can be handled by someone else in case one person is unavailable. A project administrator has the highest level of access to a project and its contents. They can:
• Add/Edit all project metadata
• Upload product to the project (datasets, codebooks, code, and documents)
• Approve exempt access to certain users for any product you have embargoed
• Access/Edit embargoed products
• Add/Remove Project Editors and other Project Administrators
• Delete the project completely from LDbase
Manage Administrators webpage.
Where it says “This is where you can add/remove LDbase users who have the ability to edit your project's pages and data. There are two roles available.”
Change to: “This is where you can add/remove LDbase users who have the ability to edit this Project’s pages, metadata and data. It is a best practice to have more than one project administrator on each project so that project management can be handled effectively in case one person is unavailable. You can add and/or remove users at any time. There are two types of project management roles available.”
"Reset your password” webpage
Password reset instructions will be sent to your registered email address. If you cannot access your registered email (e.g., you have moved institutions), then please do not start a new account and instead email LDbase@fcrr.org for assistance.
Create/Edit/Update webpages (I'll send you this exact text when the team makes decision, Brian):
Project Name
Enter the name of your project. This will help people identify your project on LDbase. It is also the exact text that will be used in the citation of your project when people use the “Get Citation” link.
(might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Below are changes to make to the webpage. I've typed it out as requested so you can copy and paste.
Change the suggested gray text in the Investigators boxes from “Dr. Sally Shares” to “Sally Shares”. Please do this for all of the pages, so: Project Investigator(s), Dataset Contributor(s), Code Contributor(s), Codebook Author(s), Document Author(s)).
Project Investigator(s) Enter the first and last names of the investigators who should get credit for this project and be part of the citation. Do not add titles or degrees to the names. Investigators may or may not include named personnel on funded grants, but likely include those who contributed significantly to the project. Add investigators in the order appropriate for citing this project. (might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting) Note: None of the investigators listed here will be given administrative rights [have the words “administrative rights” link to FAQs and auto scroll to “Can I allow others..”), open in a separate window so they do not lose their project creation] to this project. Giving administrative rights, which allows others to manage this project’s metadata and data, is a separate step that happens after the project is saved. (this might be changed after 11/2/24 meeting with dev team)
Dataset Contributor(s) Enter the first and last names of the people who should get credit for this dataset and be part of the citation. Do not add titles or degrees to the names. Contributors may or may not include named personnel on funded grants, but likely include those who contributed significantly to the dataset. Dataset contributors can be different from Project Investigators. Add contributors in the order appropriate for citing this dataset. (might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Code Contributor(s) Enter the first and last names of the people who should get credit for this code and be part of the citation. Do not add titles or degrees to the names. Contributors may or may not include named personnel on funded grants, but likely include those who put the code together. Code contributors can be different from project investigators and dataset contributors. Add contributors in the order appropriate for citing this code. (might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Codebook Author(s) Enter the first and last names of the people who should get credit for this codebook and be part of the citation. Do not add titles or degrees to the names. Authors may or may not include named personnel on funded grants, but likely include those who put the codebook together. Add authors in the order appropriate for citing this codebook. (might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Document Author(s) Enter the first and last names of the people who should get credit for these materials and be part of the citation. Do not add titles or degrees to the names. Authors may or may not include named personnel on funded grants, but likely include those who put the materials together. Add authors in the order appropriate for citing this material. (might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
FAQ page Can I allow others to manage my data? Yes! In fact, it is a best practice to allow more than one person to manage your LDbase data. Use the “Manage Members” button on your main Project page to assign registered LDbase users to your project management team. We have two roles available: a Project Administrator and a Project Editor. You can assign as many people as you’d like to each role. These assignments are per project. If you have multiple projects in LDbase, your project administrators and project editors will not be able to alter your other projects.
What is a Project Administrator? You become the project administrator when you create a Project in LDbase. Additional project administrators can be added by any current project administrator via your "Edit Project" page. It is a best practice to add more than one Project Administrator to a project, so that project management can be handled by someone else in case one person is unavailable. A project administrator has the highest level of access to a project and its contents. They can: • Add/Edit all project metadata • Upload product to the project (datasets, codebooks, code, and documents) • Approve exempt access to certain users for any product you have embargoed • Access/Edit embargoed products • Add/Remove Project Editors and other Project Administrators • Delete the project completely from LDbase
Manage Administrators webpage. Where it says “This is where you can add/remove LDbase users who have the ability to edit your project's pages and data. There are two roles available.” Change to: “This is where you can add/remove LDbase users who have the ability to edit this Project’s pages, metadata and data. It is a best practice to have more than one project administrator on each project so that project management can be handled effectively in case one person is unavailable. You can add and/or remove users at any time. There are two types of project management roles available.”
"Reset your password” webpage Password reset instructions will be sent to your registered email address. If you cannot access your registered email (e.g., you have moved institutions), then please do not start a new account and instead email LDbase@fcrr.org for assistance.
Create/Edit/Update webpages (I'll send you this exact text when the team makes decision, Brian): Project Name Enter the name of your project. This will help people identify your project on LDbase. It is also the exact text that will be used in the citation of your project when people use the “Get Citation” link. (might add one more sentence here about viewing the citation to this project? will be determined in 11/4/24 team meeting)
Dataset Name
Code Name
Codebook Name
Document Name