WO1999003048A1 - Vues statiques de base de donnees - Google Patents

Vues statiques de base de donnees Download PDF

Info

Publication number
WO1999003048A1
WO1999003048A1 PCT/US1998/014581 US9814581W WO9903048A1 WO 1999003048 A1 WO1999003048 A1 WO 1999003048A1 US 9814581 W US9814581 W US 9814581W WO 9903048 A1 WO9903048 A1 WO 9903048A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
view
information
schema
record
Prior art date
Application number
PCT/US1998/014581
Other languages
English (en)
Inventor
Matteo Cardano
Original Assignee
Infosquare Corporation
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 Infosquare Corporation filed Critical Infosquare Corporation
Priority to AU84854/98A priority Critical patent/AU8485498A/en
Publication of WO1999003048A1 publication Critical patent/WO1999003048A1/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/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G06F16/972—Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Definitions

  • the present invention relates to information storage systems. More specifically, the invention relates to producing and updating hyper-linked views of information stored in a database.
  • Databases are used to store information (or data) in an organized way so that the information can be retrieved and viewed very quickly and reliably. Accordingly, databases are very efficient at storing and retrieving data. To achieve this efficiency in handling data, databases keep the information structured in a way that is efficient for the hardware characteristics of the systems on which they run. Relational database management systems (RDBMSs) keep the data generally organized in tables and indexes. When users query the database, the data is retrieved from tables, formatted and presented to the user in suitable formats for display or printing.
  • RDBMSs Relational database management systems
  • Databases contains two basic kinds of information: content information (e.g., tables) and structural information (e.g., indexes).
  • Content information is data such as names, addresses, documents, descriptions, attributes, and the like.
  • Structural information is the information needed by the database to keep the content information organized in order to optimize the combination of storage space used and performance obtained.
  • the way tables and indexes are maintained in the database is often very different from how users view the information.
  • a database can store in a table a list of names and addresses and in another table a list of products with their description and price.
  • a user working in the sales department can query the database to get the list of people who bought a certain product. In this case, the customer would view on his terminal the data associated to the products and the data associated to individuals.
  • Schemas can be embedded in the application or can be stored in the database itself and represent the empty (data-less) structure of the view that is presented to the users.
  • the preparation of views by the application software is performed every time users query the database to obtain views. Even when many users request the same view at the same time, the application software queries the database and prepares the same view as many times as the number of users. In this case, the application executes the same operation producing the same result many times simultaneously, unnecessarily using up the resources of the system.
  • FIG. 1 shows a process of creating a view of information in a database utilizing a schema.
  • a database 101 includes a customer table 103 and a table product 105.
  • the database record in customer table 103 includes an index to the first database record in product table 105.
  • a sales schema 107 specifies the format of a view of information that a user may request. Dummy values are shown in sales schema 107 to indicate that these values will be filled when the view is created.
  • a view 109 shows the view generated utilizing sales schema 107. As shown, the user is able to see what products a specific customer has purchased.
  • a cache is a temporary replication of part of the data contained in the primary storage (databases in our case) in a faster secondary storage area (generally random access memory or a hard disk).
  • Cache systems are used in database applications to store in memory or in the file system, the most recent table accessed in the database and views produced by the application in order to avoid the redundant execution of operations needed to create a view already prepared for subsequent requests.
  • FIG. 2 shows the use of a cache to store views of information in a database.
  • a user terminal 201 issues a request for a view.
  • a database application 203 checks to see if the requested view is already in a cache 211.
  • the cache stores multiple recently requested views 213. If the requested view is in cache 211, the database application then checks to see if the cached view is invalid or out of date. For example, the database application can check timestamps to determine if the tables utilized to make this view have changed since the view was generated.
  • database application 203 retrieves data from a database 205.
  • Database 205 stores multiple tables 207.
  • the database application retrieves a schema 209 and prepares the view according to the data and schema.
  • the view is then sent to the user and stored in cache 211 for subsequent access.
  • the use of a cache can save the application the time for executing several steps if the view was already prepared and is still available in the cache. Even though the use of a cache can certainly improve the performance (throughput) of an information system, caching has some limitations. An application benefits from a cache only if the view requested by the user was recently prepared for this or another user. Also, since caches are expensive, they are usually limited in capacity and can hold only a fixed number of views. When the cache is full, the oldest views in the cache are removed and replaced with new ones. Therefore, the probability of finding a view in the cache is limited by the size of the cache in relation with the size of the database.
  • Embodiments of the present invention provide methods and systems for producing and updating views of information stored in a database.
  • Schemas or templates
  • the schemas are utilized to produce new views of the information in the database and the new views are published for users to access.
  • the views of information in the database remain current and yet users can access the views without requiring the use of the database and, possibly more important, without requiring the database application to check if a view is both in a cache and still valid, which can be a very time consuming process. Accordingly, the database application can have more processing time for other tasks.
  • the invention provides a method of accessing information in a database.
  • a request to modify a record in the database is received and a view is identified that includes information in the record.
  • a new view is generated that includes information in the modified record, where the new view is specified by a schema that includes at least one tag corresponding to information in the database.
  • the record stores information about a document and the view is a hyper-text representation of the document.
  • the invention provides a method of accessing information in a database.
  • a request to modify a record in the database is received and it is determined if the request changes a view, where the view is specified by a schema that includes at least one tag corresponding to information in the database.
  • a new view is generated that includes information in the modified record. It can be determined the request changes a view by analyzing the request to identify a tag that corresponds to new information in the request and checking the schema for the identified tag.
  • the invention provides a system for viewing information stored in a database.
  • the system includes a view of a document and a schema that specifies the view including at least one tag corresponding to information about the document.
  • a database stores records, where a record includes the information about the document, a pointer to the view and a pointer to the schema.
  • An information manager receives requests to modify the record and generates a new view utilizing the schema so that the new view includes information in the modified record.
  • FIG. 1 shows a process of creating a view of information in a database utilizing a schema.
  • FIG. 2 shows the use of a cache to store views of information in a database.
  • FIG. 3 illustrates an example of a computer system that can be utilized to execute the software of an embodiment of the invention.
  • FIG. 4 illustrates a system block diagram of the computer system of FIG. 3.
  • FIG. 5 shows a block diagram of a system that publishes static views of documents or folders for user access.
  • FIG. 6 shows a relationship of a document, database record, views, and schemas.
  • FIG. 7 shows a flow chart of a process of adding a new document (or folder) to a database.
  • FIG. 8 shows a flow chart of a process of modifying the database including the generation of new views if the views should reflect a change in the database.
  • FIG. 9 shows a flow chart of a process of determining if views change as a result of the modification of the database.
  • FIG. 10 shows a flow chart of a process of generating a new view of information in the database.
  • FIG. 11 shows a flow chart of another process of modifying the database including the generation of new views.
  • FIG. 12 shows an example of a database record.
  • FIG. 13 shows a portion of a schema in hyper-text markup language (HTML) that specifies a view of a folder.
  • FIG. 14 shows a static view of the folder.
  • HTML hyper-text markup language
  • FIG. 15 shows a page that may be utilized to modify the information about the folder.
  • FIG. 16 shows how the page may be utilized to modify the title and abstract of the folder.
  • FIG. 17 shows the database record of FIG. 12 that has been modified as specified in FIG. 16.
  • FIG. 18 shows a new static view of the folder including the modifications.
  • FIG. 3 illustrates an example of a computer system that can be used to execute the software of an embodiment of the invention.
  • FIG. 3 shows a computer system 301 that includes a display 303, screen 305, cabinet 307, keyboard 309, and mouse 311.
  • Mouse 311 can have one or more buttons for interacting with a graphical user interface.
  • Cabinet 307 houses a CD-ROM drive 313, system memory and a hard drive (see FIG. 4) which can be utilized to store and retrieve software programs incorporating computer code that implements the invention, data for use with the invention, and the like.
  • CD-ROM 315 is shown as an exemplary computer readable storage medium, other computer readable storage media including floppy disk, tape, flash memory, system memory, and hard drive can be utilized.
  • FIG. 4 shows a system block diagram of computer system 301 used to execute the software of an embodiment of the invention.
  • computer system 301 includes monitor 303 and keyboard 309, and mouse 311.
  • Computer system 301 further includes subsystems such as a central processor 351, system memory 353, fixed storage 355 (e.g., hard drive), removable storage 57 (e.g., CD-ROM drive), display adapter 359, sound card 361, speakers 363, and network interface 365.
  • Other computer systems suitable for use with the invention can include additional or fewer subsystems.
  • another computer system could include more than one processor 351 (i.e., a multi-processor system) or a cache memory.
  • the system bus architecture of computer system 301 is represented by arrows 367. However, these arrows are illustrative of any interconnection scheme serving to link the subsystems. For example, a local bus could be utilized to connect the central processor to the system memory and display adapter.
  • Computer system 301 shown in FIG. 4 is but an example of a computer system suitable for use with the invention. Other computer architectures having different configurations of subsystems can also be utilized.
  • Embodiments of the invention provide systems and methods for producing and updating views of stored information.
  • the information is in the form of documents or folders stored in a file system.
  • the invention may be advantageously applied to any stored information so it is not limited by the specific embodiments described herein.
  • a "view” of a document is the image of the document the user sees.
  • the invention provides what is called “ static views” because the views do not change when accessed by the user (as in caching), but only upon modification of the database.
  • FIG. 5 shows a block diagram of a system that publishes static views of documents or folders for user access.
  • a user can operate a browser 401 on a computer system that is in communication with a Web server 403.
  • the browser typically receives HTML files via the hyper-text transport protocol (HTTP) and displays the documents on the screen.
  • HTTP hyper-text transport protocol
  • Web server 403 can access multiple views 405.
  • the views are hyper-text documents that include information about (e.g., meta-information) or contained in documents or folders that are stored in the database.
  • Views 405 are in HTML and the user specifies a desired view via a uniform resource locator (URL).
  • URL uniform resource locator
  • views 405 are shown with a couple of hyperlinks 406 for illustration purposes, any number of hyper-links can be used.
  • Web server 403 accesses the appropriate view 405 and sends the HTML file to the user for display by browser 401.
  • the browser and Web server may operate on the same computer system, be on the same intranet or operate on a wide area network (WAN) such as the Internet.
  • WAN wide area network
  • a folder is simply a container of documents and the file system can store the documents and folders in any manner that is known in the art. The description that follows will concentrate the discussion on stored documents. However, folders can and are managed in a similar manner.
  • a database 409 stores information about the documents in file system 407. As will be described in more detail in reference to FIG. 6, database 409 stores a record that includes information about each document in file system 407 that can be requested by a user.
  • database is a repository of information and in FIG. 5, both file system 407 and database 409 provide a repository of information so they can be thought of as a single “database.”
  • the file system is utilized for storing documents in preferred embodiments, the contents of the documents can also be stored in database 409.
  • the information manager acts as the intermediary between Web server 403 that is responsible for providing views of documents and database 409 that is responsible for storing information about documents.
  • information manager 411 has access to one or more schemas 413.
  • a schema is a template of how the information about a document should be displayed. For example, a schema could specify that the information about a document should be shown in condensed form or a schema could specify a more comprehensive form. Schemas can also be directed to different artistic styles of presenting the information.
  • a document can get stored in the database through Web server 403. Assume a user has requested to store a document. Information manager 411 receives the document and can ask the user specific questions about the document in order to determine the meta-information for the document. For example, the user can be asked to enter the author, title, category, keywords, creation date, links to other documents, and the like about the document, which will be generally referred to as "meta-information.” Additionally, the user can specify the schema that will be utilized to view the document. If no schema is specified, a default schema can be utilized.
  • Information manager 411 stores the document in file system 407 and the information about the document in a record in database 409. The information manager then generates a view of the document utilizing the specified schema. Once the view is produced, the information manager publishes the view as indicated by an arrow 415. Once a view is published, the view can be accessed by a user or users through browser 401 via Web server 403 as described above.
  • the information manager is typically on the same computer system as file system 407, database 409 and schemas 413. However, there is no requirement that any of the components of FIG. 5 reside on the same computer system so the components can be distributed between and among computer systems in different ways depending on the application.
  • a user can add a document to the database through browser 401.
  • the user can also modify the document or information about the document through the browser.
  • a direct user access 417 is provided that allows users to accomplish the same or similar tasks directly.
  • a system administrator can have the ability to interact directly with the information manager via direct user interface 417 such as a custom Windows application.
  • FIG. 6 shows details of a document, database record, views, and schemas.
  • a document 451 typically includes text and hyper-links, but it can also include graphics and sounds depending on the application.
  • document 451 can be generated by a conventional word processor.
  • document 451 can be stored in file system 407.
  • a database record 453 includes information about document 451.
  • Record 453 includes meta-information 455 about the document. As shown, the meta-information may include fields indicating the author, title, category, creation date, and the like of the document.
  • Record 453 includes a field that is a link or pointer to document 451. The pointer is typically implemented as a path and file name of the document in the file system, but this is not required.
  • Record 453 also includes zero one or more field pairs of schema/view pointers. Pointers
  • FIG. 459 reference views 461 and pointers 463 reference schemas 465.
  • the schema is the template for producing the view.
  • Pointers 459 and 463 can be implement as URLs or any other mechanism.
  • record 453 can be stored in database 409.
  • both views 461 and schemas 465 are HTML files.
  • the schemas include tags (e.g., an author tag) that correspond to information about the document.
  • tags e.g., an author tag
  • the information corresponding to the tags in the schema are retrieved from the database and inserted into the schema to produce the desired view.
  • Both the views and schemas can have hyper-links to other documents.
  • FIG. 7 shows a flow chart of a process of adding a new document to the database.
  • the information manager receives a new document.
  • the new document may be received by the information manager from a user that wishes to add the document to the database.
  • the document is stored in the file system at a step 503.
  • the path and file name of the document is stored as a pointer to the stored document.
  • meta-information about the document is received.
  • the meta-information can be obtained by providing the user with a form to fill out that includes the desired meta- information.
  • the meta-information will be used in the views of the document to enhance a user's understanding of the document.
  • some or all of the meta- information is obtained automatically by analyzing the document.
  • a user selects a schema that specifies the desired view for the document at a step 507.
  • the schemas can present a variety of different formats in which the document can be viewed.
  • the user may select a schema from a list and in other embodiments, a view utilizing a selected schema is generated for the user to see and approve.
  • the user may select one or more schemas in which the document may be viewed. Additionally, there may be a default schema so if the user does not select a schema, the default will be utilized.
  • the information manager generates the view or views of the document and its meta-information utilizing the selected schema or schemas.
  • the view is published at a step 511, which allows users access to the view.
  • the information manager saves the meta-information in a record in the database.
  • the record can also include a pointer to the document in the file system and pointers to the views and schemas for this document.
  • the related indexes in the database may also need to be updated to reflect the new record.
  • FIG. 8 shows a flow chart of a process of modifying the database including the generation of new views if the views should reflect a change in the database.
  • the information manager receives a request to modify a record in the database.
  • the request can be to modify the meta-information, provide a revised version of the document or to change a schema that produces a view.
  • the request to modify the record in the database is fulfilled at a step 553.
  • the request to modify the record is fulfilled first (i.e., before any views are modified). This is because once the database is updated, the views and other information can be updated at a later date if necessary. For example, after the computer system has recovered from a crash.
  • the information manager determines if the request changes a view specified by schema.
  • the information manager analyzes the schemas to determine if the schemas have a tag that corresponds to information that was modified by the request. The process of determining if views changed will be described in more detail in reference to FIG. 9.
  • the information manager If it is determined that one or more views changed at a step 557, the information manager generates a new view for each view that changes at a step 559. The process of generating new views will be described in more detail in reference to FIG. 10.
  • FIG. 9 shows a flow chart of a process of determining if views change as a result of the modification of the database.
  • the information manager analyzes the request to modify a record in the database to identify tags corresponding to new information in the request. For example, if the request modifies the title of a document, the title tag would be identified.
  • the information manager checks the schema for the identified tag or tags at a step 603. The schemas may be identified by the pointers in the database record associated with the document (see FIG. 6).
  • the information manager analyzes the schemas utilized to view the document and finds each schema that includes the title tag. If an identified tag is found in a schema, the information manager determines that the request changes the view specified by the schema at a step 605. The new view is generated at step 559 of FIG. 8 and can be generated according to a process shown in FIG. 10.
  • FIG. 10 shows a flow chart of a process of generating a new view of information in the database.
  • the information manager retrieves a schema. For each tag in the schema, the information manager retrieves the information corresponding to the tag from the database at a step 653.
  • the tags are not required to be identical to field names in the records of the database. For example, a tag in HTML may need to be in a certain format, which is very different than the format utilized as fields in the database. Any number of ways known in the art may be utilized to match up tags and fields in the database records. In preferred embodiments, a table is produced that provides the translation between tags and fields in the database records.
  • the information manager inserts the information in the schema in place of the one or more tags to produce the new view.
  • the tags serve as placeholders for information about the document. Thus, when a view is created, the information specified by the tags is substituted for the tags.
  • FIG. 11 shows a flow chart of another process of modifying the database including the generation of all new views for the document.
  • the information manager receives a request to modify a record in the database.
  • the information manager fulfills the request at a step 703.
  • Steps 701 and 703 are the same steps as steps 551 and 553 in FIG. 8.
  • the information manager generates all new views for the document.
  • the information manager utilizes each schema specified in the database record for the document and generates a new view for each schema.
  • the new views may be produced according to the process in FIG. 10. Once the new views are generated, the new views are published at a step 707. Publishing the views can entail uploading the new views to URLs specified in the database record.
  • FIGS. 12-18 will be utilized to show an example of an embodiment of the invention.
  • FIG. 12 shows an example of a database record.
  • a database record 801 is shown that includes multiple fields.
  • a title field 803 includes the title of a folder, which is shown as " Title of this Page.”
  • An abstract 805 includes the abstract of the folder, which is shown as "This is the Abstract of this Page.”
  • a schema field 807 indicates the schema to produce the view of the folder, which is shown here a number that indexes the schema.
  • a mapping field 809 and a directory field 811 are related to the location of the view produced utilizing the schema in field 807. The mapping and directory fields are concatenated together to yield part of the URL of the view.
  • the database is not shown with a pointer to the folder on the file system.
  • FIG. 13 shows a portion of a schema in HTML that specifies a view of a folder.
  • a schema 851 is an HTML file that specifies the view of the folder.
  • Tags 853 will be utilized within the schema to specify locations where information from the database should be inserted to generate a view. As mentioned earlier, the tags may not be identical to the fields of the database record so a table may be utilized to match up corresponding tags and fields. For example, a table may be as follows:
  • a table is not required and many other mechanisms can be utilized.
  • FIG. 14 shows a static view of the folder.
  • a view 901 was produced utilizing database record 801 and schema 851. The title from title field 803 was inserted at location 903 in the view and the abstract from abstract field 805 was inserted at location 905. Mapping field 809 and directory field 811 were utilized to produce URL 907 that identifies view 901. The view may be produced by the process described in reference to FIG. 10.
  • View 901 also includes hyper-links 909, 911, 913, 915, and 917. Some hyper-links in views come directly from the document or folder. These hyper-links were present or "hard- coded" into schema 851. Edit hyper-link 919 may be utilized to edit the database as will be describe in more detail in reference to the next figure.
  • FIG. 15 shows a page that may be utilized to modify the information about the folder. If the user activates edit hyper-link 919, a page 951 is displayed. Page 951 is an HTML file that includes information in database record 801. Most notably, title field 803 and abstract field 805 are shown at locations 953 and 955, respectively. The user may then edit these fields by changing the information at these locations.
  • FIG. 16 shows how the page may be utilized to modify the title and abstract of the folder.
  • a page 1001 is the same as page 951 except that the user has changed the title to "NEW TITLE of this Page” and the abstract to " This is the NEW Abstract of this Page.” as indicated at locations 1003 and 1005, respectively.
  • FIG. 17 shows the database record of FIG. 12 that has been modified as specified in FIG. 16.
  • a database record 1051 has a new title in a title field 1053 and a new abstract in an abstract field 1055.
  • FIG. 18 shows a new static view of the folder including the modifications.
  • a view 1101 is produced.
  • View 1101 includes the new title and abstract at locations 1103 and 1005, respectively. The remainder of the view remains unchanged.
  • the example is very simple for illustration purposes, it illustrates that the invention utilizes schemas to produce views of documents or folders stored in a database. As information in the database changes, new views are generated. Users may access the views without requiring the database application to search for and provide the desired document or folder, which allows the database resources to be utilized on other tasks. Additionally, the database application does not need to check the status of the cache continually as in prior art methods.
  • the hyper-links in the views allow users to access other information in the database without actually accessing the database. This can be especially desirable when the number of accesses to the information in the database is far greater than the number of updates to the information. With prior art techniques such as caching, the system continually checks to see if the cache is up to date.
  • the views in preferred embodiments are formatted and presented using a hyper-text language such as HTML, portable document format (PDF), FrameMaker, and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne des procédés et des systèmes de production et d'actualisation de vues (405) d'informations stockées dans une base de données (409). On utilise des schémas (413) pour formater une vue d'informations dans la base de données. Lorsque la base de données est modifiée, les schémas (413) sont utilisés pour produire de nouvelles vues des informations se trouvant dans la base de données (409) et les nouvelles vues sont publiées pour permetttre aux utilisateurs d'y accéder (417). Avec l'invention, les vues (405) d'informations dans la base de données (409) restent actualisées tout en permettant aux utilisateurs d'accéder aux vues (405) sans avoir à utiliser la base de données (409), ce qui lui permet d'exécuter d'autres tâches.
