Repository Metadata Harvesting with Interface Link Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing repository systems struggle to efficiently communicate and manage metadata for learning content objects across different repositories, particularly in electronic educational systems, due to limitations in existing protocols like OAI-PMH.

Innovation Solution

A method and system for communicating between repositories that involves identifying and retrieving metadata from a first repository, including a link to an interface associated with the content object, and storing a harvested content object that includes this metadata, allowing for the communication of usage data back to the original repository through APIs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If metadata is harvested from external repositories using existing protocols like OAI-PMH, then the external repository can store and provide search results including harvested content objects, but the protocol lacks the capability to communicate specialized learning content attributes and usage data between repositories

Engineering Contradiction:
Improvemetadata communication capabilityVSAvoidlearning content attributes
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary metadata structure that bridges existing harvesting protocols (OAI-PMH) and specialized learning content requirements. This intermediary layer captures specialized attributes (content type, educational level, learning objectives) and usage data (access counts, user feedback, instructor ratings) that are not natively supported by standard protocols, thereby preserving information that would otherwise be lost in traditional metadata harvesting.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments metadata into distinct categories: core metadata (title, description, creator) that can be harvested using existing protocols, and specialized learning content metadata (content type, educational level, learning objectives, usage data) that requires extended capture mechanisms. This segmentation allows the system to maintain compatibility with existing protocols while adding specialized information capture capabilities for learning content attributes.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If repositories store only basic metadata, then storage and retrieval are simple, but search results lack detailed information about learning content objects

Engineering Contradiction:
Improvelearning content informationVSAvoidrepository system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by capturing and storing specialized learning content attributes and usage data at the point of content ingestion and harvesting, rather than attempting to add this information later. The system proactively collects content type, educational level, learning objectives, and usage metrics when metadata is first harvested, ensuring this information is available for enhanced search results without requiring complex post-processing operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a universal metadata extension framework that can handle both traditional repository metadata and specialized learning content attributes through a unified structure. This multi-functional metadata system serves dual purposes: it maintains compatibility with existing repository operations while simultaneously supporting specialized learning content description and usage tracking, thereby managing complexity through standardization rather than proliferation of separate systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If repositories use standardized metadata protocols, then interoperability is improved, but the ability to track and synchronize usage data across repositories is limited

Engineering Contradiction:
Improverepository interoperabilityVSAvoidusage data synchronization
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where usage data (access counts, user feedback, instructor ratings, completion rates) collected at one repository is systematically communicated back to the source repository and other repositories holding the same or related content. This feedback loop ensures that usage information is synchronized across the distributed repository network, improving reliability of usage data while maintaining interoperability through standardized metadata exchange formats.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250190412A1System and method for communication between repositories
Publication Date: 2025.06.12 DESIRE2LEARN
  • US20250190412A1 patent drawing
  • US20250190412A1 patent drawing
  • US20250190412A1 patent drawing

AI summary

At least one of the embodiments described herein relate generally to a method of communicating between a first repository and a second repository. The method can be performed at a second repository, and may include the acts of: identifying a content object stored in the first repository; identifying metadata for the content object stored in the first repository, the metadata comprising a link to an interface associated with the content object, the interface being provided by the first repository; retrieving the metadata from the first repository; and storing a harvested content object corresponding to the content object, the harvested content object comprising the metadata that includes the link to the interface, wherein the interface is accessible by the second repository to communicate information related to the harvested content object to the first repository.