310 likes | 326 Views
Learn about DACdb's history, team, functions, and updates in this informative presentation. Understand security levels, terminology, access details, and club management functions. Discover how DACdb streamlines communication and reporting for districts and clubs without manual efforts.
E N D
D-7610 Pre-PETS Presentation January 2015
Agenda • Background / Overview • A few things you should know • Club Management Functions • Future Plans • New UI • DACdb Mobile • Help / Support • Q & A
Where is DACdb? 73% USA 24% World 100+ Districts 6,500 clubs • Plus: • South Africa • Coming Soon: • India • England
DACdb Background • Background • Started 11+ years ago – Rotary District 7710 • July 2006 • Mike Thacker / Mark Landmann Partnership • Did business under Simply-the-Best, Inc. • Oct 2014 • Mark purchased DACdb from Mike (Mike retired) • DACdb, LLC. • 2015 • New User Interface • DACdb University - Training • Additional Documentation
DACdb Management Team • Mark Landmann • DACdb Development / Sales and Support • 35+ years, CIO Tanning, Chief Engineer Jeppesen, United Airlines • Jamie Lowery • VP of Development and Operations • Peter Gallanis • Technical Architect / Development • John Ramon / Mike Soden (custom websites) • Websites • Ed Foster • Support • Sylvia Soden • Billing / Accounting • Heather Brandt • Dues / Accounting Training • Support, 1st level support on Dues and Accounting
Technology – Behind the scene • Adobe ColdFusion • Microsoft MS SQL • Microsoft IIS • Windows Server 2008 • jQuery / JavaScript • PHP • Over 1,400,000 lines of code • ~15,000 pages of code • Over 11 years of development
Security Levels – 10 Levels • 0 – Public (public websites – not logged in) • 1 – Members • 2 – Committee Chairs – Add/Delete members • 3 – Event Moderators • 4 – Club Officers • 5 – Assistant Governors • 6 – District Administrators • 7 – District Communication Officer (DCO) • 8 – Zone Administrators (zones, multi-districts) • 9 – DACdb administrators (Mark)
The “Big Picture” Zone 33-34 Zone 34 Zone 33 Zone 26 Security Level 8 District 5110 District 5110 Security Levels 6-7 District 7610 Security Level 5 Area/Region 1 Area/Region 1 Levels 1-4 Club 1 Club 2 Club N
Its all one Database ! Member Club Area District Zone Single point of data (e.g., phone number or email)
DACdb Terminology • MemberID – RI Member Number • UserID – DACdb internal member number • MemberType – RI MemberType (Active, Honorary) • OrgYear – Organizational Year (e.g., 2012-13) • UserName – LastName, FirstName MidName Suffix • MemberName – FirstName MidName LastName Suffix • FName – Member First Name or Nick Name if there • PartnerFName – Spouse/Partner FName • DCO – District Communications Officer (Level-7) • DLT – District Leadership Team (Committee/Council) • PMail – Personalized Email • uPages – User defined/written website pages • RoleKey – a short abbreviation for a club position (e.g., P,S or T)
How do I access DACdb? • DACdb it’s in the “cloud” - it is a multi-user SAAS web-based application • http://www.directory-online.com/Rotary - or – • http:/www.DACdb.com/Rotary • Test System • http://www.directory-online.com/RotaryTest • copy of yesterday’s data! • No RI, No Emails
Club Management • Members • Adding • Updating • Deleting • Club Positions • Attendance Reporting • RI Integration • Reports • ezStory • ezBulletin
Club – Committee Positions Club Positions – Club Level Committees – District Level District Governor District Governor-Elect District Secretary District Treasurer Executive Director Membership Chair Rotary Foundation Chair Etc… Club Positions -- ARE NOT the same as – Committee Positions • President • President-Elect • Secretary • Treasurer • Club Director • Membership Chair • Rotary Foundation Chair • Etc…
Adding a Position • System makes assumption on dates • Club positions (Roles) are checked from pop-up Click Here Click Roles Here
Role Progression • One entry, can generate 5 positions with 1-click! • Add only • Role progressions recognized: • PN, PE, P, iPP, PP • SE, S • TE, T
RoleKey Relationship • Club Position • District Committee 2015-16 2014-15 2013-14 2012-13
Why did I tell you this? • If it is done, DACdb now becomes a powerful communications and reporting tool for the District and Clubs • DACdb is the repository of information • Elimination of manual lists, multiple databases, etc. • Club Positions (P, S, T, M, TRF, etc.) role-up to District Level committees automatically: • Members added at the club level are added into the district committees • Members deleted at the club level are removed from the district committees This requires NO WORK on the part of the District to maintain these committee lists!!!!!!
Year End Conversions • There is none! • Well… nothing that you need to do! • *IF* you defined the club positions for next year!!! • Members in defined positions receive new rolls • Officers without a position become members • *IF* you DO NOT defined the club positions for next year… • We will make some educated guesses on the promotion
UI Changes • Principles behind the design: • Clean / Consistent • Appropriate use of white space and colors • Things will behave as we expect • Context in Reality – our knowledge of the world as we know them • Tablet Support (Droid / iPad)
Already found in: - Grants - Ignite - Backroom - AG Area - Files New User Interface (UI)
Future Plans: • PMail Rewrite • New Event Management (add, edit calendar events) • Registration Edit (new UI, tabs) • Reposition questions • Add questions after starting event • Allowing members to update registrations • Pre-Register • Add Questions • Come back and update registration • New Calendar • Dues – Accounting Interface • FLEX/Flash to HTML5 (iPad support) • New Server (2x everything!)
DACdb Mobile • m.dacdb.com (no www)
Help • On-Line Help • Support Tickets • Training Resources • FAQ • Email: • Support@directory-online.com • Skype: mlandmann1 • Call Mark – 303-883-6196 • Until mid-night – 7 days a week
When its not there? • DACdb success can largely be attributed to its creative users. • Numerous suggestions for new modules, functional enhancements come in weekly (if not daily) • Each request is evaluated for its merits and usefulness to other users • Some requests can literally be done over night • Some requests will be queued until development in that area is scheduled • As an owner, partner and developer of DACdb • We DO want to hear your ideas and suggestions
Q & A • What are: • Your issues • Your concerns • Your suggestions
Thanks for attending today. Have a GREAT day!