Approved unanimously by RACL membership (April 17, 1998)
Revised and approved (October 21, 1998)
Revised and approved (April 16, 1999)
Revised and approved (March 11, 2005)
Revised and approved (November 12, 2010)

Revised and approved (October 13, 2017)

  1. The Regents Academic Committee on Libraries (RACL) establishes the GIL Coordinating Committee for the GALILEO Interconnected Libraries (GIL) project. The UGA Service Site provides application and technical support (GIL Technical Support) for all libraries except for Georgia Tech. GIL uses the University System of Georgia Information Technology Services (ITS) Helpdesk for support and emergency requests. 
    1. The RACL Executive Committee will provide oversight of GIL
    2. The following are members of the GIL Coordinating Committee:
      1. RACL chair-elect, who will chair the Coordinating Committee
      2. GIL Functional Committee chairs
      3. GIL Users’ Group (GUGM) chair and chair-elect
      4. UGA Service Site Liaison
      5. GIL/GALILEO Staff (Non-voting)
        1. Manager of GIL Technical Support
        2. Alma Project Director
        3. Executive Director of GALILEO
        4. Additional resources as needed (Liaisons to committees; subject matter experts)
    3. The GIL Coordinating Committee members will be appointed as follows:
      1. RACL chair-elect (elected annually by RACL)
      2. GIL Functional Committee chairs are selected by the RACL chair-elect, with the advice and consent of the RACL Executive Committee
      3. GUGM chair and chair-elect are selected by the RACL chair-elect, with the advice and consent of the RACL Executive Committee
      4. UGA Service Site Liaison is selected by the UGA University Librarian and Associate Provost
    4. The duties of the GIL Coordinating Committee are as follows:
      1. Recommend to the RACL Executive Committee the GIL policies and procedures.
      2. Review and discuss issues that arise from implementation or change of the various GIL modules.
      3. Address any issues with other resource-sharing activities that affect GIL and make recommendations as appropriate.
      4. Apprise RACL when no consensus can be reached on the resolution of a problem.
      5. Coordinate with GUGM to plan an annual GIL Users’ Group meeting
      6. Provide advice and recommendations on the implementation and maintenance of GIL support services
    5. The duties of the GIL Functional Committees ( Acquisitions and ERM; Assessment; Cataloging; Fulfillment; OPAC/Discovery; Special Collections) are:
      1. Follow the Guiding Principles for the Alma Implementation as Guiding Principles of the GIL Committees:
      2. Meet monthly, virtually (at minimum)
      3. Meet annually, in person
      4. Maintain/Improve functional documentation in GIL Documentation Wiki
      5. Recommend policies, standards, and best practices
      6. Review monthly Alma/quarterly Primo release notes and determine if testing/communication/documentation is needed
      7. Identify functionally specific trainings as needed
      8. Submit functionally specific feature requests to vendor as needed
      9. Provide suggestions and ideas for the GUGM meeting
      10. Share information
      11. Make recommendations regarding the functional area(s) to the GIL Coordinating Committee, RACL or other groups as appropriate
      12. Work on specific projects related to the functional area as tasked by the GIL Coordinating Committee or RACL
      13. Communicate and work with other committees as needed
  1. Library Services / Board of Regents will:
    1. Take advice and recommendations from the GIL Coordinating Committee and/or RACL Executive Committee on the implementation and maintenance of GIL support services
    2. Provide direction to GIL Technical Support on the implementation and maintenance of GIL support services
    3. Coordinate the provision of a Helpdesk to provide a single point of contact, 24 hours a day, seven days a week to receive service requests and to log, track, and resolve support requests in addition to emergency, business interruption, or other production down situations which may occur after hours and on weekends.
    4. Contract for services with third parties as needed.
    5. Develop written agreements as needed in consultation with the GIL Coordinating Committee and/or RACL Executive Committee to be signed by authorized institutional personnel, to ensure equitable and consistent support for all parties involved in the GIL project.
    6. Bill the libraries annually for the cost of software, hardware, support, and maintenance.
  2. The Library Contact at the Client Site will:
    1. Manage their library functions.
    2. Be responsible for the distribution and replication of documentation.
    3. Provide data to GIL Technical Supportas required.
    4. Ensure that local data meets system-wide specifications.
    5. Maintain effective communications about GIL to the local library.
  3. Official Grievances should be submitted only:
    1. When the level of service, the quality of work, the cooperative nature of the relationship or the response time of either a Service Site or the Client site is not acceptable.
    2. After an attempt has been made by all parties involved to “work through” the problem(s), including direct communication with the parties involved.
    3. In writing.
    4. To the Executive Director of GALILEO, with copies to the Manager of GIL Technical Support, and the Chair of the GIL Coordinating Committee.