PCT/US1998/014581 1997-07-14 1998-07-13 Vues statiques de base de donnees WO1999003048A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU84854/98A AU8485498A (en) 1997-07-14 1998-07-13 Static views of data bases

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US5242497P 1997-07-14 1997-07-14
US60/052,424 1997-07-14

Publications (1)

Publication Number Publication Date
WO1999003048A1 true WO1999003048A1 (fr) 1999-01-21

Family

ID=21977530

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/014581 WO1999003048A1 (fr) 1997-07-14 1998-07-13 Vues statiques de base de donnees

Country Status (2)

Country Link
AU (1) AU8485498A (fr)
WO (1) WO1999003048A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001084377A2 (fr) * 2000-05-04 2001-11-08 Kickfire, Inc. Systeme et procede de depot d'informations pour un systeme de portail internet
US6804679B2 (en) * 2001-03-12 2004-10-12 Affymetrix, Inc. System, method, and user interfaces for managing genomic data

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5276870A (en) * 1987-12-11 1994-01-04 Hewlett-Packard Company View composition in a data base management system
US5388255A (en) * 1991-12-19 1995-02-07 Wang Laboratories, Inc. System for updating local views from a global database using time stamps to determine when a change has occurred
US5446882A (en) * 1992-10-02 1995-08-29 Apple Computer, Inc. Interface for a computerized database having card and list views
US5713031A (en) * 1990-07-05 1998-01-27 Fuji Xerox Co., Ltd. Hypermedia database system
US5737591A (en) * 1996-05-23 1998-04-07 Microsoft Corporation Database view generation system
US5760770A (en) * 1996-05-15 1998-06-02 Microsoft Corporation System and method for defining a view to display data

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5276870A (en) * 1987-12-11 1994-01-04 Hewlett-Packard Company View composition in a data base management system
US5713031A (en) * 1990-07-05 1998-01-27 Fuji Xerox Co., Ltd. Hypermedia database system
US5388255A (en) * 1991-12-19 1995-02-07 Wang Laboratories, Inc. System for updating local views from a global database using time stamps to determine when a change has occurred
US5446882A (en) * 1992-10-02 1995-08-29 Apple Computer, Inc. Interface for a computerized database having card and list views
US5544358A (en) * 1992-10-02 1996-08-06 Apple Computer, Inc. Interface for a computerized database having card and list views
US5760770A (en) * 1996-05-15 1998-06-02 Microsoft Corporation System and method for defining a view to display data
US5737591A (en) * 1996-05-23 1998-04-07 Microsoft Corporation Database view generation system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DEUX O., ET AL.: "THE STORY OF O2.", IEEE TRANSACTIONS ON KNOWLEDGE AND DATA ENGINEERING., IEEE SERVICE CENTER, LOS ALAMITOS, CA., US, vol. 02., no. 01., 1 March 1990 (1990-03-01), US, pages 91 - 108., XP002914544, ISSN: 1041-4347, DOI: 10.1109/69.50908 *
GARVEY C., WU A.: "ASD-VIEWS.", PROCEEDINGS OF THE 1998 IEEE SYMPOSIUM ON SECURITY AND PRIVACY. OAKLAND, CA, MAY 3 - 6, 1998., LOS ALAMITOS, CA : IEEE COMPUTER SOC., US, vol. CONF. 19, 1 January 1998 (1998-01-01), US, pages 85 - 95., XP002914543, ISBN: 978-0-7803-4994-0 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001084377A2 (fr) * 2000-05-04 2001-11-08 Kickfire, Inc. Systeme et procede de depot d'informations pour un systeme de portail internet
WO2001084377A3 (fr) * 2000-05-04 2003-12-24 Kickfire Inc Systeme et procede de depot d'informations pour un systeme de portail internet
US6804679B2 (en) * 2001-03-12 2004-10-12 Affymetrix, Inc. System, method, and user interfaces for managing genomic data

