1. Platform overview
Role in legislative record management
DMS operates as the centralized repository for legislative documents at Municipality of Jones. Staff upload and classify records; LIS consumes public listings for committee reports, resolutions, ordinances, and session meeting documents.
Core platform functions
- Document Management — upload, classify, and manage legislative files.
- Document Finder — search, download, edit permissions, and file management.
- Folder Management — organize documents within location hierarchy.
- Location hierarchy — Branch, Department, Division, Section.
- OAuth2 API (Laravel Passport) and public listing endpoints for LIS.
2. System participants
DMS administrators
Manage documents, folders, organizational structure, and user accounts.
LIS (report consumer)
Public report pages call GET /api/getdocuments and storage URLs to display legislative records.
OAuth API clients
Authenticated integrations use Passport client credentials for GET /api/documents with filters.
3. Document lifecycle
From upload to LIS consumption
Document upload
Staff upload files with metadata: title, author, type, tags, and document date.
Location assignment
Documents are placed in folders within branch/department/division/section hierarchy.
Access classification
Public, private, or confidential access levels applied per document policy.
API publication
Public documents exposed via /api/getdocuments for LIS report pages.
File serving
Downloads via /storage/{folder_id}/{filename} route used by LIS integrations.
4. Access and routing
Access levels and file delivery
Public (1)
Available for LIS public report listings.
Private (2)
Restricted to authenticated DMS users.
Confidential (3)
Highest restriction; limited staff access.
File serving route: GET /storage/{folder_id}/{filename} — used when files are not in public disk.
5. Document types framework
Type 1 — Committee Report
Committee report documents for legislative review.
Type 2 — Resolutions
Council resolutions published for public access.
Type 3 — Ordinance
Municipal ordinances with date and tag metadata.
Type 4 — Session Meeting
Session-related documents linked to council meetings.
6. API integrations
Passport OAuth and public listing endpoints
GET /api/documents— OAuth2 protected; filter by year, month, type, tags, doc_date.GET /api/getdocuments— public paginated listing for LIS report pages.GET /api/getdocuments/{id}— single document retrieval.- Passport setup:
php artisan passport:client --clientthenPOST /oauth/tokenwith client_credentials.
Related documentation: LIS White Paper · CMS White Paper
7. System architecture
Data hierarchy
Storage
Local disk with optional AWS S3 support per deployment configuration.
8. Security and access controls
- Laravel UI authentication for web admin modules.
- Laravel Passport for OAuth2 client credentials on protected API routes.
- Document permission updates via authenticated web API.
- Access level enforcement on document records before public API exposure.
9. Risk management framework
Operational risk
File history tracking and folder structure reduce misplaced document risk.
Access risk
Three-tier access model limits exposure of confidential legislative records.
Integration risk
LIS dependency on /api/getdocuments and storage URLs; monitor API availability.
10. Operational resilience
DMS availability affects all LIS legislative report pages. Backup storage, database replication, and documented API contracts support continuity during incidents.
11. Platform role summary
DMS, in summary
- Central repository for legislative document types consumed by LIS.
- Hierarchical organization aligned with LGU office structure.
- Dual API model: OAuth for integrations, public listing for portal reports.
- White-label ready for municipal deployments (Jones, Buguey, and others).