As a developer, I want Document controller endpoints so that strategic plan documents can be registered, retrieved, and managed through the application API.
From duplicate ticket:
In this ticket, we need to define our "Documents" endpoint, and set up baseline CRUD (note: confirm if we need all CRUD operations) endpoints for any Document in the system. We need to have filtering on document types, agency alignment, year, and extraction job id, at a minimum, for filtering purposes.
This ticket will also include implementing the data layer and models to support these controllers.
Acceptance Criteria
Controllers are defined for all CRUD operations for Documents
Filters are available via parameters for the following fields: DocumentType, AgencyAlignment, Year, ExtractionJobId
Data models are created and a full backend stack implementation exposes the data from the database
As a developer, I want Document controller endpoints so that strategic plan documents can be registered, retrieved, and managed through the application API.
From duplicate ticket:
In this ticket, we need to define our "Documents" endpoint, and set up baseline CRUD (note: confirm if we need all CRUD operations) endpoints for any Document in the system. We need to have filtering on document types, agency alignment, year, and extraction job id, at a minimum, for filtering purposes.
This ticket will also include implementing the data layer and models to support these controllers.
Acceptance Criteria
Controllers are defined for all CRUD operations for Documents
Filters are available via parameters for the following fields: DocumentType, AgencyAlignment, Year, ExtractionJobId
Data models are created and a full backend stack implementation exposes the data from the database