Master Library Overview
The Master Library is a centralised repository of resources, templates, folders and tags maintained at the organisation level. Projects link to master records and can pick up updates as the library evolves.
What Lives in the Master Library
| Asset | Purpose |
|---|---|
| Master Resources | Organisational rate cards — shared across every project. |
| Master Templates | Organisation-standard patterns. |
| Master Folders | Organisation-wide resource folder trees. |
| Master Tags | Shared tag vocabulary. |
| Emission Factors | Organisation-standard factors. |
Scopes
MasterScope enum:
- Global — visible to every organisation using this TX1 install (rare; shipped with TX1).
- Organisation — visible to this organisation only (most common).
Project-scope resources (ProjectId set, IsMaster = false) are different — they live inside a single project.
Linking
A project resource can be linked to a master resource. Linking copies the master's data into the project but remembers the link via MasterResourceId and LinkedMasterVersion.
Sync Behaviours
On each linked resource:
- Manual — TX1 tells you when an update is available, you decide when to sync.
- AutoSync — TX1 applies the new values automatically.
See 11.3 for the full sync model.
What Master Library Gives You
- A single source of truth for rates.
- Consistent templates across estimators.
- Audit trail on version bumps.
- Easy onboarding — new projects drop in and start from known-good rates.
File Formats
The Master Library can be exported to two file formats:
- .masterlib (SQLite) — binary, compact, preserves structure exactly.
- .json — human-readable, good for diff/review.
These files let you share the library between TX1 installations (e.g. a shared file drop, an offsite backup, or between parent / subsidiary organisations).
Metadata Record
MasterLibraryMetadata records:
- LibraryName, Description.
- Version, SchemaVersion.
- CreatedAt, LastModifiedAt.
- Organisation, ContactEmail.
- Counts: ResourceCount, TemplateCount, FolderCount, TagCount.
- Checksum — integrity check on import.
Admin Only Actions
- Creating / editing master records.
- Publishing updates.
- Importing / exporting library files.
- Setting an organisation's default sync behaviour.
Non-admin users consume the library but can't modify it.