I have been investigating using ejournal (and other modules and methods) for a need where I want to publish several "journals" which are actually ways to use the same nodes differently. I want to have announcements nodes (which are placed on the home page, site calendar, and the "announcements" page by using views), and two journals: a weekly announcements wrapup and a monthly, more comprehensive, journal. Because of the limitation of ejournal where a node type can only be selected for one journal, I can't make it work for this use. Ejournal looks like a better solution to my need than custom views, which could be an alternate way to do the same thing.

Have you considered an enhancement where ejournal would allow multiple journals to use the same node type if this option is enabled?

Comments

romca’s picture

romca commented
Status: Active » Closed (works as designed)

Hi,
I am not sure you want to do that (does not sound very nice) because if you have two journals, two different ways of handling contents (either concise or more comprehensible) than the nodes are probably not the same. Technically, it might be possible, because after the article is published ejournal does not care about its node type. It is only during the creation stage when we need to know which journal /if any/ is associated with this type of content, yet I am not convinced to design something that will actually allow to choose the journal when in the node creation stage.

I would recommend to you to really think whether you actually need/have two journals

if you really need to keep one node type, you may use one journal and divide it into different sections - say the wrapups being published in the issue or volume X, and short notices in issues of the volume Y

or, with the CCK module, create your node type definition - export it - change its title - import it again. And voila! You got two node types, the same structure, in 2 minutes. You can use two journals then.

Best,

bdornbush’s picture

bdornbush commented

I should clarify my need. I am building a web site for a church. They have web based announcements, weekly printed announcements, and a monthly newsletter. Often, one announcement will appear all three places. Often, one announcement will appear as an abstract in the weekly printed announcements and as a full article in the monthly newsletter. Currently, the web site is used only for the web based announcements, which appear on the right side of the front page using a view that shows the top 6 announcements and also on a page that shows a view of all announcements. The announcements are made using two custom node types so that they can have other fields that control when the announcement starts and stops appearing in the view, and also appear on the site calendar.

I want to use the web site as the basis of a "work flow" that will support submitting an article once for all three purposes. I would have an article submitted and then categorized and edited for the three purposes. I am thinking that the weekly announcements and monthly newsletter would each be a "journal." Thus, if one node could be available to both "journals," it could appear as needed in either or both as well as on the web site as an announcement.

Since non-technical users would submit the articles, I am planning for a way that they could submit the article, and then it could be selected for one or both publications.