...
|
|
|---|---|
Operational Plan. | Now a word document of mostly bulleted text with a table or two. For fun, this is the is a Wikified version of the draft FY07 CSS Operational Plan Compare this version to the one in scripts.mit.edu -- http://scripts.mit.edu/~support/wiki/index.php?title=June_26%2C_2006_version |
Quarterly Reports |
|
| Generated on a quarterly basis. |
Meeting Schedule, Agendas, Outcomes | Intermittently used as a formal work planning modus operandi within CSS. |
Process Documentation |
|
Resource Allocation Model | Currently maintained on sparkler1 as the official copy, with the working master on Rob's laptop. |
Which technologies are likely to be best for what?
Confidentiality is one forcing factor. Documents with sensitive data need to be closely protected. We need to be able to have documents locked down so that as few as three people only are able to view and update.
...
Compatibility is a forcing factor. If, say, the CSS portion of the quarterly report needs to be able to merge into the same master document as other directorates, then we need to be able to convert, at least, form the group-edit format
Working Plan for a shared folder hierarchy on a suitable server
Server: a pc- and mac-compatible file-sharing environment, with group and individual permissions. It needs to not be AFS, as security accidents are relatively easy there and the impact is usually to inadvertently share sensitive data files to the world. The existing sparkler server, a windows server that exports to Macs and PC's natively, has evidently met the security test since it has all of IS&T's confidential information on it now.
Filespace: for the purpose