Welcome to the Open Targets Community forum!

Welcome!

Welcome to the Open Targets Community. This is a place where you can find out the latest news from Open Targets, find answers to your questions about using the Open Targets Platform or Open Targets Genetics, and share ideas with other members of the community.

The Open Targets team monitors the forum and responds when and where we can, but we will not answer every question. Members of Open Targets have the Open Targets staff badge.

Language

This forum operates in English, as it’s the working language of Open Targets.


Before you post

Did you read the documentation?

Our team has worked hard to create documentation for the Open Targets Platform and Open Targets Genetics.

These have search functions, and are regularly updated as we add new data and features, so make sure to take a look!

Search

A number of topics have already been raised here. Before posting your query, start by searching the forum; it might save you a lot of time.

If you find a post that solves your problem, please like that post. It will tell others that you found the post useful, and let the poster know that they’ve helped you. Answers take time and effort to write, so show the posters some love!

If you find a similar topic but it doesn’t exactly answer your question, don’t post in the same topic. Instead, start a new topic, and reference the thread you found.


How to write good questions (or suggestions)

Use a relevant category

Use relevant tags

These help improve the search engine, and give additional context to people reading your question

Title

A good topic title should summarise your post and give a good idea of what it’s about, without being too wordy.

It might be easier to write this last, after you have written the whole question.

Asking good questions

Start by describing your goal. This helps others understand what you are trying to achieve. If you’re writing a suggestion or feature request, consider including a user story, for example: “As a [type of user] I want [my goal] so that [my reason].” This means we can get to know you better!

Show your workings. Describe what you’ve tried, and what problems you are facing. Maybe link to other threads you have looked at, and why they didn’t help. Include screenshots and relevant pieces of code. For example, if you are reporting a bug you’ve observed, provide instructions on how to reproduce the bug, and make sure it’s reproducible.

Showing that you’ve put effort into writing your topic will help demonstrate that you’re not just looking for others to do all the work for you. And, the clearer your issue is, the more likely you are to get an answer.

Read before posting

Once you’re done writing, read your post before you post it. Make sure that it makes sense, that the topic, tags, and category are relevant.

And make sure it’s readable! Use paragraphs, punctuation and white space.

Tagging people

In general, you shouldn’t tag people in your post, as this may be seen as disrespectful and demanding help (unless you’re thanking them, of course!).

If you do tag someone, make sure you are polite and respectful.

Similarly, please don’t private message people to ask for help. It means that other people can’t learn from your questions. You may message our helpdesk avatar, @SirTarget, if you have a query that contains confidential information.


Once you’ve posted

Wait

It can take time for someone to respond to your question.

If it’s been more than a week, have a re-read and see if the title, category, tags, or even the post itself may need some attention. Maybe you’ve missed something important!

If you think it’s as good as you can make it, then you can consider bumping it by posting a reply to make it more visible. But don’t do this too much or too quickly!

If you’ve solved it

Fantastic! Please reply to your post with details of how you solved it.

Thank you for contributing to the Open Targets Community!



Code of conduct

Our pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identify and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our standards

Examples of behaviour that contributes to a positive environment for our community include:

  • Demonstrating empathy and kindness toward other people
  • Being respectful of differing opinions, viewpoints, and experiences
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility and apologising to those affected by our mistakes, and learning from the experience
  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behaviour include:

  • The use of sexualised language or imagery, and sexual attention or advances of any kind
  • Trolling, insulting or derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others’ private information, such as physical or email address, without their explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behaviour, and will take appropriate and fair corrective action in response to any behaviour that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, topics, and other contributions that are not aligned with this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.



Inspired by the lovely folks at Home Assistant and Writing a proper GitHub issue

Code of conduct adapted from the Contributor Covenant.