System and method for metadata-based distribution of content

• US 20050160088A1
• Filed: 01/06/2005
• Published: 07/21/2005
• Est. Priority Date: 05/17/2001
• Status: Abandoned Application

• Current Assignee: Interwoven Incorporated (HP Inc.)
• Original Assignee: Interwoven Incorporated (HP Inc.)
• Inventors: Fu, Patrick, Cuan, William G., Scallan, Todd, Zhong, Meili
• Application Number:
  US11/031,309
• Publication Number:
  US 20050160088A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/435 Filtering based on additional data, e.g. user or group profiles
• CPC Class Codes: G06F 16/48 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation

Abstract

In a system for metadata-based distribution of content, metadata queries are used to specify rules for content distribution jobs, allowing flexible, intelligent deployment, expiration and syndication of code and content across an enterprise or content network. A configurable payload adapter receives the metadata query, parses and translates the metadata into a form specific to the particular implementation, and then queries a metadata repository to identify a list of digital assets that satisfy the specified criterion specified by the metadata. The assets are retrieved from a content repository and distributed, syndicated and/or expired according to the distribution rules. Intelligent delivery of digital assets enables syndication of content based on offers and subscriptions.

Claims

1. A method of managing digital assets across an enterprise comprising:

specifying rules for a distribution action using at least one metadata-based query;

querying indexed metadata in a metadata repository associated with a source host to identify assets at the source that satisfy said query; and

one or both of;

comparing said identified assets with those on a target site, wherein at least a portion of said identified assets are deployed to said target or at least a portion of assets at said target are expired based on said comparison

2. The method of claim 1, wherein specifying rules comprises:

creating said metadata-based query with user-defined metadata and internal metadata;

converting said query into a call appropriate to said repository by a payload adapter.

3. The method of claim 2, wherein said payload adapter comprises a JAVA class.

4. The method of claim 2, wherein said payload adapter is resident on said source host.

5. The method of claim 2, wherein said payload adapter is resident on a base server.

6. The method of claim 2, further comprising:

specifying payload adapter properties in a configuration file for said source server, wherein said payload adapter properties include at least;

class; and

name.

7. The method of claim 2, further comprising:

specifying a source file location in a deployment configuration.

8. The method of claim 7, further comprising:

specifying a subpath within said source file location.

9. The method of claim 2, further comprising:

specifying a target location in a deployment configuration.

10. The method of claim 2, wherein creating said metadata-based query with user-defined metadata and internal metadata comprises:

defining input to said adapter in a ‘

payload rules’

element in a deployment configuration, wherein said payload rules are specified using either a predetermined query syntax or a CDATA (character data) string, said string composed using a syntax compatible with said payload adapter.

11. The method of claim 10, wherein specifying rules using said predetermined query syntax comprises specifying at least one predicate.

12. The method of claim 11, wherein specifying at least one predicate comprises for, each predicate, specifying:

an operator type and a value.

13. The method of claim 12, wherein specifying at least one predicate further comprises:

specifying a key element.

14. The method of claim 13, wherein specifying a key element comprises specifying that the key element is one of:

a text string, a numeric value and a date.

15. The method of claim 14, wherein specifying that the key element is a date comprises specifying that the date is either a date string or a time stamp, and if a data string, the format.

16. The method of claim 2, wherein specifying rules comprises specifying an action type, wherein action types include at least ‘

deploy’ and

‘

expire.’

17. The method of claim 2, wherein said payload adapter prepares a payload of files to be returned to a source server from a content repository at said source.

18. The method of claim 1, further comprising:

scheduling said distribution action.

19. The method of claim 1, wherein said metadata repository is part of an integrated content management system.

20. The method of claim 1, wherein said metadata repository is external to a content management system.

21. The method of claim 19, wherein said metadata repository comprises a JDBC (JAVA database connectivity)-compliant relational database.

22. The method of claim 1, further comprising:

deploying a preconfigured list of assets.

23. The method of claim 1, further comprising:

deploying assets based on comparison of assets on the source and the target.

24. A system for managing digital assets across an enterprise comprising:

a source that includes content and metadata repositories; and

means for specifying rules for a distribution action using at least one metadata-based query; and

a payload adapter for preparing a payload of assets from said content repository that satisfy said query; and

means for comparing said assets with assets at a target and distributing said assets according to a specified action type.

25. The system of claim 24, wherein said source is part of an integrated content management system.

26. The system of claim 24, wherein said source is external to a content management system.

27. The system of claim 24, wherein said source includes a base server, wherein any of said metadata repository, said content repository and said base server are physically dispersed from any of each other;

or

wherein said base server and said repositories are located at single network node.

28. The system of claim 24, further comprising a deployment configuration file resident at said source, wherein said means for specifying rules for a distribution action comprises an interface for managing said deployment configuration file, said deployment configuration file including at least one element for specifying rules for said metadata query.

29. The system of claim 28, wherein said interface comprises any of:

an administrative user interface;

a command line user interface; and

a web-services API (application programming interface).

30. The system of claim 28, wherein said payload adapter comprises a JAVA class.

31. The system of claim 30, wherein said payload adapter accepts input from said deployment configuration file.

32. The system of claim 28, wherein said payload of assets comprises a file manifest.

33. The system of claim 28, further comprising a scheduler for scheduling a distribution action, wherein said scheduler is accessible by means of said interface.

34. The system of claim of claim 27, wherein said means for comparing said assets with assets at a target and distributing said assets comprises a transport layer at said server.

35. The system of claim 28, wherein said distribution action comprises any of deploy and expire, and wherein said distribution action is specified in said deployment configuration file.

36. A method of syndicating digital assets comprising:

creating an offer, wherein said offer comprises content specified for distribution according to intelligent, metadata-based delivery rules;

creating a subscription corresponding to said offer by scheduling a distribution job corresponding to said offer; and

transmitting said specified content using a chosen delivery mechanism.

37. The method of claim 36, wherein said delivery method comprises any of:

transmitting to a receiver configured to process said transmitted assets;

transmitting via FTP;

transmitting via email;

transmitting via ICE protocol; and

delivering said assets directly to a repository for repurposing.

38. The method of claim 36, further comprising:

updating or removing an offer by modifying or deleting a corresponding deployment configuration template.

39. The method of claim 36, further comprising:

updating or suspending a subscription delivery schedule through a scheduler.

40. The method of claim 36, further comprising specifying a lifecycle for said offer that stipulates a timeframe during which said offer is valid.

41. The method of claim 36, further comprising tagging content with metadata that can be used by distribution jobs for determining which assets to deliver.