Data Migration

Total Page:16

File Type:pdf, Size:1020Kb

Data Migration Data Migration DISSECTING THE WHAT, THE WHY, AND THE HOW 02 Table of Contents The What 04 What Is Data Migration? 05 Types of Data Migration 05 Database Migration 05 Application Migration 05 Storage Migration 06 Cloud Migration 06 The Why 07 Situations That Prompt Data Migration 08 Challenges in Data Migration 08 1. The Complexity of Source Data 08 2. Loss of Data or Corrupt Data 08 3. Need for In-Depth Testing and Validation 08 Factors that Impact the Success of a Data Migration Process 09 Is Your Migration Project Getting the Attention It Needs? 09 Thoroughly Understand the Design Requirements 09 Budget for the Field Expert 10 Collaborate with the End Users 10 Migration Isn’t Done in OneGo 10 Backup Source Data 10 Migration Doesn’t Make Old Systems Useless 11 Plan for the Future 11 The How 12 Data Migration Techniques 13 Extract, Load, Transform (ETL) 14 The 7 R’s of Data Migration 14 Data Migration Tools 14 Finding the Right Migration Software – Features to Consider 15 Easy Data Mapping 15 Advanced Data Integration and Transformation Capabilities 15 Enhanced Connectivity 15 Automated Data Migration 15 Planning to Migrate? Steps to A Successful Enterprise Data Migration 16 1. Design a Strategy 16 2. Assess and Analyze 16 3. Collect and Cleanse Data 16 4. Sort Data 17 5. Validate Data 18 6. Migrate 19 Conclusion 20 Astera Centerprise – Making the Data Migration Process Painless 21 About Astera Software 22 03 Summary With data of varying formats pouring in from different systems, the existing system may require an upgrade to a larger server. Data migration enables organizations to expand their data store and management capabilities and make full use of data to drive business decisions. It is a widely used process of moving data, and almost every organization undertakes one at some point. This eBook will give you a deeper insight into the data migration process. It will further discuss why this process is essential for organizations, the challenges they might encounter during the process, and finally list down the techniques and tools that can simplify and streamline data migration. www.astera.com 04 The what Know the Basics www.astera.com 05 What Is Data Migration? According to the International Data Corporation (IDC), data migration represents 60% of any large enterprise IT project. But what is it? Simply put, it refers to the data transfer between different types of file formats, databases, and storage systems. However, ‘transfer’ is not the only aspect of data migration methodology. If the data is diverse, the migration process includes mappings and transformations between source and target data. Above all, data quality must be assessed before migration to ensure a successful implementation. The success rate of any data migration project is directly dependent on the diversity, volume, and quality of data being transferred. Types of Data Migration Data migration can be broadly categorized into four types: Database Migration This type of migration involves moving data between two database engines. However, when the original data changes, it simultaneously affects the data language or protocol. The change is reflected in the application layer as well. Database migration modifies data without modifying the schema. The circumstances that demand this type of migration include: • When the database software requires an update • To migrate a database to the cloud • In case the organization needs to change database vendors It requires careful planning and testing as there are several small tasks involved in the process, such as determining the storage capacity of the target database, testing applications, and ensuring data confidentiality. Application Migration This type of migration occurs when an organization switches from one platform or vendor application to another. Each application has a unique data model. Moreover, applications are not portable. There- fore, the operating systems, virtual machine configurations, and management tools of each application can be different in the development and deployment environment. These factors can contribute to the complexity of the migration process. Introducing middleware prod- ucts in the process simplifies it; as they help bridge the technology gap. www.astera.com 06 Storage Migration The process deals with moving data from one storage system to another, such as a hard disk or the cloud. The need for storage migration arises due to technology upgrades. It is easy to implement data management features like data validation, cloning, reducing corrupt or old information, etc. during this process. In addition, storage migration enables cost-effective scaling and faster performance. Cloud Migration Moving to the cloud ensures scalability, requires fewer storage resources, and is cost-effective and therefore, cloud migration has become one of the latest trends in the data management industry. In cloud migration, an organization’s complete or partial information assets, applications, or services are deployed to the cloud. The cloud’s firewall protects the migrated data. www.astera.com 01 07 The why Reasons for Migrating Data www.astera.com 08 Situations That Prompt Data Migration The most common reason for migration is the need to move data to a new system to scale up and accommodate volume growth. However, other circumstances may also prompt organizations to opt for a data migration project. The reasons include: • To replace legacy systems that are unable to keep up with the evolving performance requirements of the organization. • To reduce storage footprint by migrating to a system that consumes less power and space. Consequently, cutting down the operational costs. • To stay competitive by adopting state-of-the-art technologies, paving the path for data migration. • To prepare a disaster recovery plan; as data migration can help create a secure. • To transfer data to the cloud, eliminating the cost of on-premise IT infrastructure. Challenges in Data Migration Migrating enterprise data from one system to another is always challenging, especially when you have to move millions of records across systems. To help simplify your data migration process, we’ve identified the following most common data migration challenges you could face and how to avoid them: 1. The Complexity of Source Data One of the main challenges in data migration is the complexity of source data. Often, you’ll have to perform data integration on the source data to work through any intricacies. For example, if you were using a legacy data storage system, then you will have to perform data transformation to make the data compatible with the target system. 2. Loss of Data or Corrupt Data While migrating data from one system to another, you might face data loss or corruption. To tackle this issue, make sure that the number of source records matches with the number of migrated records. Various tools are available in the market that can help you authenticate the migrated data. 3. Need for In-Depth Testing and Validation For complex data migrations that involve thousands of records, the cost of failure is simply too high. Therefore, the need to perform in-depth data validation and testing cannot be ignored. Keep in mind any events that could have affected data quality. Also, test a large data volume to assure quality. It’s recommended to pull at least 10 to 20 percent of your data to make sure you include an extensive range. www.astera.com 09 Factors that Impact the Success of a Data Migration Process A fully functional data migration process must include the following considerations: Is Your Migration Project Getting the Attention It Needs? Selecting a new enterprise-wide system is a strategic business undertaking that deals with new technol- ogies and professionals. Migration is usually a small part of a much bigger project. An average business typically focuses on system configuration and other technicalities rather than ensuring the data that will populate the new system is fit for purpose. Holistically speaking, out of the plethora of tasks, data migration falls low on the list of priorities by a management that consider it to be a simple task of transferring data, and does not find the high costs and administrative burden justifiable. Thus, data migration, the resources it requires as well as the diffi- culty of the task is often underestimated and put on the backburner until it’s too late. Make sure that doesn’t happen with you. Holistically speaking, out of the plethora of tasks, data migration falls low on the list of priorities by a management that consider it to be a simple task of transferring data, and does not find the high costs and administrative burden justifiable. Thus, data migration, the resources it requires as well as the difficulty of the task is often underestimated and put on the backburner until it’s too late. Make sure that doesn’t happen with you. Thoroughly Understand the Design Requirements Firm grasp of the design requirements is critical, namely migration priorities and schedules, replication and backup settings, and capacity planning. A simple miscalculation in this area can have lasting repercussions that may impact the cost. This is also the stage where the IT department decides which migration strategy is suitable for the project – Trickle or Big Bang. Selecting one that suits you best is highly subjective to the firm’s existing data and future requirements. Let’s have a look. Big Bang – This type of migration initiates and completes full transfer within a limited time frame. Expect some downtime as the data moves and processes, however the project execution is rather quick. Trickle – This migration strategy conducts the project in multiple phases. The target and source systems run simultaneously, which keeps the migration running in real-time. This type of migration is more complex and time-consuming as compared to Big Bang, however it takes lesser downtime and eliminates operational efficiencies.
Recommended publications
  • Install and Setup Guide for Cisco Security MARS Release 5.3.X March 2008
    Install and Setup Guide for Cisco Security MARS Release 5.3.x March 2008 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Customer Order Number: Text Part Number: OL-14672-01 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Unisys to AWS Reference Architecture
    Unisys to AWS Reference Architecture Astadia Mainframe-to-Cloud Modernization Series Unisys to AWS Reference Architecture Abstract In businesses today, across all market segments, cloud computing has become the focus of current and future technology needs for the enterprise. The cloud offers compelling economics, the latest technologies and platforms, and the agility to adapt your information systems quickly and efficiently. However, many large organizations are burdened by much older, previous generation platforms, typically in the form of a mainframe computing environment. Although old and very expensive to maintain, the mainframe platform continues to run the most important information systems of an organization. The purpose of this reference architecture is to assist business and IT professionals as they prepare plans and project teams to start the process of moving mainframe-based application portfolios to Amazon Web Services (AWS). We will also share various techniques and methodologies that may be used in forming a complete and effective Legacy Modernization plan. In this document, we will explore: Why modernize a mainframe The challenges associated with mainframe modernization An overview of the Unisys mainframe The Unisys to AWS Reference Architecture An overview of AWS services A look at the Astadia Success Methodology This document is part of the Astadia Mainframe to Cloud Modernization Series that leverages Astadia’s 25+ years of mainframe platform modernization expertise. © 2017 Astadia. Inc. - All rights reserved. 12724 Gran Bay Parkway, Suite 300 Jacksonville, FL 32258 All other copyrights and trademarks the property of their respective owners. Unisys to AWS Reference Architecture Contents Introduction ............................................................................................................................ 1 Why Should We Migrate Our Mainframe Apps to AWS? ........................................................
    [Show full text]
  • Data Migration
    Science and Technology 2018, 8(1): 1-10 DOI: 10.5923/j.scit.20180801.01 Data Migration Simanta Shekhar Sarmah Business Intelligence Architect, Alpha Clinical Systems, USA Abstract This document gives the overview of all the process involved in Data Migration. Data Migration is a multi-step process that begins with an analysis of the legacy data and culminates in the loading and reconciliation of data into new applications. With the rapid growth of data, organizations are in constant need of data migration. The document focuses on the importance of data migration and various phases of it. Data migration can be a complex process where testing must be conducted to ensure the quality of the data. Testing scenarios on data migration, risk involved with it are also being discussed in this article. Migration can be very expensive if the best practices are not followed and the hidden costs are not identified at the early stage. The paper outlines the hidden costs and also provides strategies for roll back in case of any adversity. Keywords Data Migration, Phases, ETL, Testing, Data Migration Risks and Best Practices Data needs to be transportable from physical and virtual 1. Introduction environments for concepts such as virtualization To avail clean and accurate data for consumption Migration is a process of moving data from one Data migration strategy should be designed in an effective platform/format to another platform/format. It involves way such that it will enable us to ensure that tomorrow’s migrating data from a legacy system to the new system purchasing decisions fully meet both present and future without impacting active applications and finally redirecting business and the business returns maximum return on all input/output activity to the new device.
    [Show full text]
  • SQL Developer Oracle Migration Workbench Taking Database Migration to the Next Level Donal Daly Senior Director, Database Tools Agenda
    <Insert Picture Here> SQL Developer Oracle Migration Workbench Taking Database Migration to the next level Donal Daly Senior Director, Database Tools Agenda • Why Migrate to Oracle? • Oracle Migration Workbench 10.1.0.4.0 • SQL Developer Migration Workbench • New Features • New T-SQL Parser • Additional Migration Tools • Demonstration • Conclusion • Next steps • Q&A Why Migrate to Oracle? What is a migration? • A Migration is required when you have an application system that you wish to move to another technology and/or platform • For example, you could migrate your application from: • Windows to Linux • Mainframe to UNIX • Sybase to Oracle • Visual Basic to Java • Microsoft SQL Server to Oracle 10g on Linux • Microsoft Access to Oracle Application Express Why Migrate to Oracle? Business Drivers for Migration • Consolidation • Many Platforms to one • Hardware and Software Consolidation • Centralized IT Management • Reliability/Scalability/Performance • Core competencies of Oracle • Key Customer Concerns • Open Standards • JAVA, XML, SOAP Why Migrate to Oracle? Oracle’s Migration Strategy • Provide cost effective migration solutions to the Oracle platform • Migrate entire application(s) & database(s) • Minimize migration effort by using • Proven tools & methodology • Services to support complete project lifecycle Lowest Total Cost of Adoption Why Migrate to Oracle? Migration Tools Support 1. Evaluation 8. Project 2. Assessment Support 7. Production Migration Lifecycle 3. Migration 6. Customer Acceptance 4. Testing 5. Optimization Oracle
    [Show full text]
  • Data Migrations in a World Where Most Projects Fail Or Significantly Exceed Their Budgets
    Put Your Data First or Your Migration Will Come Last A discussion on how to be successful at data migrations in a world where most projects fail or significantly exceed their budgets. 1 www.lumendata.com www.oracle.com/us/products/middleware/data-integration/enterprise-data-quality/overview/index.html The only constant in business today is that change is inevitable. This change can Why should I manifest in many forms in a business such as New system implementations (ERP, CRM, Loyalty, HR, etc.) care about Large system upgrades (ERP, CRM, HR, etc.) Mergers & acquisitions data Divestitures Migrating to the cloud migration? A new (or expanded) master data management initiative A new (or expanded) business intelligence/data warehousing project A big data initiative A multi-channel program System rationalization/retirement Responding to new regulations New management The common thread across these disparate initiatives is a strong need for data migration. Typically when a business person thinks about data migration, they think, This sounds like an IT problem, and they move on. The reality is that without strong business support and a proven approach for the data migration associated with the above mentioned initiatives, you have a higher probability of failure than of success. More than 80% of data migration projects run over time and/or over budget. Cost overruns average 30%. Time overruns average 41%. Bloor Group Did you know? 83% of data migration projects either fail or exceed their budgets and schedules. Gartner 2 www.lumendata.com www.oracle.com/us/products/middleware/data-integration/enterprise-data-quality/overview/index.html The fact that over 80% of projects involving data migration fail is a sobering Why is there statistic.
    [Show full text]
  • The KEEP Emulation Framework
    Proceedings of the 1st International Workshop on Semantic Digital Archives (SDA 2011) The KEEP Emulation Framework Winfried Bergmeyer Computerspielemuseum, Berlin, Germany ([email protected]) Abstract. As part of the overall KEEP Project the task of the Emulation Framework (EF) is to provide the emulation environments required for this purpose. In a very simple and comprehensible way the users can employ emulations for the representation and the performance of both digital objects in obsolete data formats and applications for antiquated computer systems. The virtual reconstruction of original playback environments can reproduce the original look-and-feel-qualities. By means of this approach audiences unfamiliar with the very concept of emulations can employ them in a private context as well as in an institutional framework. Thus a digital object stored in an archive can be rendered in that digital environment best suited to it without the time-consuming procedure of having to equip the computer on which it is to be run with emulation-specific configurations. The range of applications is huge: In addition to allowing games to be played with an original atmosphere it encompasses e. g. access to data in obsolete formats or data migration with original software. The decisive factor from the point of view of conservation is that the original stream is being employed. There are almost no limits as to the scope of emulators that can potentially be used inside EF. The first release will support the following platforms: x86, Commodore 64, Amiga, BBC Micro and Amstrad/Schneider CPC. Keywords: KEEP, Emulation, Emulation Framework, Virtual Machine, Transfer Tool 1 Emulation as a concept of conservation The advantages of emulation as an alternative form of preservation (if compared to data migration) are numerous: Any strategy of preservation has to guarantee the permanence of the upkeep of the digital object as well as that of its accessibility1.
    [Show full text]
  • Migrating Applications Running Relational Databases to AWS Best Practices Guide
    Migrating Applications Running Relational Databases to AWS Best Practices Guide First published December 2016 Updated March 9, 2021 Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. Contents Introduction .......................................................................................................................... 1 Overview of Migrating Data-Centric Applications to AWS ................................................. 1 Migration Steps and Tools .................................................................................................. 2 Development Environment Setup Prerequisites ............................................................. 3 Step 1: Migration Assessment ......................................................................................... 4 Step 2: Schema Conversion ...........................................................................................
    [Show full text]
  • AS/400 Modernization
    WHITE PAPER AS/400 Modernization MIGRATION TO CLOUD Abstract Large enterprises often run mission-critical workloads on AS400 applications that are older, difficult to maintain and expensive to operate. Today, many enterprises want to migrate their workloads – including their AS400 portfolios – to cloud to gain higher scalability, agility and cost benefits. This white paper examines the challenges of modernizing AS400 workloads along with the common AS400 migration approaches and useful architecture patterns that ensure maximum benefit from cloud migration. This paper will be useful to IT professionals and business decision-makers in organizations looking to either migrate or modernize their existing AS400 or other legacy workloads to cloud. Contents 1. Abstract 1 2. Introduction 3 2.1. Infosys Cost Assessment Framework- Upgrade or migrate? 3 3. AS400 migration to cloud 5 3.1. Migration challenges 5 3.2. Migration approaches 6 3.2.1. Re-hosting 6 3.2.2. Re-engineering batch job migration 6 3.2.3. Re-engineering cloud native applications 8 4. Renew AS400 applications 9 4.1. RPG upgrade 9 4.2. DB2 400 upgrade 9 4.3. DevOps on AS400 10 5. Conclusion 11 6. About the author 11 7. References 11 External Document © 2017 Infosys Limited External Document © 2017 Infosys Limited 2. Introduction for these applications becomes obsolete, a customized approach that reduces TCO, it can impede business growth. From unlocks insights from hidden data and The AS400 (also known as the ‘IBM iSeries’ a modernization perspective, cloud increases system agility while delivering and ‘IBM i’) is a previous generation mid- technologies can significantly improve consistent business value.
    [Show full text]
  • Migration Strategy for Relational Databases AWS Prescriptive Guidance Migration Strategy for Relational Databases
    AWS Prescriptive Guidance Migration strategy for relational databases AWS Prescriptive Guidance Migration strategy for relational databases AWS Prescriptive Guidance: Migration strategy for relational databases Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. AWS Prescriptive Guidance Migration strategy for relational databases Table of Contents Introduction ...................................................................................................................................... 1 Overview ................................................................................................................................... 1 Phases of migration ........................................................................................................................... 2 Phase 1: Prepare ................................................................................................................................ 3 Identify dependencies ................................................................................................................. 3 Qualify workloads .....................................................................................................................
    [Show full text]
  • Migration Agent Migration Migration Agent Enables a Smooth, Predictable Migration from Any Legacy LIMS to Thermo’S Advanced LIMS Solutions
    Migration Agent Migration Agent enables a smooth, predictable migration from any legacy LIMS to Thermo’s advanced LIMS solutions Migration Agent The professional solution for LIMS migrations Challenge latest LIMS solutions. It combines a clearly Screenshot, from the ETL software used to migrate defined and documented migration process the physical data, Migrating from one LIMS to another is using an extract, transform and load (ETL) showing the graphical often a necessary step to take advantage tool specifically configured for Thermo method for mapping of new technology and product features. technology. Complete documentation and the fields between Changing business needs and concerns validation services for companies operating the source and target regarding ongoing system support, in regulated industries are also available as databases. Migration maintenance costs, and compliance also part of the offering. Agent includes a number drive the decision to migrate to another of QA-tested standard LIMS. Unfortunately LIMS migration is no Migrate in Less Time and at a Lower Cost data mappings and simple task, and without proper planning Thermo’s global services team is the transformations. and data handling, it can be disruptive to world’s largest laboratory informatics users, the laboratory and the business. In services group, and leading companies addition, companies in regulated industries worldwide have relied on Thermo’s global face additional migration challenges with services team for successful migration respect to secure data management and projects. A dedicated Tactical Thermo validation of the new system. Migration Team follows the defined 6-step Migration Agent process and begins by Thermo’s Solution conducting a gap analysis of the source and target systems.
    [Show full text]
  • Data Migration Made Simple with File Dynamics Eliminate the Complexities of Migrating Data Between Disparate Networks with Micro Focus® File Dynamics
    Flyer Information Management and Governance Data Migration Made Simple with File Dynamics Eliminate the complexities of migrating data between disparate networks with Micro Focus® File Dynamics. Easy to use, flexible and engineered to deliver consistency across operating systems, Cross­Empire Data Migration is a unique capability that can save thousands of dollars in time and effort. File Dynamics at a Glance: Migrating Data Wisely Cross-Empire Data Migration Your network storage system holds some Moves Data with Integrity Cross-Empire Data Migration: ■ of your organization’s most valuable assets: Cross­Empire Data Migration is a subsystem Move from a Micro Focus network to Microsoft user and group files. File system decisions within File Dynamics that migrates file sys- network quickly and automatically. are strategic to your IT operation, and if your tem data between Micro Focus and Microsoft plans include moving files from one operating ■ A Comprehensive Solution: networks, including their corresponding stor- system to another, you need to understand File Dynamics is a complete file management age infrastructures and identity and secur ity solution. Automate the full lifecycle of user and that maintaining all rights, permissions and file frameworks. group storage based on policies you set. metadata during the move is essential to your organization. Without these you put the contin- Through a wizard interface, Cross­Empire ued success of your file storage, access and Data Migration quickly and automatically The objective of the Cross-Empire compliance at risk. Ensuring the data is con- moves data based on a variety of scenarios, sistent from the old environment to the new which include moving data for multiple users Data Migration subsystem is doesn’t have to be difficult if you do it correctly.
    [Show full text]
  • Challenges of Metadata Migration in Digital Repository: a Case Study of the Migration of DUO to Dspace at the University of Oslo Library
    Do Van Chau ________________________________ Challenges of metadata migration in digital repository: a case study of the migration of DUO to Dspace at the University of Oslo Library Supervisor: Dr. Michael Preminger Oslo University College Faculty of Journalism, Library and Information Science 1 DECLARATION I certify that all material in this dissertation which is not my own work has been identified and that no material is included for which a degree has previously been coffered upon me. …………Do Van Chau……… (Signature of candidate) Submitted electronically and unsigned 2 ACKNOWLEDGEMENTS This work is finished with the supports from many persons in DILL program and at University of Oslo Library. I am very grateful for valuable advice and enthusiasm from my supervisor, Dr. Michael Preminger. He has taken time and effort to read and comment on my work. I would like to take this chance to thank all librarians and technical staffs at University of Oslo Library, librarians at Oslo University College and University of Cambridge Repository for sharing thoughts and comments in the questionnaires. I also express deepest attitude to all professors in DILL program who have given interesting lessons for me. In particular, I would like to say thank you to Prof. Ragnar Nordlie for critical comments on my thesis during the seminars. Finally, special love is given to my family and friends who are always beside me and give strong encouragement to me during the study. 3 ABSTRACT This work is a study of challenges in the metadata migration, generally and with DUO as a case, thereby defining the appropriate strategy to convert metadata elements of DUO to Dspace in the migration project at UBO.
    [Show full text]