Welcome to the ZDDC Archive
@@ -1078,6 +1202,67 @@ body {+ + — project workspace +
+Pick a lifecycle stage, or browse all files.
+ +Archive
+Permanent record of issued and received transmittals, organized by counterparty.
+ + +Working
+Per-user drafting workspace. Your folder is private by default; you can grant access by editing its .zddc file.
Staging
+Outbound transmittals being prepared for issue.
+ + +Reviewing
+Pending review responses — inbound submittals paired with their in-progress drafts.
+ +Master Deliverables List (MDL)
+Each counterparty in the archive has an MDL — an editable
+ table of expected deliverables. The default columns mirror
+ the ZDDC tracking-number components (originator,
+ phase, project, area,
+ discipline, type,
+ sequence, suffix) plus
+ title, plannedRevision,
+ plannedDate, status, and
+ owner.
To edit the MDL for any party:
+-
+
- Open the project archive: +
- Click into a party's folder (e.g.
PartyA)
+ - Click
mdlinside the party folder
+
To customize the columns or schema for a specific party, drop
+ a table.yaml and form.yaml into
+ archive/<party>/mdl/. Operator-supplied
+ files override the embedded defaults entirely.
/' + escapeHtml(project) + '/archive/';
+ }
+
+ // Fetch party list. Best-effort — failures render the
+ // no-parties-yet fallback. We try /No party folders yet. The MDL view auto-renders at any '
+ + 'archive/<party>/mdl/ URL, even when the folder doesn\'t exist on '
+ + 'disk — so you can start editing an MDL before any transmittals have been exchanged.
Direct links — parties currently in archive/:
- ';
+ for (var j = 0; j < parties.length; j++) {
+ var name = parties[j].name;
+ var url = parties[j].url; // server-provided absolute URL
+ html += '
- ' + escapeHtml(name) + ' MDL → '; + } + html += '