The only way this would work is if there were a USER for each position: Chieftan, Sencha, etc. This would require either

1. re-thinking how we assign accounts (your profile wouldn't be *you*, it would be your position and then it would be reassigned to whoever takes over the position at Samhain),
2. having another 'special' user account login for each administrative position and thus, a separate login username/password for when you want to post in that capacity.

I see a major problem with both of these approaches, mostly due to my belief that if the site was confusing to users before, they would *never* figure out either of these schemes. Or, they would continually be posting as the wrong account: posting as the Chieftan in the forums accidentally, etc.

Perhaps, we can use the 'category' feature to organize this stuff somehow. When you write up a new blog/story post, there is a drop down to allow you to select what category it's in. If we have Chieftan, Druid, etc. added there, perhaps we can write a way to list just those categories in the future when we want to see that stuff. That way, the member is always logging in as him/herself and FILING the post away in the right category.

What about just giving the people with the position the ability to blog. then when a new member gets that position the whole blog would be moved over to that person's account. for example, colin has his forum entries, account and blog and what not. Then when he is no longer chieftain, the chieftain's blog would move to the new chieftain's account. Whould that work?

Actually no. A blog entry is a 'story' (or a speech as you put it ;) which is tied to a specific user account. The 'blog' isn't actually a "thing" that can be moved, it's a series of stories that are connected only through the fact that they are posted by the same user. The only reason they seem like an entity is that there is a link that says 'so-and-sos-blog' which lists all of that guy's posts. You can change authorship on a blog entry, but you would have to do it on each one manually and then, it still doesn't appear as something from the Chieftan, it will just appear that somebody else wrote something the previous guy did!

I can disallow the blogs entirely, or give everyone the ability to blog, or give the ability to a special group (to which I can add certain users). There are two solutions I see (without thinking about this too deeply):

If the posts are created by a user called 'Chieftan' or another user called 'Druid', and the profile is generic for the class and the avatar for that user is set as a symbol instead of a photograph, then there will eventually be a 'thread', if you will, of stories posted by the Chieftan or the Druid, and when the member holding that position changes, the password on that account could be changed, and the new officer would gets to control it. They could log out and log back in as themselves if they wanted to say something in less 'official capacity', but I'm afraid that people will get confused. Also, the pronouncements would not appear as coming from the actual PERSON writing it at all, and that authorship info (Colin, Aonghus, etc.) would eventually be lost.

With some more work, it seems it would be possible to TAG a blog entry as an official pronouncement of whatever class (Druid, Chieftan, etc.). Then I might be able in the future to create a link that calls out all blog posts tagged in such a way. This would have the same effect that the 'blog link' has: it would *appear* that these posts are all some cohesive entity, but really they're all just tied together - instead of by user, by officer title. This is all just crazy-talk though since I haven't looked at *how* to do this yet at all.

It took me a little while to think about this 'problem', but it's clear now that we were both barking up the wrong tree. The power of Drupal is in the organization of 'nodes' into a hierarchy using the book module. Any blog post, page, story (or even forum topic) can be linked into the library in a hierarchical fashion.

I've already arranged some of the past official notices into the library (take a look at the books under the library). The books are made up of pages, which can be posts drafted by many different people, and are arranged in a logical way.

The minutes have been filed into Meeting Minutes and Event Flyers book for instance. Each complete minutes can actually be constructed of several different pages: one from the Treasurer, one from the Druid, etc. We could simply teach each member how to write up a blog post for the portion of the minutes they are responsible for and then link them into the minutes. The secretary would still be responsible for minutes, but the official reports (and anything special a member wanted to prepare ahead of time) could be linked into the minutes chapter as needed.

Forget assigning separate usernames and passwords or moving blogs around, this site is set up to provide structure to documentation, we just all need to understand how it works.

I don't see the point of having a blog (or now my thinking is Book chapter/page) by office. We have a minutes/newsletter book which is one thing officers might publish items into (think treasurer's report and the minutes), and we have an Event Info book which seems the most likely place to store event announcements, and I can see the Fili needing to post items into the Book of the Laws, and the Bard posting into the Book of Song (not yet moved over).

But I just don't see the value of filing things by office for most stuff. Sabha suggested a Druid book might make sense for ceremonial reference.