Brief introduction of the system DaemoGuilds is an online crowdsourcing platform that aggregates workers and requesters to allow them to perform and request tasks. It has a built in Guild scheme that allows its users to group and be grouped into guilds and sub-guilds that appear over time and with respect to each different kind of request. Further explanation will be given throughout this document. The first issue an introduction to our system should address is: Why using guilds in a crowdsourcing platform?
How is the system solving critical problems It is known that current state-of-art crowdsourcing platforms allow its workers to address micro-tasks with a 1-to-1 relation, meaning that they only connect with their requesters at any given time even if they are performing various tasks at a time (since they're always performing one task a specific requester introduced into the platform). What we envision by providing a guild structure is to change that paradigm, by allowing the requesters to address not only specific workers but also letting them target guilds to perform more complex tasks, introducing the concept of collective intelligence into our system. By providing an environment where guilds are formed automatically over time accordingly to which kind of tasks are being requested, we're able to build dynamic communities and sub-communities(guilds that are part of other guilds) inside our platform, making 1-to-N and ideally N-to-N connections possible in our crowdsourcing space. A important point to notice before we address the modules inside our application is that the definition of what a guild is might be a topic of discussion when it comes to different areas of specialty in Computer Science. In online gaming, guilds could be defined as [INSERT REFERENCE HERE]. However, even if we slightly change the style of the game in consideration the way guilds work in each of them may vary wildly. In some cases, the only thing in common between them is that they are groups of users who gather in an online community to achieve goals that they couldn't prior to that, but internal politics, structure and objectives may be very different from one another. From this point and beyond, we will provide our own definition of what a guild in a crowdsourcing is, so that we're able to provide a common ground for understanding. A guild in a crowdsourcing platform is defined by a group of workers who are put together inside a sub-community of our main community with the main parameters for that relocation being the history of that specific worker W to perform a determined amount of "N" tasks inside a scope of requests S within a reasonable amount of time T for each task with a standard of quality Q that reach a minimal threshold stablished by the admins of the platform. So, if we specify that a guild is formed each time a worker reaches 98% accepted tasks within the "#ImageProcessing" scope after doing 100 tasks, for example, every other worker that also get to that level will be automatically put in the same sub-community inside our platform.
Introducing modules of the system
Module 1: Census Problem/Limitations Module preview System details
Module 2: Photo Ranking Problem/Limitations Module details
Module 3: Structuring the Web Problem/Limitations Module preview Module details