I've recently discovered OP while searching for a better way to mantain the website of my weekly newspaper, and I've tried many CMS like Joomla and others, and so far only OP has almost all the features I require, except for this one, so I hope maybe someone with more experience can help me.
What I need is to organize the articles of a weekly edition separetely, or an "issue", and after said week is over, I can create a new edition and the last one goes to the Archive, so it can be viewed, but, always, organized like that, by editions, not just like older entries, something similiar to what they have in TNR (http://www.tnr.com/magazine-issues) in which you can see the past issues and access the articles in said issues, but I have no idea how I can achieve something like that, I have little knowledge about Drupal but I'm really interested in doing this, because then, OP would be the perfect choice for me, thanks in advance and sorry for my terrible English, as it's not my first language.
Comments
Packages?
I believe packages may achieve what you are trying to do. In a way.
I would regardless suggest Prosepoint instead for editions and channels.
See http://www.prosepoint.org/node/334 for a comparison
http://satyamediagroup.com
I've tried Prosepoint, but
I've tried Prosepoint, but it's not suitable for what I need, the only feature that I like from PP is the channels, but OP has, as I said, almost all the features I need except for the editions. I've tried to packages in OP, but I can't understand how to make it appear on the frontpage, but from what I tried I believe it is a good alternative, thanks for the reply.
Yeah, You would think context
Yeah, You would think context should have a way to pull in these 'packages' though I assume if you built a view based on the package(s) then you could use context.
Otherwise, simply build a Panel page, after creating a package, and use the package as content for 'existing node'. Then set the panel to frontpage.
Now, this should work perfectly in my opinion. Problem is, at least in my case, OP seems to refuse to show content in Panels set as frontpage :
http://groups.drupal.org/node/101354
http://satyamediagroup.com
Editions are not supported in
Editions are not supported in OpenPublish out of the box, yet. Implementing it in a generic way so that it's both flexible, yet user-friendly is a complex task.
However, if you want to just do something specific, for your own news website, a person familiar with Drupal should be able to put a version together, using Views, CCK, Node Reference and Node Relationships (modules already included with OP) pretty quickly.
.............................................
http://twitter.com/inadarei
You could try Views Date
You could try Views Date Range to organize your articles into weekly editions
http://drupal.org/project/views_daterange
I am looking to implement the
I am looking to implement the same functionality. I am currently evaluating the E-Publish module and Collections module. I am also evaluating organic groups as a way to setup editions. It is not exactly what is was created for, but I think the node relationships it has make it a possible canidate.
City Specific "Editions"
I'm also trying to evaluate ProsePoint vs OpenPublish for an online magazine that will also include city "editions." Meaning, some articles will have to do with what's happening in a particular location that week. I want users to have a default city they are assigned to by their own preferences. Can this be done with the packages feature?
In playing with OP for a few hours I can't seem to figure out how to even list a city in the taxonomy section...just topic. City seems to be part of Calais.
E-Publish
I am the original creator of the E-Publish module at http://drupal.org/project/epublish although I am no longer actively using it myself and maintenance has been handed off to other developers. E-publish was intended specifically to handle organization of nodes into publications with volumes and editions. (Volumes were optional, but a lot of traditional publications are organized by volume number and edition number.)
Back when I wrote E-publish, the Views and CCK modules did not yet exist, and I think the functionality of E-publish could be better implemented now using a combination of Views, CCK and Nodequeue. I have a couple of current projects for which I'm interested in doing this and will post updates here if I make headway. I'm thinking that the way to do this would be to create an "Issue" content type and use http://drupal.org/project/smartqueue_nodetypes to create a nodequeue subqueue for each issue. For maximum flexibility, there could also be a "Publication" content type and a "Volume" content type, each of which could also contain their own nodequeue subqueues. However, some sites would choose not to use these content types. For example, a website that only has a single publication might not really need the "Publication" type, and publications that have editions but don't break them out into volumes would not need the "Volume" content type.
I think most of this could be done without a need for custom coding, and since Views, CCK and Nodequeue are all exportable to Features, it could all be exported to code and then shared around as an add-on feature to OpenPublish for people who want that functionality.
Sheldon Rampton
Senior web developer, New York State Senate
http://www.nysenate.gov
http://drupal.org/user/13085