1. Elizabeth A. Evans University of North Carolina at Chapel Hill

2. Intellectual Climate Report Intellectual Climate Implementation Committee Ongoing Requests Events not Personal Scheduling Netscape calendar role Background

3. Introductory Process Working group –Included representatives from any calendar publisher identified –Added freely to the group as additional calendar publishers came forth –Received electronic mail messages –Invited to meetings to define a set of specifications/a wish list

4. Introductory Process (cont’d) Specifications/Wish List –Priorities –Others –The future

5. Introductory Process (cont’d) Specifications/Wish List: Priorities Kerberos authentication Distributed publishing Standards-based

6. Introductory Process (cont’d) Specifications/Wish List: Others Require some fields which might vary depending on type of event Categorize events using standardized terms developed by consensus Standardize input as much as possible

7. Introductory Process (cont’d) Specifications/Wish List: Others (cont’d) Automate archiving Handle open meetings Allow approval path Allow embedded URLs Include location, parking, and transit information

8. Introductory Process (cont’d) Specifications/Wish List: Others (cont’d) Allow sophisticated search options Display events in different formats Allow flexible customized printing Handle multiday events

9. Specifications/Wish List: Others (cont’d) Introductory Process (cont’d) Share dates with a personal calendar Backend database, preferably Oracle Run under Unix

10. Introductory Process (cont’d) Specifications/Wish List: The Future Room reservations Online registration for events Online ticket sales

11. Product Selection General Possibilities Process Review commercial products

12. Product Selection General Possibilities Locally developed product Develop local product Commercial products

13. Product Selection (cont’d) Process Review home pages of peer institutions Review commercial products Review locally-written application

14. The Product: Groveware’s Calendar 2.000

15. Testing and Purchase January 2000, test copy of Calendar 2.000 Preliminary testing by A&S HTML wrappers Functionality Pilot group testing during summer 2000 Purchase in early September 2000 Installed last Friday Bug reports and questions

16. Local Extensions Mailing list subscriptions/unsubscriptions Approval for posting to master calendar HTML wrappers

17. The Vendor Responsive to questions Responsive to needs Lots of promises

18. Next Steps Define calendars Define terminology Get bugs fixed, questions answered Schedule on-site training (included in license price) Production

19. Next Steps (cont’d) Resource Manager evaluation

20. Brief Demo