Introductions to Katie who's doing six week internship with Becca working on DataSHIELD
- DataSHIELD conference
-
General update:
25 people are signed up. Plans to extend deadline depending on caterers etc.
Becca, Christina and Andrei have discussed programme and drawn up a draft programme. This will be finalised on Thursday during the conference planning meeting.
Everything has been booked and activities planned.
-
Anything we need to do?
Community update session at conference - Angela will give; we will discuss the presentation at next Comms meeting
Put some feelers out who will host next year - Becca will contact Mark Ibberson to see if his group are still willing to host next year's meeting
Advertising
-
Update on workshops (beginners, advanced also now deployer webinar)
Everyone who delivered the workshop last year has been invited to deliver it this year.
Xavier will be delivering the advanced workshop (and his expenses covered - Bonn team have received additional funding from their University).
There are a few developers that could be approached to contribute to the advanced session - discuss at Steering group meeting.
- Update on website (Becca)
- new website: building slowly
Becca has started sketching out the structure for the new website (about, history, team, for analysis, for data custodians, for developers, portfolio, sections for different consortia). Most of the content is on the old website, so large part will be transferring information.
- Describe what Katie has been up to re PUMA - findings of most published/most cited consortia
Linking to published papers - developing a tool to identify published papers, including consortia and studies involved, country etc. - Need to decide where this will sit. Incorporate a section on the website where researchers can report their published paper (DOI)
- Decide some initial usercases each take one to write up. structure?
For each consortium (or user case), incorporate presentations from key people involved (e.g. data managers, analysts, project managers). Who to contact from each consortia?
- DataSHIELD data nodes map - will be developed in PUMA and will come from content of publications - Who should be given edit rights for the website - discuss at next Comms meeting
- Profiles - should be moved to the wiki as this is tech documentation. profiles on the website
- Anything else?
- LinkedIn
- People have started tagging DataSHIELD in their posts.
- What are we going to post on the DataSHIELD page?
- What structure?
- how do we want to gather news for posts? What should we post about?
- To add to steering committee meeting tomorrow (and going forward)
- Discuss in the next meeting
- Update on software audit process for DataSHIELD packages:
https://wiki.datashield.org/en/governance/audit-process
- Update on draft risk response process:
https://wiki.datashield.org/governance/risk-response
- Opt-in mailing list for disclosures and newsletter mailing list – should we try to initiate these now in conjunction with registration for the conference?
- Joint Process Themes meeting
Juan currently busy
What will happen to education theme now that Juan is stepping down?
- Discuss at steering group meeting whether Education theme should now be bundled under Comms/Outreach with Juan stepping down - Comms theme will mostly cover coordination and advertising while the stats and infrastructure theme will do content?
- AOB?
- Becca to email Mark Ibberson re: hosting next conference
- Discuss the incorporation of the Education theme into Comms and Outreach theme
- Discuss who should be approached to also contribute to the advanced workshop
- What communications should be posted on the LinkedIn page - how should this be co-ordinated?
- Points to cover in the comms update for the conference
- Who should be given edit rights for the website - how do we manage this going forward?
- LinkedIn page - how to co-ordinate communications
- Mailing list?