1 / 36

Archdiocese of New Orleans & Houma Thibodeaux, LA Welcome to Your Destiny Planning Meeting

Archdiocese of New Orleans & Houma Thibodeaux, LA Welcome to Your Destiny Planning Meeting. Implementation Teams. Archdiocese of New Orleans/Houma Thibodeaux Team Follett Software Team. Archdiocese of New Orleans Houma Thibodeaux Planning Meeting.

dougal
Télécharger la présentation

Archdiocese of New Orleans & Houma Thibodeaux, LA Welcome to Your Destiny Planning Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Archdiocese of New Orleans & Houma Thibodeaux, LAWelcome to YourDestiny Planning Meeting

  2. Implementation Teams Archdiocese of New Orleans/Houma Thibodeaux Team Follett Software Team

  3. Archdiocese of New OrleansHouma Thibodeaux Planning Meeting • Review Archdiocese of New Orleans Consortium/Houma Thibodeaux Model • Archdiocese of New Orleans/Houma Thibodeaux and FSC Team Roles and Responsibilities • Communication Plans • Technical Support & handoff for Member Districts • Implementation Review/Project Timelines

  4. AgendaDestiny Planning Meeting • Centralized System • Managing Patrons • Data Discussion • Training Needs • Project Timeline

  5. Lincoln Elementary Washington Elementary Roosevelt Elementary Creekside Middle Prairiewood Middle Central High School Home Archdiocese of New Orleans Server Host OverviewCentralized System Destiny Destiny

  6. ConsiderationsCentralized System • Single Database to Maintain and Backup – Archdiocese of New Orleans • Centralized Records • Z-Source Capability – Recommend to identify 5 for initial set up for member districts • Optional Web-Based Access • Uses port 80 inbound • SSL available (port 443) • Super Admin & District Functionality

  7. Sample Consortium Home Page

  8. District Welcome PageCentralized System

  9. AgendaDestiny Planning Meeting • Centralized System • Managing Patrons • Data Discussion • Training Needs • Project Timeline

  10. Super Administrator and Destiny AdministratorManaging Patrons • Super Administrator can install and manage all member districts at the consortium level and maintains database • Destiny Administrator has all permissions at member districts • Is able to: • Create sites • Set district policies • Post district-wide notifications • Create & modify Access Levels at the District Level • View all jobs run within the district • Trained during tech training Hierarchy Super Administrator Destiny Administrator Site Administrator Library Administrator Staff Teacher Patron (Student) Guest(Not logged-on)

  11. Access LevelsManaging Patrons • Access Levels are groupings of permissions. • Destiny comes with several pre-defined Access Levels. • Users are granted permissions to do certain tasks by assigning an Access Level in the patron record . • Logged-on users have increased empowerment tools. • Prior to on-site training, the appropriate access levels need to be set up for those that will be attending. • Access Levels can be created and modified at the site level by the Site Administrator. Access Levels and Hierarchy Site Administrator Library Administrator Staff Teacher Patron (Student) Guest (Not logged-on)

  12. Guest User Managing Patrons

  13. Logged-In User Managing Patrons

  14. Logged-In User Managing Patrons

  15. Faculty .csv Students .csv Update ProcessManaging Patrons Destiny Server Destiny Updates Patrons according to District ID Assigns Patrons according to SIS Building code Student Information System (SIS)

  16. *Barcode *SiteShortName *DistrictID *LastName FirstName MiddleName Nickname Gender PatronType AccessLevel Status CardExpires GradeLevel Homeroom GraduationYear IsTeacher AcceptableUse PolicyOnFile BirthDate UserName Password (2) Email Patron Data FieldsManaging Patrons Destiny Pre-Defined Fields (2) AddressLine1 (2) AddressLine2 (2) City (2) State (2) ZipCode (4) PhoneNumber UserDefined1 UserDefined2 UserDefined3 UserDefined4 UserDefined5

  17. Recommended Patron Field Export For the staff records: • Barcode, SiteShortName, DistrictID, Lastname, Firstname, Middlename, Gender, PatType,  • PatStatus, Birthdate, Emailaddr, Address, City, State, Zip For the student records: • Barcode, SiteShortName, DistrictID, Lastname, Firstname, Middlename, Nickname, Gender, • PatType, PatStatus, GradeLvl, Homeroom, Period, Gradyear, Birthdate, Emailaddr, Address, • City, State, Zip, Phnnumber * Homeroom identified for distribution of library notices

  18. Patron Clean-UpBibliographic Data Destiny If the StudentID is in the current system: • Only duplicate patrons without transactions will be deleted. • The remaining duplicate barcodes will have the prefix “OLD” added and marked Inactive. If the StudentID is not in the current system: • All patrons without transactions will be deleted. • The remaining records will have the prefix “OLD” added in front of the barcode and marked Inactive. MARC Enhancement Conversion Options

  19. AgendaDestiny Planning Meeting • Centralized System • Managing Patrons • Data Discussion • Training Needs • Project Timeline

  20. Lincoln Elementary (LES) Washington Elementary (WAS) Roosevelt Elementary (RES) Creekside Middle (CSMS) Prairiewood Middle (PWMS) Central High School (CHS) Centralized RecordsBibliographic Data Single Shared MARC Record for each unique title Destiny Copies associated by Site Short Name

  21. Local Tags 521, 526, 590-599, 658, 690-699, 790-799, 856, 900-999 Site Specific Site Specific Subject Reading Program Info Copy (852 tag) Barcode Location Call number Purchase price Copy Notes Title, Local & Copy TagsBibliographic Data Title (Centralized, Shared MARC Record) Title Author Publication Info Subject Material Type Standard Type Physical Description Annotations No Data to Convert Go to Follett Remote Data Conversion and Services MARC Entry

  22. MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record Alliance Plus Records Matching on EnhancementBibliographic Data During Enhancement, your records are each compared to our Alliance Plus database. When a match is made, the record is replaced except for the local tags. If no match is found, the record is not enhanced. Your MARC Record Follett Software MARC Database

  23. Matching on EnhancementBibliographic Data Strict Matching Criteria (Please refer to your MARC Enhancement Description document) Standard Number* Title Material Type Matching criteria applied to all records Minimal risk of incorrect matches in typical MARC database. Presence of Standard Number results in greater certainty of matches First, Standard Number Author Material Type Next, * In cases that records do not contain standard numbers, the use of expanded record matching rules may be beneficial and can be requested. Conversion Options

  24. Data Conversion Options Customer Conversion No Data Services Data Services after Conversion, before Implementation Data Services before Conversion (Circ/Cat, Athena, InfoCentre) Enhancement Post Implementation Follett Software Company Conversion Data Services Conversion Offline Circulation Options Follett Remote Dual Circulation

  25. Data File TypesBibliographic Data File with Stats/Trans (.all file) Microlif file (.001) Statistics and Transactions Fines Categories Circulation Stats Circulation Types Copy Status (missing, etc.) Current Holds & Reserves Previous Checkout Information Barcode Filters + Title Record Local Tags Copies Patron Info No Statistics or Enhancement Go to Conversion Options No StatisticsGo to Enhancement Statistics

  26. Data Services MICROLIF (.001) MARC Records .ALL File PackagedData File Customer ConversionData Services before Conversion Export MARC records www.follettsoftware.com Place .ALL file on Destiny server Upload to Follett Import data into Destiny Data Enhanced Conversion Utility Install on each server Import Enhanced data into old system Download Conversion Utility Run Utility to generate .ALL Current Database Destiny Stop Circulating Stop Cataloging Back to Conversion Options Continue to Follett Remote

  27. Offline CirculationBibliographic Data Follett Remote For circulation while moving to Destiny, it is best to use the unique patron ID that you will be using in Destiny

  28. Offline CirculationBibliographic Data Follett Remote Destiny Site-based Day1.txt Follett Remote Place on one circulation Desk per site Day2.txt Day3.txt Skip Dual CirculationGo to Matching on Import No DataGo to Training Back to Conversion Options Dual Circulation

  29. MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record MARC Record All MARC Records Matching for Roll-upBibliographic Data During Roll-up, incoming records are compared to existing records in database. When a match is made, the record with the most access points survives and all copies from both records are associated with the surviving record. If no match is found, the record is added. MARC Record Destiny Database

  30. Matching for Roll-upBibliographic Data Strict v. Relaxed Matching Rollup Criteria Lower percentage of matches Substantially decreases undesired rollup Manual merging after data load Standard Number Title Material Type Author Publish Date Strict Matching* * In cases that have typographical errors in the author tag, the Strict Matching option can be set to ignore the author. Greater percentage of matches Possibility of undesired rollup Undesired rollups would have to be re-cataloged *If standard number is present in both records, it must match. • Standard Number (not required)* • Title • Material Type • Author • Publish Date Relaxed Matching

  31. AgendaDestiny Planning Meeting • Centralized System • Managing Patrons • Data Discussion • Training Needs • Project Timeline

  32. Destiny TrainingTraining • Technical Training Consortium (Required) Format: 3 hour on site Attendees: Consortium Technical Team, Super Administrator, Project Lead • Technical Training Member Districts (Required) Format: eLearning Attendees: District Tech, Destiny Admin, Library Media Specialist

  33. Destiny TrainingTraining • Site Administrator Training (Required) Format: Instructor Led WebEx 90 minutes – over a week period Attendees: Site Administrators • On-Demand eLearning (3 Days Post AoD) www.follettsoftware.com • On-Site Fundamentals Training (Consolidated) Format: 2 days Attendees: District end-users • Esssentials Webinar Format: 3 ½ hours Webinar Attendees: District end-users

  34. Optional Destiny TrainingTraining Needs District Level Users Patrons Library Materials Library Materials-Authority Reports Report Builder District Users Intended for users that will be performing functions or managing resource information at district level. * Recommend taking the Library Materials multiple site member districts

  35. AgendaDestiny Planning Meeting • Centralized System • Managing Patrons • Data Discussion • Training Needs • Project Timeline

  36. Add Ons Annual Subscriptions Services: Per year

More Related