KCL e-Research
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # e-Research Survey 2025 --- ## Slides --- ### Motivation 1. feedback on existing services / support 2. increase awareness 3. guide strategy development and future work 4. evidence need for growth 5. increase academic profile - Focus on feedback and future work - Awareness and outputs will happen if we do it well - Make modules relevant here core modules - Others optional? #### Outcomes we expect/want to pass up to senior leadership - Gaps in provision - are we missing things? - Free text - unknown unknowns - What do people want going forward? - Measuring what we do? - Are we doing it well? e.g. do our answers meet your needs? - Don't want to ask about time to close tickets - don't want that to be our metric - Do you want more of it? - Feedback on specific services ### Comms - RMN event on 21st/22nd May - Probably too soon at this point - Ask them to pass it on when it comes - e-Research Wednesday May block a couple of hours in the afternoon - Bring all our parts together - Review - Port to Qualtrics - Bare bones --- ### Modules - Route people through questions only for services they use / have views on --- ### Demographics Who are you? - Faculty - Career stage - Job role Discussion in the meeting: - Do we want to ask different questions to different parts of the audience? - e.g. technicians / academics - Target all 'researchers' and facility technicians - Catching people in hybrid roles like us - What do we do with research managers? - Maybe exclude here? --- ### Your work - What do you do? - What e-Research services do you use? - Data / software creation and use Discussion in the meeting: - Ethical risk asking about data storage - Mitigate by not asking too specific - "local storage solution" - Ask what are the barriers to central storage? Making sure there is a way to do the right thing - New data risk model - have you checked your data with this? - Anonymity - Balance between utility and anonymity - willingness to provide criticism - Options for: - "You can contact me" - "You can use my LDAP record" --- ### Satisfaction and Awareness - Do you know what we do? - How do you feel about it? #### Each service - Get service lead to write initial set of questions for each - Then harmonise - - Any other comments? free text ##### Ops - Do people want videos? - What's the quality of our communication through various mechanisms? - Tickets, docs, etc --- ## Motivation Multiple purposes for running this survey: 1. feedback about our existing systems, platforms and support 2. increase awareness about e-Research - via laptop prize - people who could use our services, but don't 3. input and steer to assis with strategic- and forward-planning - what do people want / need - what tech is coming our way in the future? 4. evidence to Bry / Bashir for expansion / funding 5. publishing report supports further research and increases our academic profile Aims: - 500 respsonses - drive more adoption of our systems and support ## Eligability We want this to be representative of the research community at King's. Need some way of filtering. - Filter by comms lists - All faculties - ## Ethics We're classified as "minimal risk" according to [the documentation](https://internal.kcl.ac.uk/innovation/governance-ethics-integrity/research-ethics/stored-documents/3applications/1index/what-is-the-risk-level-of-my-project.pdf), so only need to register our survey in REMAS to receive automatic approval within 24 hours. See [guiding principles document](https://internal.kcl.ac.uk/innovation/governance-ethics-integrity/research-ethics/stored-documents/3applications/minimal-risk/minimal-ethical-risk-guiding-principles.pdf) for information on consent and participant information. ## Survey Modules ### Consent ### Demographics The purpose of this section is to make sure the responses we receive are representative of the college and to look for differences in experience between groups. - Which faculty(s) are you based in? - Purpose: check proportional representation - Type: select multiple, custom other - Responses - ... - What is your current career stage? - Purpose: check proportional representation and understand userbase - Type: select one - Responses - ... - What is your job family? - Purpose: understand userbase - Type: select multiple - Responses - ... ### Your work - Short summary of their work - Do you manage or generate research data in your role? - What tools do you use? - How much data do you generate? - Where do you host it? - Notes: this question will give us a list of people who are potentially storing sensitive data in inappropriate places. This may bump up our ethics requirement to a full application. - Do you develop your own code? - Do you use commercial software packages? - Where do you access e-Research services from? - Purpose: prioritise time spent on infra development to support these routes - Type: ranked importance - Responses: - KCL campus network - e-Research VPN - Home - etc. - Something to understand expectations wrt. recent storage outage - - Do you have responsibility over the work of others? e.g. PI / PhD supervisor ### Service awareness and satisfaction - Are you aware of the following services provided by e-Research? - Purpose: check awareness of what we do - where do we need to focus comms improvement? - Type: grid - Questions - ... - Responses - ... - To what extent are you satisfied with the following: - Purpose: understand how services are received - Type: grid - Questions - ... - Responses - ... - Please rate your satisfaction with the range of methods we may use to communicate with you - Purpose: assess success of comms strategy especially where tied to services - Type: grid - Questions - ... - Responses - ... - Directly reference HPC scratch outage - How does this impact on general satisfaction - reliability will be one of the satisfaction axes - Mitigate recency bias - Prompt for satisfaction "excluding recent scratch outage" - Split satisfaction into multiple factors e.g. reliability, capacity / wait time - Relibility - Capacity - Support - Documentation - Training (could be its own) ### Looking forward ### Software use and development Questions from Southampton survey - Do you use research software? - How important is research software to your work? - Have you developed your own research software? - Commercialisation? - Ready to share? - How do you rate your software development expertise - Sufficient training? - Confidence with version control - Confidence with unit testing - Confidence with continuous integration - Included software development in funding proposal - _Hired to develop software_ - _Recruit full-time developer_ - _Recruit from central pool_ ### Misc - Do you have any other feedback for us? If so, please share it here - Type: free-text, optional - Can we follow-up with you about your responses?

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully