WO2010074655A1 - Système et procédé pour mettre en place un système d'étiquetage incitatif de ressources électroniques - Google Patents

Système et procédé pour mettre en place un système d'étiquetage incitatif de ressources électroniques Download PDF

Info

Publication number
WO2010074655A1
WO2010074655A1 PCT/SG2008/000498 SG2008000498W WO2010074655A1 WO 2010074655 A1 WO2010074655 A1 WO 2010074655A1 SG 2008000498 W SG2008000498 W SG 2008000498W WO 2010074655 A1 WO2010074655 A1 WO 2010074655A1
Authority
WO
WIPO (PCT)
Prior art keywords
tag
data
resource
search
user interface
Prior art date
Application number
PCT/SG2008/000498
Other languages
English (en)
Inventor
Nachiappan Sudha
Original Assignee
Nachiappan Sudha
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nachiappan Sudha filed Critical Nachiappan Sudha
Priority to PCT/SG2008/000498 priority Critical patent/WO2010074655A1/fr
Priority to SG2011075611A priority patent/SG178008A1/en
Publication of WO2010074655A1 publication Critical patent/WO2010074655A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/12—Use of codes for handling textual entities
    • G06F40/14—Tree-structured documents
    • G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/169—Annotation, e.g. comment data or footnotes

