workPage
Pages
Draft Variance
- The Draft Archive should be a new environment/context/screen/interface reached by clicking on the number of drafts displayed next to a time version of a resource in the Master Archive - It makes each draft available for editing (though each save makes a new draft), shows when each draft was saved and by whom (and can sort drafts by author, label, date, etc.), allows the creation of new drafts and the upload of drafts, and offers a link to finalize/make time-generic the selected draft - it also manages whether a draft is valid or not, that is, whether it should be shown in the Draft Archive by default - perhaps there should be a seperate flag for tentative drafts submitted anonymously - Define - High
- Anyone may skyWrite any page and generate a draft. Only administrators, owners, maintainers, editors, and authors of the Page Series may review drafts and authorize them to become serving time-versions or invalidate them so they do not clutter the Darft Archive. Only owners or administrators of a Page Series can ultimately delete invalid drafts, but this should not be encouraged.
- Navigation of drafts should be offered to the browser that is logged in and authorized to maintain drafts. This navigation should be in the footer (or header) and duplicate the navigation of time variants. A link may also be offered to make the draft being viewed the time-generic, for the convenience of the user.
- Save every saved change as a hidden version - no work is ever lost - approaching CVS functionality - extension can go at end of file name as drafts are never meant to be served - no, rather place it next to the time version number, delineated with a dash - Define - High
- Labelling of different drafts seems vital, in order to differentiate. Also a Comment/Description about what change was made and why.
- There is such a mass of metadata to be kept about each draft that is is obvious that they will require records in the Pages table, if not a PageDrafts table of their own.
- Phase One is to save every change operation as a separate draft file in the background and to conceal them from the interface altogether, simply as a safety measure protecting every slight change from being erased by any of various authors.
- Phase Two is listing them in the interface (by request only) for read only access, to be able to copy and paste lost sections or to be able to revert completely to a draft version (by making a new version with the draft content).
- Phase Three is offering a delete capability. This could be either a flag which removes that version from the interface (so as not to clutter the history with meaningless drafts), or a true deletion of the draft file itself, for drive space management.
- Phase Four involves automatic draft file management, either deleting files a certain number of versions or days in the past, deleting files not marked with an archive flag, or collapsing files using a compression or diff scheme.
