We integrate information from published papers and image data. See below for what to do if you have new data that could be incorporated into VFB.
The provenance of information, textual or image, is always acknowledged.
Have you just had a paper published which describes new anatomical or expression information?
The best way to make us aware of your paper, and to put it on our curation list is to act on an email you will receive from FlyBase after your paper has been published. The link on the email points to the Fast-Track Your Paper Tool.
Using this tool you can provide information on what types of data your paper contains. If it has new anatomical or expression information you’ll need to fill the sections, Anatomical data or Expression, respectively, in addition to any other suitable ones.
You can also use this tool for any other, previously published paper.
Email us, and we will be able to give you advice on image requirements.
Ideally, you should contact us when you are still in the planning stages. But if you already generated a dataset, we’ll still be able to provide advice.
It is essential for successful registrations that the images are of good quality.
Follow this protocol to acquire stacks that can be used for registration.
Once you have the images, follow this protocol to register your images.
Information on publicly available template brains and bridging data is available here.
We use Hugo to format and generate these support pages, the Docsy theme for styling and site structure. Hugo is an open-source static site generator that provides us with templates, content organisation in a standard directory structure, and a website generation engine. You write the pages in Markdown (or HTML if you want), and Hugo wraps them up into a website.
All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.
If you’ve just spotted something you’d like to change while using the docs, Docsy has a shortcut for you:
If you’ve found a problem in the docs, but you’re not sure how to fix it yourself, please create an issue in the VirtualFlyBrain/VFB2 repo. You can also create an issue about a specific page by clicking the Create Issue button in the top right hand corner of the page.
An exploration of how an example query is added to the VFBTerm object under VFBconnect which provides a template for any future queries you may want to add add to vfb.term
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.