Definitions

  • the present invention relates to system and method for providing user interface for tagging an electronic resource, exposing tag data for search and a reward system to credit users for tag relevance and usage.
  • Present enterprise search implementations utilize the same technology that is used in the web for searching documents and resources.
  • a vast amount of structured and unstructured information in the form of documents and the like is available in an enterprise similar to web.
  • This information may include business information such as, for e.g., proposal to specific industry customer, quotation for the industrial customer in a certain geographical area under a particular business unit, and may be in the form of spreadsheets, power point presentations, visio drawings, one note documents, pdf documents, HTML documents or a bevy of other formats and applications including custom ones.
  • Essentially vast swaths of documents are churned by an enterprise in today's environment.
  • these search engines never have the ability to understand business relevancy and effectively find metadata information associated with each of the document. They typically try to mine physical file properties as provided by operating system or their host handling program while searching the documents. Basically user involvement in adding additional business relevant tag information is missing for each of the resources that enterprises generate in today's environment in a simplified and affordable manner. If an enterprise user wants, for example, to search an architecture visio diagram file and associated architecture word & pdf document created in the year 2000 belonging to creative division in the Americas region with an associated proposal that was sold for 2 million isn't available. This kind of search is remote with current brew of enterprise search engines.
  • Rich metadata for each of the resource shared can be added automatically by system or by an enterprise user. If user adds business and business process related tags, then the metadata available for searching provide clues to answers for above search example. Hence a simplified, intuitive interface to collect and enter tag attribute and data is essential. To persuade and to achieve good business tagging, user participation in enterprise needs to be incentivized.
  • Embodiments of present invention provide a system and method to provide tag and search capability for electronic resources using a intuitive user interface system for tagging, creating multi-dimensional fact tables to expose tag data for searching and a reward system to credit users for tagging relevance and usage
  • a user interface program to tag an electronic resource is provided.
  • access to user interface system is provided by right clicking the target file resource from the operating system file explorer and selecting the user interface program listed in menu.
  • access to user interface system is provided by a means for user to click a button on the tool bar or other configured areas within the target resource's handling program to launch the user interface within the host program's display or process application space.
  • access to user interface is provided via a browser that launches URL to fetch the user interface program available as a web application with plug-ins.
  • resources can be tagged by dragging and dropping file icons from operation system file explorer or URLs from browser into the user interface.
  • user interface program comprises of a specific area to display information wherein a plurality of predefined business process or business classification tag attributes are displayed in the bottom of the interface visually as icons. Display of above said icons are in a carousel display format allowing users to scroll. Tag header and values pertaining to selected attribute are shown on the left as known in the art and is searchable. Tag values can be loaded on demand and narrowed down by searching.
  • user interface program comprises of a specific area to display information wherein a plurality of tag attributes currently associated under different categories that include but not limited to dimensional and custom categories are shown. For designated categories, users can dynamically add as many tag attributes and values as required.
  • user interface program comprises of a specific area to display information wherein a plurality most recently created tags associated to individual resources are shown in reverse chronological order.
  • User can search by entering filter criteria to narrow down the requisite tags for view and to apply it to current resource being tagged.
  • user interface program comprises of a specific area to display information wherein tag statistics is displayed that comprises of count of resources that has been tagged, searched, viewed and downloaded and reward points awarded.
  • Reward algorithm decides points to be awarded based on the tag relevance and usage factors configured.
  • tag attributes are based and linked to columns of dimensional tables, master detail tables, hierarchical tables of a relational data store. Tag attributes are also based on headers of any structured data list.
  • tag data of any tagged resource is saved locally in the computer system in XML format prior to submitting tag data and resource content to designated resource repository through a web service wherein web service or resource repository can be online or offline.
  • tag data received by the web service is stored as XML document and database records are created in multi-dimensional fact table where in the tag data items and their derived data items forms part of the dimension or fact. These multi-dimensional fact tables, derived views and query interfaces are exposed to search engines and search algorithms. [020] In accordance to another aspect of the invention, counts are maintained for each user whose tagged resources are accessed, viewed and downloaded through interfaces exposed. Also count of number of resources tagged by each and all users are maintained.
  • a reward algorithm will assign points for each user determining tag relevance and usage based on the above said count information.
  • a user interface program to search tag data XML files wherein a plurality distinct tag attributes along with their values from tag data XML files and recently searched text is shown on the left.
  • Free form search text can be entered into search text box or a tag attribute with value can be selected or dragged and dropped into search text box to refine the search.
  • FIG. 1 depicts a representation of a network of data processing systems in which the present invention may be implemented
  • FIG. 2 is a block diagram illustrating a data processing system in which the present invention may be implemented
  • FIG. 3 is a block diagram illustrating components used in collecting, managing, storing, preparing and exposing tag metadata and resources in accordance with an illustrative embodiment of the present invention
  • FIG. 4 is a block diagram illustrating sub components used in client and server side in accordance with an illustrative embodiment of the present invention
  • FIG. 5 is a block diagram illustrating client user interface outline in accordance with an illustrative embodiment of the present invention.
  • FIG. 6 is a block diagram illustrating invoking of client user interface from operating system file explorer in accordance with an illustrative embodiment of the present invention
  • FIG. 7 is a block diagram illustrating invoking of client user interface from within word editing program (Microsoft Word ® ) in accordance with an illustrative embodiment of the present invention
  • FIG. 8 is a block diagram illustrating invoking of client user interface from within spreadsheet program (Microsoft Excel ® ) in accordance with an illustrative embodiment of the present invention
  • FIG. 9 is a block diagram illustrating display of client user interface as web application served from a web URi in arrnrHanrp with an illustrative embodiment of the present invention.
  • FIG. 10 is a block diagram illustrating detailed client user interface elements and various display areas in accordance with an illustrative embodiment of the present invention.
  • FIG. 11 is a flow chart diagram illustrating invocation of client user interface and data fetch process with an illustrative embodiment of the present invention
  • FIG. 12 is a flow chart diagram illustrating functionalities in client user interface and their business process with an illustrative embodiment of the present invention
  • FIG. 13 is a block diagram illustrating various configurations in which the present invention may be implemented.
  • FIG. 14 is a block diagram illustrating server data reception process with an illustrative embodiment of the present invention.
  • FIG. 15 is a block diagram illustrating server data preparation process with an illustrative embodiment of the present invention.
  • FIG. 16 is a block diagram illustrating server plug-in and search process with an illustrative embodiment of the present invention
  • FIG. 17 is a block diagram illustrating client user interface elements and various display areas in accordance with an illustrative embodiment of the present invention used to search tag data xml documents saved with tagxml file extension.
  • FIGS. 1-2 exemplary diagrams of data processing environments are provided in which embodiments of the present invention may be implemented. It should be appreciated that FIGS. 1-2 are only exemplary and are not intended to assert or imply any limitation with regard to the environments in which aspects or embodiments of the present invention may be implemented. Many modifications to the depicted environments may be made without departing from the spirit and scope of the present invention.
  • FIG. 1 depicts a pictorial representation of a network of data processing systems in which aspects of the present invention may be implemented.
  • Network data processing system 100 is a network of computers in which embodiments of the present invention may be implemented.
  • Network data processing system 100 contains network 102, which is the medium used to provide communications links between various devices and computers connected together within network data processing system 100.
  • Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.
  • server 104 and server 106 connect to network 102 along with storage unit 108.
  • clients 110, 112, and 114 connect to network 102. These clients 110, 112, and 114 may be, for example, personal computers or network computers.
  • server 104 provides data, such as boot files, operating system images, and applications to clients 110, 112, and 114. Clients 110, 112, and 114 are clients to server 104 in this example.
  • Network data processing system 100 may include additional servers, clients, and other devices not shown.
  • network data processing system 100 is the Internet with network 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, governmental, educational and other computer systems that route data and messages.
  • network data processing system 100 also may be implemented as a number of different types of networks, such as for example, an intranet, a local area network (LAN), or a wide area network (WAN).
  • FIG. 1 is intended as an example, and not as an architectural limitation for different embodiments of the present invention.
  • Data processing system 200 is an example of a computer, such as server 104 or client 110 in FIG. 1, in which computer usable code or instructions implementing the processes for embodiments of the present invention may be located.
  • data processing system 200 employs a hub architecture including north bridge and memory controller hub (NB/MCH) 202 and south bridge and input/output (I/O) controller hub (SB/ICH) 204.
  • NB/MCH north bridge and memory controller hub
  • SB/ICH south bridge and input/output controller hub
  • Processing unit 206, main memory 208, and graphics processor 210 are connected to NB/MCH 202.
  • Graphics processor 210 may be connected to NB/MCH 202 through an accelerated graphics port (AGP).
  • AGP accelerated graphics port
  • local area network (LAN) adapter 212 connects to SB/ICH 204.
  • Audio adapter 216, keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224, hard disk drive (HDD) 226, CD-ROM drive 230, universal serial bus (USB) ports and other communication ports 232, and PCI/PCIe devices 234 connect to SB/ICH 204 through bus 238 and bus 240.
  • PCI/PCIe devices may include, for example, Ethernet adapters, add-in cards, and PC cards for notebook computers. PCI uses a card bus controller, while PCIe does not.
  • ROM 224 may be, for example, a flash binary input/output system (BIOS).
  • HDD 226 and CD-ROM drive 230 connect to SB/ICH 204 through bus 240.
  • HDD 226 and CD-ROM drive 230 may use, for example, an integrated drive electronics (IDE) or serial advanced technology attachment (SATA) interface.
  • IDE integrated drive electronics
  • SATA serial advanced technology attachment
  • Super I/O (SIO) device 236 may be connected to SB/ICH 204.
  • An operating system runs on processing unit 206 and coordinates and provides control of various components within data processing system 200 in FIG. 2.
  • the operating system may be a commercially available operating system such as Microsoft ® Windows ® XP, Windows ® Vista (Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both).
  • An object- oriented programming system such as the C# programming system, may run in conjunction with the operating system and provides calls to the operating system from .NET programs or applications executing on data processing system 200 (.NET is a trademark of Microsoft in the United States, other countries, or both).
  • data processing system 200 may be, for example, an Wintel server computer system, running the Microsoft ® Windows Server 2003 / 2008 ® operating system.
  • Data processing system 200 may be a symmetric multiprocessor (SMP) system including a plurality of processors in processing unit 206. Alternatively, a single processor system may be employed.
  • SMP symmetric multiprocessor
  • Instructions for the operating system, the object-oriented programming system, and applications or programs are located on storage devices, such as HDD 226, and may be loaded into main memory 208 for execution by processing unit 206.
  • the processes for embodiments of the present invention are performed by processing unit 206 using computer usable program code, which may be located in a memory such as, for example, main memory 208, ROM 224, or in one or more peripheral devices 226 and 230.
  • FIGS. 1-2 may vary depending on the implementation.
  • Other internal hardware or peripheral devices such as flash memory, equivalent non-volatile memory, or optical disk drives and the like, may be used in addition to or in place of the hardware depicted in FIGS. 1-2.
  • data processing system 200 may be a personal digital assistant (PDA), which is configured with flash memory to provide non-volatile memory for storing operating system files and/or user generated data. Also, the processes of the present invention may be applied to a multiprocessor data processing system.
  • PDA personal digital assistant
  • flash memory to provide non-volatile memory for storing operating system files and/or user generated data.
  • the processes of the present invention may be applied to a multiprocessor data processing system.
  • a bus system may be comprised of one or more buses, such as bus 238 or bus 240 as shown in FIG. 2.
  • the bus system may be implemented using any type of communication fabric or architecture that provides for a transfer of data between different components or devices attached to the fabric or architecture.
  • a communication unit may include one or more devices used to transmit and receive data, such as modem 222 or network adapter 212 of FIG. 2.
  • a memory may be, for example, main memory 208, ROM 224, or a cache such as found in NB/MCH 202 in FIG. 2.
  • FIGS. 1-2 and above-described examples are not meant to imply architectural limitations.
  • data processing system 200 also may be a tablet computer, laptop computer, or compatible processing device in addition to taking the form of a PDA.
  • Embodiments of the present invention provide tagging functionality to electronic resources including electronic documents, files and URL resources.
  • User interface part of the invention can be hosted from within the display area of any resource handling program subjected to such facility available.
  • the user's resource handling programs may include a calendaring program, document editing program, spreadsheet program, drawing editing program and presentation document editing program.
  • FIG. 3 represents an overview of an exemplary tag, submit, search and retrieval application which may be used to implement the method and system of the present invention. It should be recognized by those of ordinary skill in the art that the system and method of the present invention may equally be implemented over a host of other application platforms, and may equally be a standalone module. Accordingly, the present invention should not be limited to the application shown in FIG. 1, but is equally adaptable as a standalone module or implemented through other applications, search engines and the like. [056] The overall system architecture shown in FIG.
  • 3 includes five modules: (i) User Interface module 300, (ii) Middleware module 301, (iii) Resource Repository Store 302, (iv) Search Engine Server 303 and (v) RDBMS Data Store 304 will be briefly described in order to provide an understanding of the overall exemplary system; however, the present invention is directed more specifically to innovations associated with the Client module 300 and Middleware module 302.
  • User Interface module 300 is client application running on the operating system allows users to collect, manage and edit tag metadata associated to a document. Even though the present invention is described herein with reference to a generic electronic resource, may also include other documents such as word processing documents, ADOBE documents, workbooks, web pages, emails, notes or any other type of document or file or resource where tagging is desired.
  • a spreadsheet document comprises the Excel ® spreadsheet application program
  • a document edit program comprises the Word ® edit program
  • a presentation document comprises the PowerPoint ® program
  • a note document comprises OneNote ® program
  • email document comprises of Outlook ® messaging program
  • drawing document comprises of Visio ® editing program from Microsoft Corporation headquartered in Redmond, Wash
  • pdf document comprises of Adobe ® document editing application from Adobe Corporation.
  • the User Interface module allows users to submit tag data and the concerned resource content to middleware 301 which can store the tag data and document inside a RDBMS data store 304 and a resource repository store 302 respectively.
  • FIG. 4 represents an exemplary aspect of the present invention to be compared with FIG. 3 above.
  • FIG. 4 represents in detail the various embodiments of the client user interface and the server middleware.
  • the client user interface 409 may include a number of program modules and data files stored on the client comprising Operating System Service 401, User Interface program 400 and local file storage 402.
  • the user interface 400 may have a Web browser application that is operative to request, receive, render, and provide interactivity with electronic documents, such as a Web page that has been formatted using HTML.
  • the Web browser application comprises the Internet Explorer ® Web browser application program from Microsoft Corporation. It should be appreciated, however, that other Web browser application programs from other manufactures may be utilized to embody various aspects of the present invention.
  • the user interface 401 in another embodiment, may have a WINDOWS application that comprises of Windows Forms ® , Windows Presentation Foundation ® and Silverlight ® technologies from Microsoft Corporation.
  • User interface 400 can connect to Middleware 410 in a server system directly or alternatively through the Operating System Service 401. 401 also provide asynchronous services to upload or download files or resources.
  • the middleware 410 may include a number of data providers comprising statistics data provider 404, tag data provider 405 and configuration data provider 406 and program modules comprising tag data and resource receiver module 403, tag data ETL (Extract, Transform and Load) engine module 407 and tag data search engine provider module 408.
  • Statistics data provider 404 provides statistics data related to tag relevancy and usage on a per user basis.
  • Tag data provider 405 provides tag item data in XML (extensible Markup Language) format that can be retrieved from tables comprising dimensional tables, hierarchical tables, master-detail tables, master tables or any designated tables from the RDBMS data store or from any designated files or resources as anyone in the art understands.
  • XML tag item data can be cached in the client and can be accessed by the proxy providers in the client in offline mode when connectivity to middleware is not available.
  • ETL module 407 in general has database objects and routines to implement extraction, transformation of tag data received by module 403 and loading of prepared data into multi-dimensional tables. Module 403 also facilitates saving of resource content in a designated resource repository.
  • the resource repository may be a system running Windows XP or Windows Vista or Windows 2008 Server software with files services or any other operating system with file services.
  • resource repository can be a RDBMS data store or a Microsoft SharePoint Server or any server system capable of holding content.
  • Tag data search engine provider module 408 comprises of search engine plug-in and search API implementation supporting any Search Server or as a standalone.
  • Search Server may be a Microsoft Search Server or a Microsoft SharePoint Server or any other search server or appliance implementations.
  • Every tag item data provided by tag data provider module 405 comprises of a unique number and source name associated to tables in a RDBMS store or local file or any resource.
  • Tag attribute metadata provided by module 405 comprises of properties associated to the tag like name, source table, number of occurrence, and other associated source table names. Tags from previously tagged documents are also provided by this module.
  • FIG. 5 represents an exemplary aspect of the present invention wherein it depicts the general screen display outline of the client user interface comprising of various display areas dedicated to provide specific information for intuitive collection and submission of tag data and resource content.
  • display area size, color and appearance may vary but comprises of a status bar panel 509 at the bottom, Tag item data comprising tag attributes and their values is presented in panel 501 and a tag data item search panel 502 below it.
  • On the right is previous tags listing panel 506, following below is Statistics data panel 507 and toolbar panel 508.
  • Tag dashboard 503 displaying the resource properties and tag attribute names and values, below this is action bar 504 that allows various operations on the current resource being tagged.
  • action bar 504 that allows various operations on the current resource being tagged.
  • FIG. 6 represents an exemplary aspect of the present invention wherein the user interface may be invoked from the operating system file explorer 600. Users may right click on the concerned document or file or resource as displayed by the file explorer and look for text description entry 601 to click on it or any of its context menu items.
  • the text description may be "Tag with Searchprise”. In another example may be "Tag with " followed by a listing of context menu items. In another example the description text may vary and may be configured.
  • FIG. 7 and FIG. 8 represents an exemplary aspect of the present invention wherein the user interface 701 and 801 may be invoked within the word edit program and spreadsheet edit program respectively using the toolbar panel or ribbon panel 700 and 800 provided by the host resource handling program like Microsoft Word ® or Microsoft Excel ® programs.
  • this mechanism can be implemented across Microsoft Office ® 2003 and 2007 programs comprising Word ® , Excel ® , PowerPoint ® , Outlook ® , OneNote ® and InfoPath ® .
  • user interface can be invoked from any host resource handling program subject to API (Application Programming Interface) availability and a visual graphic icon display which can be invoked to trigger the user interface.
  • text in 700 and 800 may be "Tag & Search" with graphical icons.
  • description and graphical icons may vary and can be configured.
  • FIG. 9 represents an exemplary aspect of the present invention wherein the user interface 901 is displayed in the browser 900.
  • User interface 901 may be rendered from XBAP ® (XAML Browser Application) or Silverlight ® or ActiveX ® application, all technologies from Microsoft Corporation or rendered by a HTML (HyperText Markup Language) application.
  • XBAP ® XAML Browser Application
  • Silverlight ® ActiveX ®
  • HTML HyperText Markup Language
  • FIG. 10 represents an exemplary aspect of the present invention wherein it depicts details of the tag user interface elements as outlined in FIG. 3.
  • Tag Items panel 1000 allows the tag item data to be displayed and selected using a tree view controller or a list box. Further the data can be searched using a tag item search text box and button in panel 1020. A sliding error message panel 1019 is displayed whenever there's an error in operation.
  • Tag dashboard 1001 comprises of 2 panels at the minimum wherein Resource Properties panel 1002 displays resource (selected file or document or resource) properties and their values. Each category tag attribute names and values as in panels 1004 and 1005 appear in succession. With as many category of tags, as many panels are shown.
  • Action bar 1007 displays context menu enabled buttons or simple buttons that can act upon the tags and resource being tagged.
  • Tag attribute name selector for each category as selected from the dropdown 1013 is shown as a carousel of graphical icons in carousel graphical control 1014 with scrollable arrow displays 1015. Selectable attribute name is displayed in a label 1016, as the user moves along each of the graphical icons.
  • Tag collections from previously tagged documents are listed in tag listing panel 1008 as shown in the list view 1009. This list view allows drag and drop feature to copy the previous tag collection to current resource being tagged.
  • Statistics panel 1010 displays important tag statistics information like counts related to total tagged documents, searches, downloads and previews made on the tagged documents and assigned reward points to current user logged in from the middleware data provider or from locally cached client data.
  • Status bar 1018 displays the tag data item count and connectivity status.
  • the process of tagging a resource as illustrated in FIG. 11 begins with invoking the user interface, essentially choosing the client interface 1100 is the next step to perform wherein selecting a thick client 1102, user has the option 1103 to invoke it from the operating system file explorer by right clicking on the concerned file and selecting the user interface or by clicking the installed icon from desktop or program group or by invoking from within the resource or document handling program or by dragging and dropping the file icon from operating system file explorer into the interface.
  • Process 1100 moves to 1104 in the event thin client delivery of user interface is desired and browser 1105 need to be launched with requisite URL to load the client interface.
  • the program checks middleware web server connectivity 1107, wherein with connectivity established 1108, upon successful authentication and authorization, proceeds to block 1113 to download configuration data. With failure to connect to middleware server, establishes a connection to local file storage and proceeds to block 1113. Next the process proceeds to retrieve tag categories 1114, followed by tag business dimensional or taxonomy tag item data 1115, tag statistics data 1116 and previous tags 1117 from tagged documents. If the local connectivity or storage is not available, shows default blank screen 1112 with an error message 1111. In the event, blocks 1116 and 1117 fails, the process proceeds to block 1119 with all acquired data so far and finally acquires resource data as in 1120. If blocks 1116 and 1117 succeeds.
  • FIG. 12 illustrates an exemplary aspect of the present invention wherein functionalities of the user interface is depicted as process flows wherein once a user interface with the resource to be tagged is launched successfully as in block 1201, different functions may be selected.
  • new tag attribute name 1204 obtain the new name and call tag manager 1212 to include new tag attribute which then updates the internal storage 1213 and the display as in 1214.
  • Tag attribute can be selected as in block 1215 by clicking on the graphical icon in the carousel panel and corresponding attribute value can be selected from the tag item selector panel as in 1216.
  • Tag collection values as displayed in previously tagged item can be dragged and dropped as in block 1202 upon which this data is updated to current resource being tagged as per block 1203.
  • block 1211 fetches tag item data from various sources and displays in tag item selector panel.
  • validation routine 1219 happens. If successful, proceeds to save the tag content locally 1220 and updates display and checks for middleware server connectivity 1221. If connectivity is successful, proceeds to save tag data to server and if resource is submitted 1223, file is uploaded. Finally statistics is retrieved 1225 and display 1214 is updated. Statistics can be refreshed 1226 separately.
  • FIG. 13 illustrates an exemplary aspect of the present invention wherein different configurations of the present invention can be implemented.
  • all components of the solution may follow a highly scalable and available setup.
  • multiple clients 1300 connect to load balanced middleware web server 1302 and load balanced search server 1303 through a network 1301.
  • the network may be represented by internet or intranet over LAN or WAN or wireless in multitude of combinations and protocols.
  • Web server is connected to load balanced middleware application server 1304 which in turn connects to clustered file server 1305 and clustered database server 1307 which is hooked to a common redundant SAN storage 1306.
  • Search server can access both file and database server.
  • the web, file and application server above may run Windows Server software.
  • Database server may run Microsoft SQL Server.
  • Search Server may run Microsoft Search Server or Microsoft SharePoint Server.
  • multiple clients 1308 connects to a single and combined web and application server 1310 and search server 1311 through a network 1309. They in turn connect to database server 1312 and file server repository 1313.
  • 1310, 1312 and 1313 may run Windows XP or Windows VISTA or Windows Server software.
  • 1311 may run Microsoft Search Server Express or Server.
  • 1312 may run Microsoft SQL Express or SQL Server.
  • FIG. 14 illustrates an exemplary aspect of the present invention wherein the middleware process of receiving tag data and file and its processing is depicted. This process starts at block 1400 followed by 1401 receiving the tag data. Received data is ascertained for content type.
  • content type is tag data as in 1402
  • submission entry records are created and unique ID is provided as in 1403 and moves to block 1412 to mark it for processing.
  • content type is resource content as in 1404, proceeds to check for the tag data entry for this content as in 1405. If successfully tracks down a submission entry, moves to save the content on the repository server 1406 and updates tag entry record 1407 and marks for processing 1412. If unsuccessful at 1405, moves to 1408 to save the file in repository server and marks as error in submission for resolution. If the content type received at 1410 is of permission related data, moves to block 1411 to set up permission on the content authorization accordingly.
  • FIG. 15 illustrates an exemplary aspect of the present invention wherein explains the middleware tag ETL engine process.
  • a scheduler as in 1500 invokes the ETL process on preset time interval or on demand.
  • ETL process as in 1501 scans the submitted tag data that are unprocessed and collects them for processing.
  • ETL process 1502 retrieves unique identifier associated to each tag item data, its source table in the data store and category. Further moves to 1503 to determine the validity of source table data and then prepare additional dimensional data from other tables and configurations 1504, Subsequently prepares data for insertion into multi-dimensional fact table as in 1505 and inserts into the table and updates the processed status as in 1506.
  • FIG. 16 illustrates an exemplary aspect of the present invention wherein depicts search server plug-in and search API interaction with components of the solution.
  • Client 1600 connects to search server 1602 to perform searching wherein the search plug-in 1603 installed inside or outside of the search server acts as an intermediary to talk to search API 1604 in the middleware server which queries the database server 1605 that contains the multi-dimensional views.
  • Search API also fetches the resource content for preview and download by the client either through search server or directly. Activities like previews, downloads and searches delivered by API through the search multi-dimensional database and file server are tracked and counts per user per tagged resource is updated.
  • FIG. 17 represents an exemplary aspect of the present invention wherein it depicts details of the search user interface elements.
  • This embodiment allows tags to be searched locally by loading all tagxml documents cached or saved locally without involving fact tables and search engines.
  • Tag Items panel 1700 loads distinct tag attributes and their distinct values from all tagxml documents and displays using a tree view representation.
  • Tag attributes can be selectively chosen for inclusion in the search criteria.
  • Tag attributes and values data can be narrowed down or refined by using a tag item search text box and button in panel 1701.
  • 1702 comprises of 2 areas namely search text entry area and search results display area wherein a search text box 1703 allows to enter search criteria in free form text and a panel 1705, below, allows tag attributes and their values to be entered by either selecting or dragging and dropping them in this area. Panel 1705 is displayed only when tag attributes are selected. Search results 1706 are displayed upon invoking button 1704. Search statistics and status info are shown in status bar 1707.
  • FIG. 18 represents an exemplary aspect of the present invention wherein it depicts details of the tag data XML document saved with a file extension tagxml.
  • This embodiment shown is a XML document conforming to W3C standards body and houses all tag data between TagXMLDocument elements 1800.
  • ResourceTags element 1801 contains group of tag categories. In this example, categories include, but not limited to DimensionTags 1802, CustomTags 1804, UserTags and ResourceProperties 1805. In another example, it may be of different description and can be varied and configured.
  • Each tag category comprises of corresponding collection of tags generally represented as [TagCategoryjTag and in this example as in DimensionTag element 1802.
  • Each tag comprises of Name representing the tag attribute name, Source representing source table name or source list, Type representing tag category type, IsMultiTagContent representing whether the tag value comprises of multiple tag values.
  • Each tag contains one or multiple tag content elements 1803 which comprises of value and a unique ID.
  • TagMetaData element 1806 holds all tagging operation details and also the saved tagxml document name which has a unique name by prefixing a GUID with resource name and adding tagxml file extension at the end.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Library & Information Science (AREA)
  • Data Mining & Analysis (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

On décrit un système et un procédé destinés à étiqueter une ressource électronique en mettant en place une interface utilisateur intuitive accessible directement par un clic droit sur le fichier de ressource affiché par l'explorateur de fichiers du système d'exploitation et en sélectionnant un programme d'interface utilisateur cité dans un menu, par une invocation à partir du programme correspondant de prise en charge de ressource ou par une invocation à partir d'un navigateur. Après avoir étiqueté une ressource, les données d'étiquetage peuvent être sauvegardées sous la forme d'un document XML. Les données d'étiquetage et / ou le contenu de la ressource peuvent être soumis à un référentiel désigné. En créant des enregistrements de table de faits multidimensionnelle tirés de valeurs de données d'étiquetage et en exposant leurs données préparées à des moteurs et à des algorithmes de recherche, on facilite la recherche d'une ressource quelconque. Il est possible d'effectuer une recherche sur des données d'étiquetage dans des documents XML de données d'étiquetage. On prend note de toute ressource faisant l'objet d'une recherche, d'une identification, d'un accès et d'un téléchargement à partir d'un emplacement au-dessus dudit référentiel par un quelconque algorithme de recherche et des statistiques sont tenues. Un système de récompense attribue des points à des utilisateurs sur la base des décomptes susmentionnés et de critères spécifiques.
PCT/SG2008/000498 2008-12-24 2008-12-24 Système et procédé pour mettre en place un système d'étiquetage incitatif de ressources électroniques WO2010074655A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/SG2008/000498 WO2010074655A1 (fr) 2008-12-24 2008-12-24 Système et procédé pour mettre en place un système d'étiquetage incitatif de ressources électroniques
SG2011075611A SG178008A1 (en) 2008-12-24 2008-12-24 System and method for providing an incentivized tagging system for electronic resources

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SG2008/000498 WO2010074655A1 (fr) 2008-12-24 2008-12-24 Système et procédé pour mettre en place un système d'étiquetage incitatif de ressources électroniques

Publications (1)

Publication Number Publication Date
WO2010074655A1 true WO2010074655A1 (fr) 2010-07-01

Family

ID=42288018

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2008/000498 WO2010074655A1 (fr) 2008-12-24 2008-12-24 Système et procédé pour mettre en place un système d'étiquetage incitatif de ressources électroniques

Country Status (2)

Country Link
SG (1) SG178008A1 (fr)
WO (1) WO2010074655A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9098841B2 (en) 2011-01-03 2015-08-04 Curt Evans Methods and systems for conducting an online contest
WO2018044695A1 (fr) * 2016-08-31 2018-03-08 Microsoft Technology Licensing, Llc Partage de documents par l'intermédiaire d'un étiquetage logique
US10116732B1 (en) 2014-12-08 2018-10-30 Amazon Technologies, Inc. Automated management of resource attributes across network-based services
US10182104B1 (en) 2014-12-08 2019-01-15 Amazon Technologies, Inc. Automatic propagation of resource attributes in a provider network according to propagation criteria

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6510434B1 (en) * 1999-12-29 2003-01-21 Bellsouth Intellectual Property Corporation System and method for retrieving information from a database using an index of XML tags and metafiles
US6947947B2 (en) * 2001-08-17 2005-09-20 Universal Business Matrix Llc Method for adding metadata to data
US7228299B1 (en) * 2003-05-02 2007-06-05 Veritas Operating Corporation System and method for performing file lookups based on tags

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6510434B1 (en) * 1999-12-29 2003-01-21 Bellsouth Intellectual Property Corporation System and method for retrieving information from a database using an index of XML tags and metafiles
US6947947B2 (en) * 2001-08-17 2005-09-20 Universal Business Matrix Llc Method for adding metadata to data
US7228299B1 (en) * 2003-05-02 2007-06-05 Veritas Operating Corporation System and method for performing file lookups based on tags

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9098841B2 (en) 2011-01-03 2015-08-04 Curt Evans Methods and systems for conducting an online contest
US10116732B1 (en) 2014-12-08 2018-10-30 Amazon Technologies, Inc. Automated management of resource attributes across network-based services
US10182104B1 (en) 2014-12-08 2019-01-15 Amazon Technologies, Inc. Automatic propagation of resource attributes in a provider network according to propagation criteria
US11711420B2 (en) 2014-12-08 2023-07-25 Amazon Technologies, Inc. Automated management of resource attributes across network-based services
WO2018044695A1 (fr) * 2016-08-31 2018-03-08 Microsoft Technology Licensing, Llc Partage de documents par l'intermédiaire d'un étiquetage logique
US10409779B2 (en) 2016-08-31 2019-09-10 Microsoft Technology Licensing, Llc. Document sharing via logical tagging

Also Published As

Publication number Publication date
SG178008A1 (en) 2012-03-29

Similar Documents

Publication Publication Date Title
US11176114B2 (en) RAM daemons
US8060513B2 (en) Information processing with integrated semantic contexts
US9069853B2 (en) System and method of goal-oriented searching
US9977827B2 (en) System and methods of automatic query generation
US20090210391A1 (en) Method and system for automated search for, and retrieval and distribution of, information
US20020065857A1 (en) System and method for analysis and clustering of documents for search engine
US20020042789A1 (en) Internet search engine with interactive search criteria construction
US20100005087A1 (en) Facilitating collaborative searching using semantic contexts associated with information
EP3185149A1 (fr) Système et procédé d'inclusion d'éléments dynamics dans une page de résultats de recherche
US20140222795A1 (en) Methods and apparatus for facilitating delivery of a service associated with a product
US20050234894A1 (en) Techniques for maintaining collections of generated web forms that are hyperlinked by subject
US20060112081A1 (en) Storing searches in an e-mail folder
US20080243787A1 (en) System and method of presenting search results
US20070294230A1 (en) Dynamic content analysis of collected online discussions
US20050028156A1 (en) Automatic method and system for formulating and transforming representations of context used by information services
US20130166563A1 (en) Integration of Text Analysis and Search Functionality
US20140136509A1 (en) Personalized search result re-rank based on relationship bond strength alteration among different keywords
US8775336B2 (en) Interactive interface for object search
EP2541446A1 (fr) Procédé et appareil permettant d'effectuer une recherche de contenu d'article au niveau de plusieurs sites de contenu
Coban et al. Towards the design and implementation of an OSN crawler: A case of Turkish Facebook users
US11567908B1 (en) Virtual storage interface
WO2010074655A1 (fr) Système et procédé pour mettre en place un système d'étiquetage incitatif de ressources électroniques
KR101821832B1 (ko) 정보 관리
Oliveira et al. Enabling a unified view of open data catalogs
KR20050074058A (ko) 인터넷상에서 기사를 자동분류하여 타 웹사이트에자동송출하는 시스템 및 그 제어방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08879237

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08879237

Country of ref document: EP

Kind code of ref document: A1