Method and system for linking data across multiple files

• US 20040236754A1
• Filed: 05/21/2003
• Published: 11/25/2004
• Est. Priority Date: 05/21/2003
• Status: Abandoned Application

• Current Assignee: Bentley Systems Incorporated
• Original Assignee: Bentley Systems Incorporated
• Inventors: Workman, Brad, Chmielenski, Tom, Sewall, Shaun, Dulchinos, George, Barr, Jim, Fouche, David
• Application Number:
  US10/442,121
• Publication Number:
  US 20040236754A1
• Time in Patent Office: Days
• US Class Current: 707/10
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/94 Hypermedia Hyperlinking G06F40/134

Abstract

A method of maintaining a bidirectional link between data in a file checked-out from a content management system to a user computer and data in at least one file maintained at the content management system is provided. In the method, a first file is scanned at least when it is one of checked in and checked out of the document management system to locate a link in the file. Information is gathered from the first file regarding a source and target of the link. It is determined if an element in the file is the source or the target. The information is the stored in a database. The information in the database is automatically updated when a second file is corresponding to the other end of the link is checked in to the document management system to reflect changes made to the end of the link in the second file. The changes are applied to the information in the first file.

Claims

1. A method linking data across an AEC project where the data is arranged in a plurality of files, comprising:

defining a link source located in a first of the plurality of files;

defining a link target located in a second of the plurality of files; and

establishing a bidirectional link between the link source and the link target.

2. The method of claim 1, wherein defining a link source further comprises:

storing a sheet definition for the link source in a database;

storing a drawing definition for the link source in the database; and

storing a callout definition for the link source in the database.

3. The method of claim 2, wherein the sheet definition includes at least one of a name, description, and sheet number.

4. The method of claim 2, wherein the drawing definition includes at least one of a name, description, home sheet, and drawing number

5. The method of claim 2, wherein the callout definition includes at least one of the link source, link target, and status.

6. The method of claim 1, wherein defining a link target further comprises:

storing a sheet definition for the link target in a database; and

storing a drawing definition for the link target in the database.

7. The method of claim 6, wherein the sheet definition includes at least one of a name, description, and sheet number.

8. The method of claim 6, wherein the drawing definition includes at least one of a name, description, home sheet, and drawing number.

9. The method of claim 1, further comprising:

detecting predetermined modifications to the link source or the link target; and

automatically updating the bidirectional link to reflect the modification and maintain the link between the link source and the link target.

10. The method of claim 9, wherein the predetermined modification results in a change in at least one of the sheet definition and drawing definition for the link source and the link target and the callout of the link source.

11. The method of claim 10, wherein the change reflects a removal of a sheet from the project and further comprising flagging all callouts referring to the removed sheet to be resolved.

12. In an AEC project including a plurality of design file comprised of models, with each model being comprised of a number of elements, the elements being organized into drawings that are arranged on a number of sheets, a method for establishing and maintaining bidirectional links between data in the plurality of files, the method comprising:

receiving an identification of a link source;

receiving an identification of a link target;

adding a dependency linkage to the link source, wherein the dependency linkage references a link description sufficient to locate the link target; and

indexing the link source, link target and link description is a database.

13. The method of claim 12, further comprising assigning an element ID to the link source.

14. The method of claim 12, wherein the link description is an XML element.

15. The method of claim 12, further comprising storing the link description in the same file as the link source.

16. The method of claim 12, wherein the link source is an annotation.

17. The method of claim 16, further comprising defining reference data for the annotation.

18. The method of claim 17, wherein the reference data comprises a sheet and a drawing number for the link target.

19. The method of claim 18, further comprising automatically updating the reference data for the link source with information about the link target.

20. The method of claim 17, further comprising creating a tag for the reference data and storing the tag with the annotation.

21. The method of claim 20, further comprising creating a recipe that defines how to update a value of the tag and storing the recipe in the tag.

22. The method of claim 21, wherein the recipe is an XML fragment.

23. The method of claim 12, further comprising attaching a target XML fragment to the link target.

24. The method of claim 12, wherein the index is created in a relational database.

25. The method of claim 12, further comprising associating a plurality of different link sources with the same link description.

26. The method of claim 12, further comprising creating an index of annotation elements and including respective link descriptions.

27. A method of maintaining a bidirectional link between data in a file checked-out from a content management system to a user computer and data in at least one file maintained at the content management system, comprising:

scanning a first file at least when it is one of checked in and checked out of the document management system to locate a link indicator in the file;

gathering information from the first file regarding a source and target of the link;

determining if an element identified by the link indicator is the source or the target;

storing the information in a database;

automatically updating the information in the database when a second file is corresponding to the other end of the link is checked in to the document management system to reflect changes made to the end of the link in the second file; and

applying the changes to the information in the first file.

28. The method of claim 27, further comprising:

assigning a unique document ID to each document in the project;

assigning a unique element ID to each element in the first file;

defining an annotation element in the first file;

attaching a dependency linkage to the annotation element; and

creating a link description containing the information about the target, wherein the dependency linkage refers to the link description.

29. The method of claim 28, further comprising storing the link description in the first file.

30. The method of claim 29, wherein the link description is an XML element including at least one of the document ID for the target and the element ID of the target.

31. The method of claim 27, wherein the scanning step searches for dependency linkages.

32. The method of claim 27, further comprising:

assigning a unique document ID to each document in the project;

assigning a unique element ID to each element in the first file; and

attaching a target XML fragment to an element target.

33. The method of claim 28, further comprising attaching a recipe XML fragment to a tag or text element, the recipe defining how to update the value of the tag or text element.

34. The method of claim 33, wherein the applying step comprises:

scanning for elements with recipes attached;

calculating the recipe to calculate a new value for the tag or text element; and

writing the new value into the tag or text element.

35. A system for linking data, comprising:

a database storing a plurality of files that are part of a project, the files being comprised of a plurality of elements;

a content management system controlling access of users to the files and assigning a unique document ID to each document in the project;

means for establishing a bidirectional link between a first element in a first of the plurality of files and a second element in a second of the plurality of files; and

means for updating the link, the first element and the second element to reflect changes made to the first or second element.

36. The system of claim 35, wherein the first element is a link source and the second element is a link target.

37. The system of claim 35, further comprising means for locating and publishing the second element upon a predetermined user operation at the first element.

38. The system of claim 35, further comprising means for updating updates the first element and the link when the second element is moved to a new location.

39. The system of claim 35, further comprising means for displaying all links to the second element.

40. The system of claim 36, further comprising means for placing a callout in the first file and the callout is the link source.

41. The system of claim 36, wherein the link target is a drawing in a sheet and further comprising means for recording a location of the drawing on the sheet and a sheet number of the sheet.

42. The system of claim 41, further comprising means for defining a sheet;

and

means for defining a drawing.