Aristotle Metadata Registry help documentation
  • Welcome to the Aristotle Metadata Knowledge Base
  • Finding and Viewing Metadata
    • Search
      • Using omnisearch to find registry content
      • Using advanced search filters to find registry content
        • Advanced Search: Help
    • Browsing the registry
    • Item page breakdown
    • Searching for Alternate Names in the Search Bar
    • Viewing related items and graphs
    • Compare different versions of a metadata item
    • Bulk actions
    • Downloading Content
    • Generating an API token
  • Personalisation
    • Navigation Choices on 'My Dashboard'
    • Managing your account
    • How to reset your password
    • Invite/Reset Password Link Is expired
    • How to set up multi factor authentication
    • Roles in the registry
    • Viewing your roles
    • Favouriting and tagging content
    • Notifications
  • Creating and Editing
    • My sandbox
    • Metadata Toolbox
    • Creating metadata items
      • Creating a data element or data element concept
      • Creating a metadata item with a single item creation wizard
    • Editing content
    • Cloning
    • Deleting metadata items
    • Restore Deleted Content
    • How to create and link quality statements
    • How to create and link glossary items
    • How to record data lineage
    • How to add alternative names to a metadata item
    • How to move individual and bulk metadata into a collection
    • Upload Metadata Using Bulk Import Feature
    • HTML Sanitization
    • Version Control - Supersede
    • Classifications
    • How to link Quality statement to an Indicator?
    • Dataset Grouping
    • Property Groups
      • How to Create Property Groups In Aristotle Registry?
    • Object Class Specialisation
      • How to create an object class specialisation
  • Collaborating within the registry
    • Aristotle Help
    • How to add content to workgroups
    • Reviews
    • Aristotle metadata community
    • How to create Collections and Sub Collections
    • Issues and Change Requests
      • Creating an issue label
      • Creating an issue
      • Viewing all issues
      • Proposing a change request
    • Metadata History: Comparing change logs
  • Registration Authorities
    • Creating and editing registration authorities
      • Validation Rules
        • Setting validation rules
          • Writing validation rules
    • Directly endorsing metadata items
    • Managing members of a registration authority
  • Administrator Tasks
    • Managing user accounts
    • Creating and maintaining a Stewardship Organization
    • Creating and managing workgroups
    • Managing and adding members to a workgroup
    • Add a user to Multiple Stewardship Organizations and Workgroups
    • Creating and editing namespaces and identifiers
      • Configuring manually triggered incremental identifiers
      • Configuring automatically triggered incremental identifiers
    • Deactivating a user account
    • View CRUD (Create, Read, Update and Delete) Changes
    • View deleted items using query string
    • Contact Form
    • Custom Item Templates
      • Creating and editing custom item templates
        • Creating and editing sub-pages
      • Creating metadata items using custom item templates
    • Task Runner
      • Resolving issues with the search function using reindex
      • Populating help pages using load help
      • Resolving issues with item visibility by recaching visibility
      • Viewing all recent and historical task runner information
    • Aristotle Cloud Settings Editor
      • Adjusting visual settings
      • Adding and deleting header and footer links
      • Adjusting general registry settings
      • Adjusting metadata and functionality extensions
      • Making workgroup changes
      • Toggling summary statistics
      • Adjusting separator options
      • Adjusting download options
      • Adjusting translation options
      • Adjusting search options
      • Adjusting spam detection options
    • Registry Customisation in Cloud Settings
    • Custom Domains
      • Requesting a custom domain
      • Setting up a custom domain
  • Registry configuration
    • How to customise a registry
    • Enabling self sign-up
    • Adjusting privacy mode settings
    • Adding a custom login message
    • Homepage Editor
      • Creating a custom homepage using the HTML editor
      • Creating a custom homepage using the safe editor
    • Adding custom HTML to the header and footer of the registry
    • Simple customisation of Header, Body, and Footer
    • Content policies
    • Adding custom fields
      • Custom Field: Structured Data (Json) Type
  • Stewardship Tasks
    • Collection publication and permissions
    • Publishing metadata
    • Creating and managing registration authorities
    • How to add members to a stewardship organisation
    • How to create alternative name types
    • Metadata Report Builder
    • Reference Document Uploads to the Registry
    • Linking reference documents to metadata items
    • Remove Metadata from Workgroup
    • Organisation Records
      • Creating, managing and deleting an organisation record
      • Linking an organisation record to a metadata item
  • Subject Matter and Theory
    • What is metadata?
    • Data Dictionary
    • ISO/IEC 11179 data element representation
    • Bulk Import
    • Data Lineage
    • MAST(Metadata Analysis Standards Teamwork) Methodology and IDEAL Framework
      • Aristotle metadata user guides
  • Special features
    • Generating a Business Information Model using the Visualization Tool
    • Registering an app with the app store
    • Metadata Merger Tool
      • How to set up rules in the merger tool?
    • Federation
      • How do I federate content from another Aristotle Metadata Registry?
  • Geospatial Information
  • Checking for duplicates in the registry
  • Custom Field Bulk Uploader
    • Uploading structured data (JSON) custom fields
    • Bulk Importing Alternative names and Identifiers
  • System Users
  • Single Sign On
    • How to invite and update permissions of Aristotle Metadata staff on a client registry
  • Tablion - Data request portal
    • How to Extract Datasets from the Aristotle Metadata Registry into Tablion
  • Data Inventory View
  • Accessing the Aristotle Metadata Academy
