Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

What are we trying to solve with a Shared Documents Model for CSS?

Anne's Framing Questions

Panel

In an email from June 27, 2006, Anne reminded us:

Here I would like to interject for a moment to ask the question: what was our original purpose in seeking a central place for us to go for information, reports, plans, etc.?

I would like to add the following questions for consideration in the discussion:

1. What are the desired outcomes of having a central place for all these shared items? I envision having links in the future between documents, say quarterly reports/resource model/financials that would be best done with files in one place.

2. What tasks do we envision relative to each type of document ie changes to annual plans, quarterly report text, inputting of updated financial forecasts, addition of css-mgrs meeting agendas, etc...

3. Can both confidential and non-confidential materials be kept in one central place with confidential materials kept in a hierarchy of password-protected access folders?

...

Existing Conditions...

Our default approach to collaborative work seems to be:

...

 

 

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

 


Budgets and Forecasts

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. 

...