Customizable Metadata System for Learning Resources
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional meta data standards, such as XML, are not optimized for maintaining meta data within a specific organization or group of users, as they include large quantities of optional values and fixed semantic tags, making it difficult to accommodate unique user requirements and maintain organization-specific meta data.
Innovation Solution
A system and method for handling meta data that uses a customizable non-semantic tag format, allowing users to customize meta data fields, importance, and data types, with a meta data processor transforming data between predefined and customizable formats, and a user interface for customizing meta data values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional meta data standards (XML, LOM, Dublin Core) are used, then meta data can be exchanged between different independent users and organizations, but the standards include large quantities of optional values and fixed semantic tags that are not required by all users, making it difficult to maintain organization-specific meta data
Solution Approach 1:
The patent segments the meta data structure into two distinct parts: a standardized header section containing common meta data elements (for interoperability) and a customizable body section (for organization-specific requirements). This segmentation allows the system to maintain both exchange capability and organizational customization without the entire structure being complex.
Solution Approach 2:
The patent introduces dynamic customization capabilities where the body section of the meta data can be configured differently for each organization or user group. The system allows dynamic addition, modification, or removal of custom meta data elements while maintaining the fixed header structure, enabling adaptability without increasing overall complexity.
2Reliability
If conventional standards use fixed values with predefined semantic and XML tags, then meta data can be exchanged between different independent users, but it is not possible to maintain meta data that is unique to a particular user or organization
Solution Approach 1:
By dividing the meta data into a standardized header and customizable body, the patent ensures that the header maintains reliable exchange capabilities across organizations while the body can be customized for organization-specific requirements, thus achieving both reliability and adaptability.
Solution Approach 2:
The standardized header acts as an intermediary layer that enables communication between different organizations, while the customizable body serves as an extension that allows organization-specific data to be maintained. The header mediates the exchange process, ensuring compatibility while allowing customization in the body section.
3Adaptability or versatility
If a one size fits all approach is used to accommodate diverse user requirements, then broad user needs are met, but a large proportion of meta data becomes optional and cannot be reliably maintained
Solution Approach 1:
The patent segments meta data into mandatory header elements (maintained reliably) and optional body elements (customized per organization). This segmentation ensures that core meta data is reliably maintained while allowing optional customization for different user requirements, resolving the contradiction between adaptability and reliability.
Solution Approach 2:
The patent applies local quality by allowing different levels of customization in the body section for different organizations or user groups. Each organization can configure the meta data body to match its specific needs while the header maintains uniform quality and reliability across all users.
Data Source
AI summary
A system for handling meta data for describing one or more resources, wherein the one or more resources are deliverable to a common group of users at one or more user terminals, the system including: a resource server for storing the one or more resources for delivery to at least one of the common group of users at one or more user terminals, an administration server arranged to serve the common group of users at the one or more user terminals, for storing a set of meta data for describing the learning resources, the meta data having a format including a non-semantic tag which is customisable in accordance with the common group of users' requirements.