Metadata Management Tutorial - Meta Integration
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)MetadataManagementTutorialWeb Portal & Data GovernanceUsing erwin Metadata Management(EMM)P a g e 1 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)TABLE OF CONTENTS12Introduction 51.1Conventions used in the tutorial 61.2Setting Up the Tutorial 7About Data Governance and Metadata Management tify data stores & associated design tools 14Understanding This Tutorial’s Enterprise Architecture 16Catalog the Operational Data Stores 16Catalog the Data Processes. 18Harvesting the Finance System Metadata 20Harvest the Accounts Payable model 20Harvest the Accounts Receivable model 334.1Configuration Management 374.2Populate the Published Configuration 384.34.3.14.46From Data Stores and Data Processes To Enterprise Architecture 14Configuration Management 364.2.14.2.24.2.34.2.44.2.55Data and metadata are everywhere! 10MITI’s strategy to support data and metadata management 11Metadata Harvesting 133.14General data and metadata management discussion 10Bringing Model Formats into a ConfigurationSemantic lineage architectureWarehouse dataflow architectureData Flow ArchitectureMetadata Explorer UI3839444949Metadata Explorer UI 50Shapes 50Attachments 52Metadata Search, Browsing and Analysis 545.1Impact of Change Lineage 565.2Data Source Lineage 59Simple Data Governance with Business Glossary 626.1Overview of the Business Glossary features 646.2Creating an abstract Business Glossary 656.2.16.2.26.36.3.16.3.2Create the Business Glossary 65Populate the Business Glossary 66Glossary derived from a Model 72Import the Model 72Create and Populate the glossary 72P a g e 2 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)6.3.37Update the configuration 76More Metadata Analysis 797.1Terminology Usage (Impact) Analysis 807.1.17.2Trace Semantic Usage 80Trace Semantic Definition 857.2.17.38Build Glossary to Glossary Mappings 87Embed the mapping 94Data Governance with Business Glossary 958.1Glossary Semantic Mapping and Term Classification 968.2Extending the Business Glossary with existing metadata 1068.2.18.2.28.3Analyze potential metadata 106Populate the Business Glossary 108Normalization of Terminology 1118.3.18.3.29Preventing redundancy 111Mapping terminology 1128.4More Editing Terminology in the Metadata Explorer UI 1428.5Report Glossary and Report Documenter 152Data Mapping Specifications 1659.1Constructing a data mapping specification 1669.2Simple Load 1679.3Detailed data mapping specifications 1729.3.19.3.2Include business names 174Creating a map 17510 Advanced Business Glossary Workflow 18110.1Overview of the advanced Business Glossary features nfiguring the Glossary for Workflow 18810.2.110.2.210.2.310.2.410.3Glossary WorkflowWorkflow RolesStewardsWorkflow process optionsTerm management dashboardsWorkflow transition buttonsVersionsCategoriesRelationshipsFlexible and optional workflow processConfigure the GlossaryPublished configuration versionDefining groups to support glossary rolesWorkflow Roles188191193196Glossary Workflow 19910.3.1Propose a draft 199P a g e 3 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)10.3.210.3.310.3.410.3.5EditReviewApprove a termPublish20120520620711 Semantic Mapping 20911.2Configuration Architecture Diagram 21311.2.1Annotation 213Appendix A 215P a g e 4 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)1 IntroductionIt is certainly possible to skip through the tutorials, and thus simply glean an“management-level understanding” of erwin Metadata Management (EMM) and its usewithin a metadata management environment. However, it is not recommended that onetry to skip parts of the tutorials and then try to go through later parts. When followingthrough the tutorial sections, it is very important to respect the order of the steps (and theorder sections/labs within each section). The results of preceding tutorials are re-usedand built upon in each successive lesson.In addition, it is important to ensure complete understanding of the conceptualbackground provided in the sections leading up to and supporting the tutorial material.Thus, one should not simply jump into the tutorials with carefully reviewing the conceptspresented in that section.As this document include hand-on tutorials, a great deal of specificity is required. Thisdetail includes specifying particular CASE, ETL, BI, etc., vendor’s tools. While erwinMetadata Management (EMM) environment itself is capable of working with over 100different versions of third-party tools upportedTools.html), it is necessary forthe clarity conciseness of the tutorials to limit the cadre of tools that will be referred to.Please note that it is not necessary to have these tools on-hand to get the full benefit ofthe tutorials. Remember also, though you may intend to use erwin MetadataManagement (EMM) suite of tools with many of the supported third-party tools notspecified in the tutorial, it is still quite valuable to learn the processes, methods and bestpractices presented here. Then one may reuse what one has learned and apply thatknowledge and skill to the particular set of tools that are critical to one’s own enterprise.DisclaimerSome of the features detailed in this document may not apply and/or be available for theparticular erwin Metadata Management (EMM) edition you may have.P a g e 5 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)1.1 Conventions used in the tutorialThe following font conventions will be used throughout the tutorial. User Interface item – NewSubmenu item – New › FolderTerminology item – model content itemName or label reference – Accounts PayableP a g e 6 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)1.2 Setting Up the TutorialThis tutorial currently does not contain a separate orientation on the erwin MetadataManagement (EMM) toolset. Specific examples of how to perform the operationsrequired for this tutorial are provided in the next sections.In order to create this structure in the repository for the tutorial, you will restore a backupthat includes the basic repository structure for the tutorial plus any metadata that youcannot easily replicate. To do so1. Sign in as Administrator2. Go to MANAGE Advanced Metadata Manager3. In the Repository panel on the left right-click on the folder named Configuration andselect Delete.4. Now, right-click on the Repository and select More Restore.P a g e 7 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)5. Click Browse and navigate to the backup at and click More Options Restore.6. Select the following path:C:\Temp\Models \Backups\Data Governance\7. Click Restore8. Refresh the browser.Note how the metadata cataloged in the previous section are reflected in the tutorialrepository structure under the folders Tutorial/Metadata Management.P a g e 8 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)2About Data Governance and Metadata ManagementFigure 1 -Model Connection Diagram for System Metadata Management ExercisesThe above figure represents an overview of the tutorial that this document will lead onethrough. While it appears here to be a fairly complicated diagram, this document willdecompose and will walk one through the data and metadata management conceptsencompassed.The sample metadata represents what would be captured from operational finance basedsystems, including the operational data stores (ODS), warehouse models (DW andDWStaging), Big Data sources, XML messages and business intelligence (BI) data marts.These will be from a variety of data modeling tools or directly from the sourcesthemselves. In addition, a Business Glossary and enterprise conceptual data model(CDM) are also included and mapped to the operational system metadata.P a g e 9 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)2.1 General data and metadata management discussionMetadata management is not an end in and of itself. There has to be real return oninvestment in what can be a very expensive and long term undertaking. The promise interms of having a well architected and interoperable information systems environment iswell understood by most people in the information management community. However,as with any foundation, it must be solid, well thought out, and appropriate to the need. Inorder to have an outrageously successful effort, then, the specific objectives must be veryclearly defined, the organization as a whole must be able to leverage the results of themetadata efforts, and the infrastructure must be able to support all of the many methods,design tools, etc., that an organization is using and will adopt into the future.It has been said many times that “Metadata and Architecture assets will outlive the tools,methodologies, and individuals used to produce them.” Thus, it is imperative that yourmetadata be as independent as possible from a particular tool format, methodology orprocess. Having incredibly valuable and expensive work “locked” into a particular tooland methodology or process can spell doom for any metadata and data managementeffort. Metadata must also be accessible to the widest possible audience within anorganization, in order to conclusively demonstrate to the technical and businesscommunities that metadata is a valuable (and accessible) corporate asset.2.1.1 Data and metadata are everywhere!One of the key reasons seen for integrating and managing metadata across an enterprise isthat, as we know, data is everywhere. The proliferation of different software applicationsthat can accomplish more and more specific tasks, and the incredible cost to develop newones, means that inter-operation, or enterprise application integration, with manydisparate data sources is the only way to provide an integrated enterprise. After decadesof trying, we have given up on the concept that there will be just one data source, virtualor otherwise, and interoperability is now known to be the key to integration. If data mustexist in physically separate data stores, on a diverse array of platforms, then integratedenterprise data architecture will be required to “link” the disparate and possibly redundantdata stores together via well-defined processes. Losing track of these “links” costsorganizations millions of dollars annually, by increasing the risk of system errors,extending application development project timelines, increasing the cost/complexity ofbuilding decision support systems, and countless other ways. The inability to traceinformation across disparate processes and technologies has lead to a lack of trust bybusiness management about the reliability of the content of corporate information.Having to then assure the quality of the information used to make the decision, inevitablycauses delays in key business decision making. Thus is born the need for metadatarepositories, metadata integration and management.P a g e 10 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)What needs to be recognized, though, is that metadata is also everywhere. DataModeling tools abound in an organization, many with their own repositories, just aboutevery application has its own data dictionary, XML carries the metadata with it in themessage or document, and data flow mapping inter-relate all of it together. Thus, thesame difficult lesson applies: the truly effective and future proof way to integrate andmanage this metadata is interoperability and enterprise repository integration. There isnever going a single repository (metadata source), virtual or otherwise, and thus,metadata exchange and repository interoperability are key to metadata integration.2.1.2 MITI’s strategy to support data and metadata managementIn order to succeed, then, one must have a good enterprise repository integrationenvironment. This philosophy is what the erwin Metadata Management (EMM)repository solution and products are based upon. It is an integrated whole that can bridgethe technical and non-technical aspects of metadata, while simultaneously bridging thechasm between the different metadata source and target systems that constitute anymodern information management environment.Metadata is everywhere and erwin Metadata Management (EMM) provides datagovernance metadata repository environment that is agnostic of data modeling toolsource or other data store metadata sources. Including the business glossary, data flowmapping design, semantic mapper and bridges into big data, database technologies,P a g e 11 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)XML, COBOL, etc., erwin Metadata Management (EMM) allows one to manage andanalyze the complete enterprise metadata life cycle across heterogeneous vendors.P a g e 12 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)3 Metadata HarvestingIn order to design, build and maintain a metadata management environment, one mustidentify and catalog the assets in the current environment. In general, this process isbroken into the cataloging of data stores, data processes and conceptual models.P a g e 13 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)3.1From Data Stores and Data Processes To Enterprise Architecture3.1.1 Identify data stores & associated design toolsWith that overview of the erwin Metadata Management (EMM), we may now return tothe general metadata management discussion. One of the first steps in populating therepository and thus building up one’s metadata management environment is an inventoryof the metadata in your organization.For the purposes of this document, the specific methodology used is immaterial. Instead,from the MIR perspective it is most important to analyze where the metadata resideswhat technology is required to extract it (and ultimately forward-engineered)what process or set of steps must be followed in order to ensure proper extractionAs was stated in previous sections, metadata is everywhere within any moderninformation management organization. Also, there are many repositories that arerequired to exist for each technology environment in order for it to perform properly. Inorder for these sources and targets to provide a coherent and coordinated environment,this metadata must be exchanged.3.1.1.1 Interface technology issuesFundamental to the repository is the ability to exchange metadata among the disparatesources and targets that exist in the enterprise and those that will be adopted into thefuture. The following table addresses how metadata is extracted from and returned to thedifferent sources.MetadataSource /TargetTool NameandDescriptionFigure 2 -POCPoint ofContact /Steward ntents, cumentation/SupportedTools.htmlfor specificdetails contents, cumentation/SupportedTools.htmlfor specificdetails bytarget)Classifying metadata sources and targetsP a g e 14 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)Depending upon the particular source, there will most likely be different technologyrelated issues to consider when extracting metadata. Generally these issues revolvearound the type of interface required by the particular tool vendor. These interfaces maybe divided into three categories:Issues related to these different technology approaches are summarized in the followingtable and are also documented on the website:Metadata Interface TypeDirect applicationprogramming interface(API)Examples Repository bridges(e.g., erwin Mart)Import/Export file format Native File FormatFigure 3 -Specific text or binaryformats CSV text filesdumping tables fromrepositories XML files (standardslike OMG UML orCWM XMI orproprietary Binary files of designtools or repositories,e.g., IBM InforsphereData Architect .DBM,or erwin Data Modeler.ERWIN. Text files, possiblystructured in alanguage, e.g., erwinData Moder .XML orEmbarcaderoER/Studio .DM1 Direct database access(underlyingrepository)Issues Generally must have clientfor repository with APIinstalled on repository server Sometimes will not crossOS-specific lines, e.g.,COM/DCOM based APIrequires a Windows-basedrepository server Sometimes incomplete orunreliable (try the export/reimport roundtrip test) Sometimes multipleinterpretations of thestandards like CDIF andXMI Reliable metadata whenexporting.Possibility of corruptingmetadata when importing.Proprietary solution specificto the tool vendorMay again require vendorAPITypes of metadata interfacesAgain, one should refer to the web site for specific details by source. It is highlyencouraged that any organization building a metadata management environment developsa detailed set of tables like the ones above.P a g e 15 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)3.2 Understanding This Tutorial’s Enterprise ArchitectureAs a business case, this document refers to the data management and metadatamanagement lifecycle associated with a financial system for a large organization, simplyreferred to as “My Company.” It is comprised of several components and activities,including: Finance System:o Physical legacy Accounts Payable (AP) system and reverse-engineered datamodelo Logical design and physical data model for Accounts Receivable (AR) systemo Logical-Physical DW Staging and Physical dimensional Star-Schema DBModelo Data Mapping SpecificationsA conceptual layero Business Glossary maintained in erwin Metadata Management (EMM)o And Enterprise Conceptual Data Model (CDM) created using a logical designtool (erwin Data Modeler).o Semantic MappingsMetadata harvesting is the process of populating the repository with metadata from all ofthe sources identified in the last section after cataloging the metadata sources and dataprocesses and associated metadata mappings. In order to do so in a well managedprocess, one must first develop a catalog of the metadata in your organization.3.2.1 Catalog the Operational Data StoresBelow is the completed Data Store Catalog for the tutorial scenarios. Normally, such atable would take several iterations to complete in a large organization.P a g e 16 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)Metadata Source /TargetPOCReverseEngineeringMethodReverse EngineeringContentsFinance AccountsPayable (AP) erwinReverse EngineeringFinance AP-ARPOCER/Studio DM1bridgeFinance AccountsReceivable (AR) erwinLogical PhysicalDesignFinance DataWarehouse StagingDB Logical PhysicalDesignFinance DataWarehouse DB LogicalPhysical DesignFinance AP-ARPOCerwin v 9.x XMLbridgePhysical RDBMS design reverseengineered from the SQL ServerDB (MITI-AP.mdb) andcommented in erwin.Logical E-R and derived PhysicalRDBMS design for the SQL ServerDB (MITI-AR.mdb) in erwinFinance DWPOCerwin v 9.x XMLbridgeLogical E-R and derived PhysicalRDBMS design for the SQL ServerDB (MITI-FinanceDWStaging.mdb)in erwinFinance DWPOCerwin v 9.x XMLbridgeFinance Vendor MartDBFinance BI POCSAP PowerDesignerPDM bridgeLogical E-R and derived PhysicalRDBMS design for the SQL ServerDB (MITI-FinanceDW.mdb) inerwinRDBMS model for the SQL ServerDB (MITI-FinanceDW.mdb), BIcube design and packaginginformationP a g e 17 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)3.2.2 Catalog the Data Processes.Below is the completed Data Process Catalog for the tutorial scenarios. Normally, such atable would take several iterations to complete in a large organization.P a g e 18 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)Data ProcessNameFinanceAccountsPayable (AP)to Finance DWStaging ETLFinanceAccountsReceivable(AP) toFinance DWStaging ETLFinance DWStaging to DWETLFinance DW toVendor MartFinance BIDesign toReportingDescriptionExtracts fromthe AP RDBMSare loaded intoDW StagingDBExtracts fromthe ARRDBMS areloaded into DWStaging DBExtracts fromthe DW StagingRDBMS areloaded into DWRDBMSData MappingSpecificationsStitchingbetween BIdesign andreportingProcessPOCTypeScheduled DW POCETL viaInformaticaData Source(s)Scheduled DW POCETL viaInformaticaSource: MITI-ARTarget: MITIFinanceDWStagingScheduledETL viaPL SQLDW POCSource: MITIFinanceDWStagingTarget: MITI-FinanceDWerwinMetadataManagement (EMM)UIReal-timeBItransformationsBI POCSource: MITI-FinanceDWTarget: MITI-VendorMartBI POCSource: NoneTarget: NoneSource: Accounts PayableDBTarget: Finance DWStaging DBP a g e 19 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Management Tutorial – Web Portal & Data Governance Using erwin MetadataManagement (EMM)3.3Harvesting the Finance System MetadataAfter executing the tutorial restore structure script, the basic folder structure of therepository is created. Now it is time to define models to represent the data stores and dataprocesses that were cataloged in the previous sections. This section of the tutorial willdeal with the mechanics of harvesting the metadata embedded in data stores and dataprocess tools.Harvesting may be as automatic a process as one wishes to specify it. Most of the effortinvolved is in the definition of connection information or bridge import parameters todefine how the particular bridge will import, or harvest, the metadata from that source.Beyond that, harvesting is a scheduled or manual process, depending upon your workflow. The next sections walk one through the process of creating and harvesting theappropriate models for My Company.In the above diagram, one can see a lineage diagram at the model level of detail of thecomplete Finance System for My Company. As described earlier, it is a fairly typicalarchitecture consisting of Operational data stores (ODS) consisting of data entry and data management systems Data integration or extract, transform and load (ETL) feeds to A data warehouse consisting ofo A data warehouse staging (normalized) databaseo A snowflake or star-schema dimensional database Mart database for reporting.We will now refer back to the metadata catalog that we developed earlier in order topopulate the repository with metadata.As one may note from the metadata catalog, harvesting from the sources of metadata insome cases require connectivity directly to a source tool repository and/or API.However, for the purposes of this demonstration, all the metadata required for harvestingwill be either available directly in the tool format that a bridge can read (e.g., erwin DataModeler in XML format or Embarcadero ER/Studio Data Architect DM1 format), or willbe provided as an internal XML Metadata Interchange (MIR XMI), a proprietary formatof erwin Metadata Management (EMM) that faithfully represents the metadata capturedin the repository and via any of the bridges.3.3.1 Harvest the Accounts Payable modelIn erwin Metadata Management (EMM), expand the Repository Tree in the left handpanel:P a g e 20 220C o p y r i g h t 2 0 1 8 ,e r w i n I n c . a n d / o r i t s a f f i l i a t e s .V e r s i o n 2 0 1 8 R 1 ( 1 0 / 1 6 / 2 0 1 8 )A l lR i g h t sR e s e r v e d .
Metadata Manage
This tutorial currently does not contain a separate orientation on the erwin Metadata Management (EMM) toolset. Specific examples of how to perform the operations required for this tutorial are provided in the next sections. In order to create this structure in t
Metadata, Shodhganga of INFLIBNET metadata standard has been followed. 1.5 Vocabulary for Educational Metadata Chapter 7 discusses the use of Vocabulary in some fields under educational metadata. 1.6 Metadata Schema 1.6.1 Qualified Dublin Core The Dublin Core Metadata
Introduction Welcome to the User Guide for Oracle Metadata Management (OMM). Disclaimer Some of the features detailed in this document may not apply and/or be available for the particular Oracle Metadata Management (OMM) edition you may have. Metadata Overview Oracle Metadata Management (OMM) provides a comprehensive and well integrated set of Metadata Management (MM), Data Cataloging (DC) and .
of study designs. These approaches include meta-study, meta-summary, grounded formal theory, meta-ethnography, and qualitative meta-synthesis. In this workshop, we will focus on qualitative meta-synthesis by presenting a six-step approach for conducting this type of systematic review and sharing our procedures and results from our own studies.
The erwin Metadata Management (EMM) Physical Data Model allows customers to document existing data stores, like databases, big data sources, imported as models in erwin Metadata Management (EMM), and publish the resulting documented data stores to the enterprise. When documenting a model, one may:
- Developed using the SharePoint Metadata OM - WhitePaper is out - Documentation on MSDN. DEMO Applying Metadata Simple Metadata editing - Through the browser - Using Word Metadata Navigation Settings Ratings. Advanced document management All documents can now be auto-tagged with an ID - Unique accross the Site Collection and with .
That is, HDFS ensures the consistency of metadata by only allowing a single client at a time to mutate its metadata. The metadata must t on the heap of a single Java virtual machine (JVM) [10] running on the . We are addressing the problem of how to migrate HDFS' metadata to a relational model, while maintaining consistency semantics at least .
If you have identified that a managed metadata column is a good fit for your SharePoint project, here is how you can implement it. To create a managed metadata in SharePoint, you need to take the following two steps: Step 1: Create a Managed Metadata Column A managed metadata column is a special column that is linked to a specific term set.
TASC Reading Test Practice Items Read the text. Then answer the questions. Excerpt from Main Street by Sinclair Lewis Main Street is a novel about a girl who grew up in the big city. She has married a physician who moves them to the small town in the Midwest in which he grew up. She is reluctant to move from the city she knows, but goes along with her husband thinking that perhaps she can .