Powered by GitBook
On this page
  • The MAST Manifesto
  • The MAST Methodology
  1. Subject Matter and Theory

MAST(Metadata Analysis Standards Teamwork) Methodology and IDEAL Framework

PreviousData LineageNextAristotle metadata user guides

Last updated 1 year ago

The MAST at Aristotle Metadata has come up with "The MAST Methodology," a human-centric approach to data based on our proven experience delivering change programs to improve data governance.

The Metadata Analysis Standards Team (MAST) uses the MAST™ methodology to help clients analyse and create metadata in Aristotle (see below). This methodology can be replicated by organisations to develop collaborative metadata practices.

The MAST Manifesto

The MAST Methodology

The MAST methodology uses the IDEAL Framework to provide a consistent organisational approach to metadata management and data governance, and is underpinned by of the Inventory, Documentation, Endorsement, Audit and Leadership (IDEAL™) metadata framework (see below).

Goals, actions and pitfalls when implementing the IDEAL Framework

The IDEAL framework is an iterative process that recognises that quality metadata promotes data literacy within an organisation.

  • I (Investigate and Inventory Data)

In this phase a client organisation starts to consider the benefits of documenting their metadata in a more discoverable way.

For example, an organisation may want a better understanding of how their organisational data is collected and managed. This includes having more clarity about definitions and duplication of content, as well as greater visibility of their metadata.

MAST’s role at this stage is to show a potential client how Aristotle can help them. This can be customised to an organisation’s needs and level of metadata maturity. Some organisations may prefer a pilot study that enables them to see the benefits of a metadata registry before committing to a large-scale metadata project.

MAST may research organisational data assets during the investigation phase. This includes Word and/or PDF documents, and published data on their website. A sample of the client’s data assets can be displayed in an Excel spreadsheet to highlight the benefits of metadata management within their organisation.

The inventory stage will help clients to focus on those assets that have the most value to the organisation and therefore inform the scope of the work.

  • D (Document data and metadata)

The documentation phase aims to increase an organisation’s understanding of the structure and content of their data. This involves migrating information from multiple locations into a single metadata repository based on an international standard for metadata registries, ISO 11179.

The source metadata is often contained in spreadsheets, Word documents, data dictionaries and/or databases. There may be duplication of content, given that client organisations often use several applications across an organisation in collecting data. This step includes to capturing the information into machine readable formats.

During this phase, MAST support will be tailored to meet client needs. In some cases, MAST may do the documentation in Aristotle for the client. Other organisations may document their data in Aristotle independently, and seeking help on an ‘as needed’ basis.

  • E (Endorse and publish metadata)

After completing the documentation phase, the content can be made visible for peer review. Sharing content allows it to be explored, assessing issues such as fitness for purpose, redundancies, and duplication of content.

Client organisations have control over the processes for making their metadata visible to others. Assigning registration statuses to metadata makes it visible and allows stakeholders to approve the content.

Sharing and approval of content occurs through registration authorities within Aristotle. Registration authorities are groups of people with authority to approve metadata. They include committees or agencies with specific governance arrangements.

  • A (Audit and Harmonise terms)

The audit stage of the IDEAL™ framework aims to standardise the representation of organisational data. Although this may be challenging in practical terms, the iterative nature of IDEAL™ means that it may be achievable in the future.

Stakeholder engagement is key to improving the comparability and interoperability of the metadata. This involves asking questions about how users interpret data and terms and seeking consensus about content. MAST can provide guidance on quality metadata based on the ISO 11179 standard to help with decision-making.

This stage includes harmonising content by finding duplicate content and redundant metadata. MAST can help this process by highlighting metadata issues and making recommendations for remedial action.

  • L (Leadership and long-term strategy)

Implementing the IDEAL framework within an organisation will help users to have a better understanding of their data. Teams who work in this area can be leaders in educating users about the benefits of a centralised metadata repository that can be updated as business requirements change.

Aristotle promotes leadership in metadata through stewardship organisations. These organisations are responsible for maintaining the accuracy and relevance of content within their metadata registry. They provide a leadership role for the long-term management of organisational metadata.

Other long-term strategies include examining and disposing of data which is not being used by or within the client organisation. This role may be undertaken by a data consultancy organisation, although there is scope for Aristotle to do this work in the future.