DrawMGT Release V12.1
Doc-to-Doc and Task-to-Task Links
Requirements
- Link related documents:
- Different language versions of same documents (might be solved by multi-file per revision)
- Document X replaces document Y
Document X is a reply to document Y (correspondence chains)
- Ability to make certificate hierarchies. E.g. document X complete implies sub-documents Y1, Y2, etc. complete.
- Ability to create composite documents out of sub-documents
- Ability to create a work breakdown structure of tasks (parent-child tasks)
- E.g. task X has sub-tasks Y1, Y2, etc.
- Ability to display/list the hierarchical structure of documents/tasks (perhaps combined)
Need to have set of link-types, which the project can define.
- May need to be able to change a link from a revision to a document, or document to a revision
Possible Implementations
Add new many-to-many link tables (doc-doc table, task-task table) -- NO
- New table (example):
- fromDrawingId
- toDrawingId
- linkTypeId
- Disadvantage: Have to search in many tables
- New table (example):
Extend the existing CommentRevisions table with objectId fields: -- YES
- Fixes problem of linking a document (without revision) to a task
CommentRevisions (name change to ObjectLinks?) gets the following fields (all id fields form the primary key):
- fromObjectTypeId
- fromObjectId
- toObjectTypeId
- toObjectId
- linkTypeId
- note (optional text that the user can add to describe the link)
- Disadvantage: Have to fix/update some existing code
- Advantage: ALlows links between pretty much anything in the system (revisions, submittals, etc.)
Need to have link-type included with the link (e.g. new table LinkTypeRef)
Link types:
Implement with a standard reference table. E.g. id, code, name, description, define, order(?)
Fields for Front-Page
Multiple Files per Revision