Tags

General / Background information

Introduction by Ray Helmke

Meeting focusing on organization / presence. NOT appearance

public presence

organized by research activities / public relations. Coordinated with physics dpt., cornell guidelines, CHESS. mindful of funding agency needs.

internal

any information anyone keeps should be available to others in dpt and lab, obviously available via web
  • preprints / documentation
  • drawings / drafting
    • interaction with outside vendors
    • versioning
    • Natural choice is autodesk vault, but must work in web interface
  • images
    • fedora project * digital library
  • Elogs
  • Wiki
    • internal documentation
    • access control
    • edit from anywhere
    • collaboratively maintain documentation
  • CMS and international collidor will have own DMS systems
    • ERL

Separate content from presentation!!! allow anyone to easily edit / post documentation

Proposed Implementation / Organization

Discussion / Feedback

Compared with other large universities, it seems we need / have a general "Communications Office." Someone in charge of overseeing the site / appearance / documentation. Someone to critically view communications / appearance / publication process. Proactively think of what should be where, what's missing.

A primary goal is a distributed authoring environment. This will encorporate some sort of "publication" process where anyone (who you allow) can update/add a page, have changes approved, and posted.

Model of organizing content based on user groups can sometimes be confusing. Organizing from point of view of user community is good, but still need topic-based grouping which leads to cross-referencing.

Directory link for user community.

Transitional plan for groups with existing sites (such as Accelerator Physics).

Hopefully some working test model available by end of year.

Once again, a strong need for group overseeing vision / presentation / content "Communications".

"Events" Calendar
  • Try to leverage Oracle Calendar as much as possible.
    • Possibly an "Events Calendar" component of Oracle Calendar

Presentation / attractability is key, but obviously no frivolous extra "features".

Accessibility is also a top criteria.

need and leverage man power.
Topic revision: r1 - 07 Dec 2005, DevinBougie
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding CLASSE Wiki? Send feedback