 | | |
|
joa1
User
Aug 28, 2002, 1:25 AM
Post #1 of 3
(2817 views)
Shortcut
|
DocBuilder -> Collaborative Tool...
|
Can't Post
|
|
Greetings,
I thought I would add my DocBuilder wish list to the forum:
1. AutoBackup and recovery to a folder of choice, entered in the admin panel.
2. Possibility to assign several users' levels, and areas; this could be done using a simple panel, that is created automatically by the script for any book/manual/project that is created, using a folder tree, that progressively grows as choices are made/permissions granted or denied.
For example, the main administrator, would be the only person who has access to DocBuilder's full functions, and all current projects, creating and assigning accounts, etc. Then, project administrators can be assigned areas/folders to manage and see, and same with users/editors/writers.
Project administrators can be granted access to access a folder and all it's subfolders, and view any folders that the main administrator assigns as well. They may also, if permission is assigned, create folders, subfolders, paragraphs, etc., in those folders.
Users/editors/writers can be given access to edit/publish to some folders, and see others that the main administrator assigns.
If I use a book or manual as an example, this is what I would see it working like in DocBuilder, saying this would be a manual, part of a series of five manuals, and each with 3 chapters, and we start with an Introduction, 3 subchapters or sections, it would be looking like:
MANUAL
Introduction
Chap. 1
SubChap.1.1
Paragraph1.1.1
Paragraph1.1.2
Paragraph1.1.3
SubChap.1.2
SubChap.1.3
Chap. 2
SubChap.2.1
SubChap.2.2
SubChap.2.3
Chap. 3
SubChap.3.1
SubChap.3.2
SubChap.3.3
Administrator has access to the whole series, and can alter manuals' structure in anyway.
Then could assign a project administrator to each manual, and some writers/editors.
Project Administrator is granted these rights:
Modify Book structure – (Yes/No) No
Modify Introduction – (Yes/No) No
See All Content – (Yes/No) No
Add Chapters – (Yes/No) No
Add Subchapters – (Yes/No) No
Delete Subchapters – (Yes/No) No
Add Paragraphs – (Yes/No) Yes
Delete Paragraphs – (Yes/No) Yes
Writer A is granted these rights:
Viewing Access – (pull down lets select) Full / Restricted; full means all book/manual content; Restricted, opens another series of puldowns, with all content areas, intro, chapters, etc. When a section is selected, an option again is presented, for full or restricted, and it follows like this is tree like manner; full meaning everything under it, restricted asking how to restricted what's under it.
Publishing Access – Full / Restricted (same as above)
In this way, the main administrator can create accounts for different users, with different rights assigned to editors/writers, and let them access/edit and/or view all or part of the book being put together.
When a user logs in, he is only shown his own area of editable/viewable content, but none of the others'. Full administrator also is given a chance of adding to these account pages a decryption of the project, a list of names of people involved, who is administrating it, etc. If available, these can provide also a click'n email link, so people can keep in touch.
Any edited content could have a [x] box so editors could click on it, and the administrator receive notification that work has been finished and is ready for reviewing and is being submitted for approval/request is being made it may be published. This can be made visible by a flag/icon that appears on the administrator's control panel, by the article… If anyone has administration editing or viewing rights over any section(s), than they too get to see that flag/icon.
In this way, the administrator of DocBuilder could, for example, have a writer access the login area, and have selective access to view the whole book, but add content to Chapter 1, but no possibility to create nor delete Chapters or SubChapters/sections, although having the possibility to add paragraphs.
Another, could be granted access (view/edit) only to SubChapters 2 and 3, on Chapter 2, while another could be granted only editing rights to SubChapter 1, filling in content on paragraphs already created, but not adding nor deleting paragraphs, etc. The structure of the book would be entrusted either to a project administrator, or stay with the DocBuilder administrator, as s/he would decide.
Having read access to areas other than the already published on the website would mean that members of an editing team could have access to the material being worked on but not yet made public. These materials could have a draft status.
All content could indeed have different flags for it's status. Assigned but empty areas/chapters, etc., would display one icon. As soon as any content was added, it was flagged as editing having worked; same for any sections created, etc. Then the above flag for revision/publishing; then another for "published" (meaning, made public.)
And of course, a search tool, mentioned elsewhere, would be essential too.
Well, hope this is clear. It is in my head, but easier seen that worded… Hope still made it to be useful…
If this could be done, DocBuilder would be one of a kind for collaborative work, and the use endless! I also know this is a lot of work and maybe even a major overall facelift or DocBuilder, but wishing big make dreams come true! 
Kindest regards,
Joao
|
|
| |
|
Damon
Staff
/ Moderator
Sep 9, 2002, 5:32 PM
Post #2 of 3
(2647 views)
Shortcut
|
|
Re: [joa1] DocBuilder -> Collaborative Tool...
[In reply to]
|
Can't Post
|
|
Hi joa1,
Wow. That has to be one of the most detailed and well thought out feature request lists I have received. I'm not sure what is possible as I'm not a programmer myself but I will add your suggestions to our feature request list for our programmers to review.
For users management, possibly what would be more feasible is to allow specific users access to specific document groups without having to re-work the whole software.
Thanks for all your effort in putting together your detailed suggestions. We appreciate it. :)
Cheers
Damon Edis
interactivetools.com
|
|
| |
|
joa1
User
Sep 9, 2002, 8:29 PM
Post #3 of 3
(2643 views)
Shortcut
|
|
Re: [Damon] DocBuilder -> Collaborative Tool...
[In reply to]
|
Can't Post
|
|
Hi Damon,
You are welcome. Glad it is comprehensive and may be at least in part considered. I just believe the potential is there - and would make DocBuilder a one of a kind tool!...
Maybe for starters, the alternative you mention would make this in part possible - and that would really be the bottom line for collaborative work. As is, this is a good tool, but must remain closed to the webmaster(s)/insiders... not really possible to open it up...
Community tools, on the other hand, must support increased functionlaity and extra security measures :) and I am really think collaborative here.
Kind regards, and keep up all the good work at IT!
Joao
|
|
| |
|
