Wellington City Libraries Case
THE LIBRARY CORPORATION CORPORATION THE LIBRARY Solutions that Deliver Consequently, TLC•Cloud Services opened up Implementation Meanwhile, technical service specialists were Recommendation Additionally, the Library was aware of the underlying geographic access for TLC to oer hosting services in completing similar tasks from their own homes: making technical architecture. The Library had been using Linux Part of choosing the alternative option meant the all OCI data regions, globally. In the co-location model, sure the reports worked, the databases were connected, Two details were top of mind for WCL in their servers in their operations and continuing in a Linux Library would coordinate between all of the entities to TLC customers would have needed to connect to SIP connections were established, and so on. Similarly, decision-making process: the technical compatibility environment, which is what was oered with the safely move data from the previous vendor into the either the Denver, CO, or Ashburn, VA, hosting facilities the Smart Council team was conrming the network that a new hosting provider could oer within the TLC•Cloud Services option, would be advantageous for cloud. At this point in the spring and early summer, respective of their ILS product. connectivity and trac, plus checking the integrations existing library foundations, and how the solution the Library in terms of maintaining servers, diagnosing teams in Wellington were starting to return to their issues, and general application knowledge. between OCI into the City's AWS environment. TLC expanded into the international market, oering a would work in practice with a new data hosting libraries and oces while the TLC teams were still closer network endpoint and decreased global network partner.
[Show full text]