Also Published As

Publication number Publication date
AU8485498A (en) 1999-02-08

Similar Documents

Publication Publication Date Title
US6012053A (en) Computer system with user-controlled relevance ranking of search results
JP4593793B2 (ja) 問合せ可能なダイナミック・キャッシュを有するウェブサーバ
US7051274B1 (en) Scalable computing system for managing annotations
US6185608B1 (en) Caching dynamic web pages
US7177862B2 (en) Method and structure for federated web service discovery search over multiple registries with result aggregation
US6856992B2 (en) Methods and apparatus for real-time business visibility using persistent schema-less data storage
US8291000B2 (en) Method and system for managing data transaction requests
US20070220089A1 (en) Modular distributed mobile data applications
US20030187841A1 (en) Method and structure for federated web service discovery search over multiple registries with result aggregation
US20030158947A1 (en) Enabling online and offline operation
US7519739B2 (en) Synchronizing a client user interface with a server backend
US6931428B2 (en) Method and apparatus for handling requests for content in a network data processing system
JP2013054755A (ja) 情報のシンボルによるリンクとインテリジェントな分類を行う方法及びシステム
US6915303B2 (en) Code generator system for digital libraries
US20030226104A1 (en) System and method for navigating search results
US7793220B1 (en) Scalable derivative services
US7895337B2 (en) Systems and methods of generating a content aware interface
US6996574B2 (en) System and method for accessing database design information
US8775443B2 (en) Ranking of business objects for search engines
US7089232B2 (en) Method of synchronizing distributed but interconnected data repositories
US6735594B1 (en) Transparent parameter marker support for a relational database over a network
WO1999003048A1 (fr) Vues statiques de base de donnees
EP1014283A1 (fr) Système et méthode basées d'intranet pour catalogage et publication
US7398262B1 (en) Method and system for referencing, archiving and retrieving symbolically linked information
US7349918B2 (en) Method and system for searching binary files

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM HR HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: KR

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA