dude, are you aware that this is genius? you've created a publishing mgmt app
| Project: | Writing Assignment |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
okay, as you've described this you have in fact created an editor's **dream** from within a content management system and i think that unless others have brought this up before, you may not even understand the scope and brilliance of your module for application to content management within editorial environments (a HUGE part of the drupal user base, newspapers, etc)
as i understand it, and i'll use my analogy to see if this makes it crystal clear, here's the ultimate workflow - and a possible feature request with the 'claiming' item:
an editor puts up "stories wanted" (your 'teacher assignments') with word count requirement
writers 'claim them' (your students)
once claimed, that item is not available to other students to claim unless 'unclaimed' (feature?)
story written/reviewed/commented etc through editorial review cycle under auspices of groups.
could this module be doing this kind of thing? a "stories needed' following your assignment metaphor is brilliant - only clincher is that a claimed item must be locked to other users while being written and must be possibe to mark as completed (or passed by date or some other thing that probably is already in there)
you might think about renaming it the "Editor in Chief" module - no joke. this is killer, and not just for schools.
#1
btw, will it be coming to d6?
..sorry, also wanted to add to above (very important!) - collaborative author review (identical to your 'students grading others' model, but in this case writing peers improving overall quality of articles with feedback and critiques etc - or a factcheck dept could cite needs like, "need to check this fact about X" or "need to state source of quote Y" and so on...)
#2
Hey zilla -- sorry to take so long to get back to you -- I need to check the issue queue's more often. To answer your question -- no I hadn't realized I'm a genius... :> But thanks for pointing it out! I really like your idea of applying my module to newspapers. I actually hadn't thought of that application but I really like the idea. The claiming feature wouldn't be difficult to implement either.
Here's my problem though. My module has sat dead in the water since January. I'm a student in college and I only have time to code for my research job and I've been busy writing papers / building websites / whatever else.
I've been wanting to do a complete rewrite anyways of my module because the architecture of the first draft is ugly -- also I wanted to use the power of workflow_ng to handle much of the workflow + state tracking parts of my code. I'm not sure though when I'll have time to get back to my writing_module code. Perhaps this summer when school's out.
Are you a coder? If you are and want to help write the module that'd be great -- send me an email if you're interested.
Kyle
#3
unfortunately i'm not a coder- but to be honest, it looks like a lot of major d6 modules won't be ready until summer anyways, so sounds like you're timing might be just fine ;)
#4
"students learn best if they teach what they learn", a good phyloshpy, I agree with you. I am trying your module on my site, hope it works for me.