Posted by kamorrissey on January 31, 2012 at 10:47pm
I am new to Drupal. I intend to build a catalog of Colorado authors and publishers and their published works, where registered users can opt to take control of specific pages, e.g., an author can register as a user and claim control of the author page about them, or someone can register and claim control of a publisher's or bookstore's page. There will also be a calendar of author events such as book signings.
I'd like to pick some peoples' brains (say 1-2 people) about how to implement what I have in mind, specifically what features of Drupal use and suggested modules, and I'm willing to treat them to dinner in return. Any takers?
People can reach me at kamorrissey@kamorrissey.com.
Comments
I forgot to say, I live in
I forgot to say, I live in Denver, due south of the Capitol but north of I-25.
I do know how to do this but
I do know how to do this but it would take some step by step explanation of how i went about it and why. I'd be willing to present the how to's in the next drupal meetup if anyone else is interested.
Presenting at DBUG Denver?
Hey Andy,
Are you still interested in presenting on this? I saved a spot for you in the schedule:
http://groups.drupal.org/node/209903
I just wanted to confirm with you before putting your name down.
Sure, if there's enough
Sure, if there's enough interest... I'd be happy to volunteer for that.
intend to be at meetup
I intend to be at the next meetup.
I'm interested in the project
I'm interested in the project as a whole - amusingly I've got www.dasfa.org up as a Drupal site, and there's a number of local Science Fiction authors that get mentioned there.
I'll be available at the next Denver meetup to chat about this, or maybe could meet on a good weekend to discuss it.
-john
DASFA, eh?
I'm a somewhat recent DASFA member and a friend of Sourdough's. I just ran for DASFAx editor and lost by 1 vote. Have we met?
Hey!You may not have - I
Hey!
You may not have - I don't show up to many meetings, I'm afraid. I'm fond of DASFA and of MileHiCon in general, but I'm pretty busy with my new daughter. :)
I'm a little astonished there was actually a race for editor - sadly, a lot of the time the elected positions go to whomever is willing to do them without much competition.
ps: As a further note, I used to be editor for a few years (with my wife) a number of years ago myself.
-john
Since there is a little
Since there is a little interest here... i'll explain briefly what i used to make this work with no custom code at all.
Modules used:
references
nodereference_url
rules
rules_link
views
workflow
Some of the modules above could be skipped but i used them for backend administrator approval of the claim.
How i did this...
Created a "claim" node type with node reference field linking to the nodetype to be claimed. I used the node reference url widget to autopopulate the node reference field from a link in a block on the parent node page.
I used the rules link module to create a rules link called "approve this" which i can populate the link in an administrative view. Theres a rule attached to this link that when fired (meaning the administrator clicks approve), the parent node author becomes the author of the claim node which enables that user to now have edit permissions to the parent node. I also created a hidden checkbox called "verified" on the parent node that by default is unchecked. That rule also sets that value to true for the checkbox. I did this to be able to filter the "Claim this Block" generated from views module to only be shown if parent node is NOT verified. The workflow module i used to simply manage status changes for the claim form from creation > pending > approved merely for backend filtering.
There may be other better ways to do this but it works pretty marvelous for me. My way of doing this is to only allow registered users to create a claim in which i'll display the same link text for anonymous users but direct them to the user registration page instead.
Hope that helps inspire some ideas...
Andy