Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

...

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