-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create "project showcase" template #830
Comments
Would a section for linking the project grant/funding award be overkill? |
Don't think so, potentially helps researchers who would be interested in including an RSE get an idea of where they can find money to do so |
Good idea Neil, think that can help rationalise the process for an academic |
@tdjames1 - Should we add something like "Picture"? Think we should try to encourage a photo for the project to make it look pretty (although not all projects lend themelves to picture I guess) |
It's the second item in the original post:
|
Oh bloody hell, I checked like 3 times before posting that, sorry!! |
Only pretty pictures allowed 😉 |
Something like this? title: blah
rses: []
completed: true
start_date: 29-10-2023
end_date: 29-10-2024
image: only-pretty.png
keywords: []
dept:
pi_name:
pi_quote: none
funding_sources: []
short_summary: "Lorem ipsum odor amet, consectetuer adipiscing elit.
Tempus fusce magnis cursus vitae aliquet mattis arcu.
Eu conubia diam habitant aliquam platea sollicitudin.
Viverra auctor vivamus blandit volutpat taciti ex quam nunc.
Placerat duis porttitor, interdum donec sapien proin consequat vehicula magnis.
Vulputate amet sed convallis viverra ad vehicula."
long_decription: "Lorem ipsum odor amet, consectetuer adipiscing elit.
Porta neque sit facilisis curabitur maecenas interdum natoque donec vitae.
Turpis ad urna nascetur ridiculus enim sociosqu.
Potenti ipsum diam lectus suspendisse ligula?
Mattis tortor tincidunt primis dignissim pretium dapibus leo ultricies tortor.
Est in consectetur eleifend, habitasse fringilla id.
Luctus facilisis aenean conubia penatibus sollicitudin urna.
Alibero vivamus semper cursus ut ipsum.
Justo porttitor conubia efficitur orci curabitur tempor; class tristique varius.
Congue eros nisi non libero praesent malesuada.
Justo leo lectus; magna ac magnis integer.
Consectetur pellentesque tempor laoreet felis praesent lacus?
Nisl urna enim vel euismod habitasse a.
Libero quisque lectus dolor maecenas mattis quam malesuada.
Rhoncus consequat pulvinar mauris faucibus ultrices sit in varius."
software_link: www.example.com
publication_links: [] One yaml file for each project/case study, and then use a loop and template to populate the page? Edit: Updated with Edwin's suggestions. |
This looks excellent to me, guess RSE Involved too? And maybe a date? |
doi/publications could be useful in some cases. |
RSE(s) are a good shout. |
Space for this in the last item, set as an array in case there are multiple published works from a project. |
Both? This would give an idea of duration too. Guess it would have to support "Ongoing" or "present" too |
derp missed that, sorry |
Okay, updated the template. |
We should have a collaborate field too I think. Somewhere to put industry names, or other stakeholders :) |
Would that perhaps fall under the |
I would argue funders and stakeholders can be very different? For a lot of our work, its just working with a PI, with one source of funding. But some have multiple PIs with multiple Stakeholders who are different entities to the funder. I think its also good to celebrate collaboration with external partners |
Funder sounds like a grant, collab is a person |
person or organisation? |
Funder: grant and/or company/organisation |
Could also list PI under collaborators to reduce number of fields to fill/display. |
Should/could include:
Any other details?
The text was updated successfully, but these errors were encountered: