Alex and I started trying to build our new data model last Thursday, and we figured that it would go much more smoothly and quickly than the last time we tried. Like the previous time, we decided to use Rails scaffolding, figuring it would be easier than generating the individual pieces by hand. However, we ran into some unanticipated road blocks. For example, we wanted a few different models to have IDs associated with them, so we added them into the model framework. The scaffolding helpfully added them to our views page as well, so instead of having IDs generated automatically, they appear on a form for the user to fill out, thus defeating the purpose of the ID field. After lots of frustration, we decided to try to create a model without scaffolding when we get back from break. We figure that it will take more time, but will involve less tweaking and will give us the opportunity of better understanding how the component parts of a rails application fit together. We may decide that it’s too much of a headache and that it would make more sense to use scaffolding and just to delete the unnecessary parts, but in the interests of experimentation, we’ll give it a shot.
- Sounding Scholarship: A Workshop on Making Your Research Sing
- Starting off on the Right Foot (Part One)
- String Theory, or: Let’s Explore Social Networks with String!
- Teaching Transcription (and Secretly Metaphysics)
- Twitterature: Mining Twitter Data
- Call for Digital Humanities Fellows Applications – 2019-2020
- A Toolkit […?] the Public Domain
- Text Mining and Digital Humanities
- I/O: Reading & writing as a digital humanist
- Job opening: Come advocate for our users!