1. Nile

2. 2 What is Nile? Nile is based on Plone®, an open source web application designed to make it easy for non-technical users to create, edit, and manage content and websites. Third-party products and local customizations were added to enhance the functionality and make Nile a unique system for Computing & Communications. Nile is a Content Management System (CMS) built for and by Computing & Communications

3. 3 Uses of Nile ContentOrganization TeamsRoles CollaborationPublication Work FlowDocuments VersioningControl StructureEditing SearchSharing ProjectsNavigation StructuresAdministration ImagesAuthoring LinkagePermissions

4. 4 When to use Nile More Complexity Structure Control Work Flow Content Tracking Wiki Nile Less Reference: https://docs.cac.washington.edu/cactools/framework/reference- documents/Collaboration%20Applications_Guide%20v.02.doc/view

5. 5 Current Nile Sites Nile Site NameSite ContactSite Address Nile Help nile@cac.washington.eduhttps://docs.cac.washington.edu/cac/nile/help Nile Support nile@cac.washington.eduhttps://docs.cac.washington.edu/plone Nile Tutorial nile@cac.washington.eduhttps://docs.cac.washington.edu/cac/nile/tutorial C&C Product & Service Framework nile@cac.washington.eduhttps://docs.cac.washington.edu/cactools/frame work CAI Focus Group Ais-caifocus@u.washington.eduhttps://docs.cac.washington.edu/cai/ DRBR Cms-drbr@cac.washington.eduhttps://docs.cac.washington.edu/drbr/ EDW datawarehousing@u.washington.eduhttps://docs.cac.washington.edu/edw ERA sagehelp@u.washington.eduhttps://docs.cac.washington.edu/era PM Focus Group pmfocus@u.washington.eduhttps://docs.cac.washington.edu/pm/ Rome Cac-rome@u.washington.eduhttps://docs.cac.washington.edu/rome/ SURE suredevcon@u.washington.eduhttps://docs.cac.washington.edu/sure VS2005 Focus Group vs2005@u.washington.eduhttps://docs.cac.washington.edu/vs2005/

6. 6 Questions for Prospective Sites 1. Is there a Nile site in your department or work group already? 2. How many authors will be creating content? 3. How many people will be accessing the site (reading)? 4. Should the site be accessible to people outside C&C? 5. How much experience do the authors have with creating Web pages? 6. Do the authors have any experience with Plone? With Wiki’s? With other content management systems? 7. Is there a person in the group who can help with administrative tasks in Plone, such as adding users, etc? 8. Where are the documents now? 9. How much content needs to be migrated? 10. Is version control a requirement? 11. What additional functionality is needed? Any special requirements?

7. 7 How We Select New Nile Products Evaluation 1. What are the features of the product? Do they fit the needs of our site? 2. What are the dependencies? Are there any incompatibilities? 3. Check the product's bug tracker. Are there critical unresolved bugs? How quickly do bugs get resolved? 4. What is the release frequency? 5. How much customization does the product require? 6. Who created the product? Is it still supported? Is there a group supporting it? 7. Look for reviews. 8. Read the documentation. Making a Decision 1. How well do the features work? 2. Will we be able to maintain it? 3. How well will migrations work? 4. Can you un-install cleanly? 5. How much does it complicate our site? 6. Is there a less-complicated way to get the same (or similar) functionality? 7. Do other features stop working? 8. Is it a released product?

8. 8 Nile Support First line user support, site training, CMS best practices: contact your department or work group Nile primary site manager. Report product bugs, request new Nile products, contribute to Nile documentation & training materials: submit email to Nile Support Team at nile@cac.washington.edu. Reference: https://docs.cac.washington.edu/plone/nile-user-group/Nile%20User%20- %20Support%20Group%20Charter.doc/

9. Questions? Contact your local Nile site manager or email nile@cac.washington.edu