This is part of my series of posts about the PolyAnno project – more here I never really got far enough into completing the more necessary parts of the project to implement anything useful or even working with the users, but I planned to allow the users data to record favourited data (an image or … Continue reading PolyAnno: Users
This is part of my series of posts about the PolyAnno project – more here Qualifications vs Wisdom of the Crowd? The methodology by which we verify which transcriptions and translations are "most correct" was/is a huge design problem. Leaving aside the more in depth discussions about defining correct, crowd sourcing projects appeared to take … Continue reading PolyAnno: Verification
This is part of my series of posts about the PolyAnno project – more here Basics Eventually I decided it would be easier to separate out development of the longer term storage i.e. the Node/Express/MongoDB/Mongoose framework such that it can be installed separately and understood more simply in isolation. The Github repo can currently be … Continue reading PolyAnno: Polyanno Storage
This is part of my series of posts about the PolyAnno project - more here Storage and API Setup To store the annotations I decided to use MongoDB as a classic NoSQL, non-relational database to store the JSON-LD files because of its support for handling JSONs. I decided for simplicity to use Mongoose as a … Continue reading Polyanno: Basic API Design
This post is part of the series A Complete Beginner's Guide To Hacking So the main website languages define files that are sent off to be interpreted "client side" or rather to be interpreted by the browser that the client or user trying to view the page has. Client side languages are really good for … Continue reading A Complete Beginner’s Guide to Hacking: Data Design
Blue Pigeons 