| Jeremy Delahanty | |
|---|---|
| Timezone | America/Argentina/Buenos Aires (GMT−03:00/GMT−03:00) |
| Institutional Affiliation(s) | Minerva University |
| Relevant Projects | Abstract Poetry
|
| Group(s) | Table 3 |
| Table Assignment | Table 3
|
Discord
Page Schemas#Creating a new Schema Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using Page Forms is something that is an interface for filling in values for a template.
For an example of how this shakes out, see Category:Participant Template:Participant Form:Participant
- go to a `Category:CategoryName` page, creating it if it doesn't already exist.
- Click "Create schema" in top right
- If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
- Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
- Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
- Once you're finished, save the schema
- Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy.
Workshop Submission
What's your interest in this workshop?
With what "frame" do you approach the workshop? (or identity)?
Tool-builder
What materials can you contribute to the workshop for consideration?
I have conducted research as an undergraduate and as a technician for about 8 years now primarily studying the sensations of itch and pain in rodents. Much of these studies were quite simple behavioral studies using tools that were similarly simple and often fail to capture the full behavioral outputs of the subjects being studied.
I have worked on building a library that unites a 2-photon microscope with an Arduino and a machine vision camera into a (somewhat) coherent system for gathering neural data and behavior from rodent subjects. You can check it out here: https://github.com/Tyelab/bruker_control
I've also worked on a couple other small projects for the Tye Lab at the Salk Institute related to helping make some things somewhat more efficient in different workflows or more flexible to run on various machines that can be seen in that organizations repositories. Most of them have gone unused.
I have also tried introducing Git, data standards like neurodata without borders, and experimental frameworks like Autopilot for distributed behavior experiments but was often met with either apathy or, more commonly, a reluctance to adopt different practices because it would require investing a fair amount of extra time into something that is not sufficiently incentivized or supported. Many best practices when it comes to scientific infrastructure are currently somewhat hard to adopt and therefore require some additional effort from people who are often overworked, underpaid, and spread too thin. Further, not everyone finds this that interesting and are therefore even less likely to engage in discussions of communal tool building and knowledge management.
Organizer-estimated Topics
Research Data, Social Systems, Reproducibility, Incentive Systems