Digital Repository Data Item Extension via Interface Description
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional digital object repositories have fixed interfaces and do not allow for additional functionality or arbitrary operations to be associated with objects or groups of objects, limiting the ability to extend the data model or programmatic API.
Innovation Solution
A method that allows clients to request data items with identifiers pointing to interface routines, which return an interface description document containing data processing routines, enabling clients to invoke these routines with or without arguments, effectively extending the functionality of digital repository objects without modifying the interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional fixed interfaces are used in digital repositories, then system stability and simplicity are maintained, but adaptability and versatility are limited
Solution Approach 1:
The patent implements dynamic interfaces where data items can have associated processes attached to them. The interface description document dynamically generated for each data item reveals which processes are available, allowing the system to adapt its behavior based on the specific data item being accessed rather than following a fixed interface pattern for all items.
Solution Approach 2:
The patent creates a universal interface mechanism that works across different types of data items. The same interface description document structure and process attachment mechanism can be applied to any data item in the repository, whether it's a simple file or a complex data structure, providing multi-functionality without requiring type-specific interface implementations.
2Adaptability or versatility
If arbitrary operations are associated with objects, then functionality is extended, but ease of operation deteriorates due to interface complexity
Solution Approach 1:
The system automatically generates the interface description document for each data item, revealing the available processes without requiring users to manually configure or discover them. The repository service itself provides the interface information, making the system self-describing and reducing the operational burden on users.
Solution Approach 2:
The interface description document acts as an intermediary between the data item and the client. Instead of requiring clients to directly interact with complex underlying processes, the interface description document provides a standardized way to discover and invoke processes, simplifying the interaction model.
3Reliability
If system administrators control interface extensions, then reliability is maintained, but ease of manufacture deteriorates due to restricted customization
Solution Approach 1:
The patent allows different levels of control over process attachment. While system administrators can control repository-wide settings, individual users can attach processes to specific data items within their authority scope. This local quality approach enables customization at the data item level without compromising overall system reliability and administrative control.
Solution Approach 2:
The system segments interface extension control into different levels: repository-level administrative control and data-item-level user customization. This segmentation allows system administrators to maintain reliability through centralized policies while enabling users to customize functionality for specific data items without requiring administrative privileges.
Data Source
AI summary
A digital repository 20 includes data items. A user can add additional functionality or program routines to data item by including as a data item a data processing identifier pointing to at least one data processing routine. Such routines are accessed by a client 22 by sending from a client to the digital repository 20 a request to access a data item, wherein the repository provides an interface description document 32 from the digital repository 20 to the client 22 as the response to the request. The client 22 can then transmit a data processing request from the client to a service 26 identified by the data processing identifier of the interface description document 32, the data processing request including the identifier from the interface description document.